freescale/fsl-community-bsp-base

BSP base files

fsl-community-bsp-base's Issues

MACHINE and DISTRO environment variables are unset even if they were set explicitly

It's possible that someone that's automating the build needs these variables after the build.
In my particular case, I needed the MACHINE variable to find the directory with images.
It was very confusing to me why and where these variables disappeared after the build.

On another note, if someone would like to run export MACHINE=imx7d-pico to configure their environment, this would be unset on subsequent calls of source setup-environment, resulting in very confusing behavior.

A function with local variables would seem like a nice solution to me. I'll see if I find the time to make a pull request.

Pyro release

I have a project on top of Wandboard Solo Rev. D1 board. Unfortunately, I have noticed that support of this bord is not presend in stable branch ("morty"), so I have two options: base on top of "morty" and do necessary changes to u-boot, kernel or I can just wait for "pyro" release.

When do you plan to release "pyro"?

Thanks in advance for your answer.

setup-environment fails unless system shell is /bin/bash

The shebang line on ./setup-environment invokes the script with /bin/sh

However the script only works if sh == /bin/bash/ . This causes at least two problems on modern distros where dash provides /bin/sh.

First, directory 'build' gets created underneath sources/poky. Reason is that supplying parameters to "sourced" scripts is a bash extension.

Also, the script also uses "echo -e" which, under some shells, results in a literal "-e" being echoed. This interferes with checking and listing the supported machine types.

Simple fix is to replace #!/bin/sh with #!/bin/bash

A more complex fix would be possible such as is used by Poky's own oe-init scripts if preferred, but I have gone for minimal changes at the moment. This doesn't change the Freescale BSP shell requirement, just makes it explicit.

bitbake core-image-minimal-xfce4 fails

Building core-image-minimal-xfce4 fails with machine set to wandboard / imx6dlsabreauto.conf (morty branch).

| ../../libxfce4ui-4.12.1/libxfce4ui/xfce-sm-client.c:60:22: fatal error: gdk/gdkx.h: No such file or directory
|  #include <gdk/gdkx.h>

Something removes gdk/* headers from
/tmp/sysroots/MACHINE/usr/include/gtk-3.0/

It is present there in the begining of build process, but then disappears and compilation of libxfce4ui fails with error above.

Thanks in advance for your support.

Master build is broken at parsing stage

I'm seeing a lot of warnings and several errors when trying to use the build setup from this manifest.

Steps to reproduce the issue:

1. repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master
2. repo sync
3. setup for i.MX8M Mini EVK board: EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source setup-environment build
4. bitbake core-image-base

NOTE: On consecutive invocation of the bitbake core-image-base command - the build proceeds without warnings or errors, it happens only when above sequence is invoked.

Following errors are observed:

ERROR: Nothing RPROVIDES 'libssp-nonshared-staticdev' (but /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-core/musl/musl_git.bb RDEPENDS on or otherwise requires it)
libssp-nonshared RPROVIDES libssp-nonshared-staticdev but was skipped: incompatible with host aarch64-poky-linux (not in COMPATIBLE_HOST)
NOTE: Runtime target 'libssp-nonshared-staticdev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libssp-nonshared-staticdev']
ERROR: Nothing RPROVIDES 'bsd-headers-dev' (but /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-core/musl/musl_git.bb RDEPENDS on or otherwise requires it)
bsd-headers RPROVIDES bsd-headers-dev but was skipped: incompatible with host aarch64-poky-linux (not in COMPATIBLE_HOST)
NOTE: Runtime target 'bsd-headers-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['bsd-headers-dev']
ERROR: Nothing RPROVIDES 'musl-dev' (but /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-core/musl/musl_git.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'musl-dev'
NOTE: Runtime target 'musl-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['musl-dev']
ERROR: Nothing RPROVIDES 'musl' (but /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-core/musl/musl_git.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'musl'
NOTE: Runtime target 'musl' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['musl']
ERROR: Nothing PROVIDES 'bsd-headers' (but /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-core/musl/musl_git.bb DEPENDS on or otherwise requires it)
bsd-headers was skipped: incompatible with host aarch64-poky-linux (not in COMPATIBLE_HOST)
ERROR: Nothing PROVIDES 'libssp-nonshared' (but /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-core/musl/musl_git.bb DEPENDS on or otherwise requires it)
libssp-nonshared was skipped: incompatible with host aarch64-poky-linux (not in COMPATIBLE_HOST)
WARNING: preferred version 1.20.imx of wayland-protocols not available (for item wayland-protocols)
WARNING: versions of wayland-protocols available: 1.20
WARNING: preferred version 1.20.imx of wayland-protocols not available (for item wayland-protocols)
WARNING: versions of wayland-protocols available: 1.20

There are also a lot of warnings reported about the replacement of preferred providers, like following:

WARNING: /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-graphics/ttf-fonts/liberation-fonts_2.00.1.bb: Variable key PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}compilerlibs (gcc-runtime) replaces original key PREFERRED_PROVIDER_virtual/x86_64-pokysdk-linux-compilerlibs (nativesdk-gcc-runtime).
WARNING: /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-graphics/ttf-fonts/liberation-fonts_2.00.1.bb: Variable key PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}g++ (gcc-cross-${TARGET_ARCH}) replaces original key PREFERRED_PROVIDER_virtual/x86_64-pokysdk-linux-g++ (gcc-crosssdk-${SDK_SYS}).
WARNING: /storage/projects/fsl-bsp-from-manifest/sources/poky/meta/recipes-graphics/ttf-fonts/liberation-fonts_2.00.1.bb: Variable key PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}gcc (gcc-cross-${TARGET_ARCH}) replaces original key PREFERRED_PROVIDER_virtual/x86_64-pokysdk-linux-gcc (gcc-crosssdk-${SDK_SYS}).
WARNING: /storage/projects/fsl-bsp-from-manifest/sources/meta-openembedded/meta-python/recipes-devtools/python/python3-html5lib_1.1.bb: Variable key PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}compilerlibs (gcc-runtime) replaces original key PREFERRED_PROVIDER_virtual/x86_64-pokysdk-linux-compilerlibs (nativesdk-gcc-runtime).
WARNING: /storage/projects/fsl-bsp-from-manifest/sources/meta-openembedded/meta-python/recipes-devtools/python/python3-html5lib_1.1.bb: Variable key PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}g++ (gcc-cross-${TARGET_ARCH}) replaces original key PREFERRED_PROVIDER_virtual/x86_64-pokysdk-linux-g++ (gcc-crosssdk-${SDK_SYS}).
WARNING: /storage/projects/fsl-bsp-from-manifest/sources/meta-openembedded/meta-python/recipes-devtools/python/python3-html5lib_1.1.bb: Variable key PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}gcc (gcc-cross-${TARGET_ARCH}) replaces original key PREFERRED_PROVIDER_virtual/x86_64-pokysdk-linux-gcc (gcc-crosssdk-${SDK_SYS}).

Can this be taken care of? This has been reported several times already: at least once on meta-freescale ML indirectly and once in PR in meta-freescale layer.

-- andrey

setup-environment clobbers bblayers.conf when using TEMPLATECONF

If you attempt to use TEMPLATECONF to define an alternate bblayers.conf, the setup-environment script will overwrite it which is unexpected behavior. This is due to the script line that explicitly copies from the local templates to the build path conf/ dir, losing the template brought in by the TEMPLATECONF usage.

Note that the treatment of local.conf works because the script in this case modifies what is copied rather than overwriting what is used, so using TEMPLATECONF in that respect works.

fsl-community-bsp-base/setup-environment

Line 166 in 70535e1

cp $TEMPLATES/* conf/

Recommend removing the explicit copy and that templates get copied via a default TEMPLATECONF value that can be properly overridden at the command-line.