linux/poky.git/meta/classes, branch danny

classes/package_rpm: avoid bash being pulled in unnecessarily

2013-08-22T22:19:43+00:00

The initial installation step for base-passwd, base-files and shadow will pull in bash if any of these packages depend on /bin/sh and a bash package has been built, which is undesirable if you are using busybox; so force the early installation of one or the other depending on which is going to be installed in the second step. Note: this fix is not needed for 1.4 (dylan) and newer, since there we use smart to construct the root filesystem without this initial step. (From OE-Core rev: 71387ee5a126e3df5771da88eb6febc400f249c8) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

sanity.bbclass: Ensure tmpdir exists when running the check

2013-05-08T11:03:16+00:00

This avoids tracebacks from bitbake if the directory doesn't already exist. [YOCTO #3640] (From OE-Core rev: 2d0f0d39dacc57c2c6eefade0b06aed4dc9814d5) Signed-off-by: Richard Purdie

multilib: skip packages that provide virtual/kernel

2013-05-08T11:03:16+00:00

Rather than keying on recipes that inherit kernel.bbclass, we should be checking for providers of virtual/kernel when skipping kernel recipes in multlib builds. Not all providers of virtual/kernel inherit kernel.bbclass (notably linux-dummy), so checking on the provider is a more complete check. We need to be sure to check for inheritance of module-base as well, this allows for packages that provides modules to avoid the multilib renaming. (From OE-Core rev: 036bf4dd800147f18b9b1451061e7e7a794300a7) Signed-off-by: Bruce Ashfield Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

multilib/clsextend: Improve handling of regexps in PACKAGES_DYNAMIC

2013-04-29T17:00:00+00:00

Now that PACKAGES_DYNAMIC is more standardised, starting with ^ anchors, the variable manipulations performed by clsextend for multilib don't work. This patch at least improves it to hack around the problem and enable mulitlib builds to work again. If this code doesn't do the right thing, the recipe is free to override the variable with the correct multilib case. (From OE-Core rev: d4f366c00335d28b90e1b071631aa90ce9d38321) Signed-off-by: Richard Purdie

kernel bbclass: return to original directory in do_deploy

2013-04-23T12:00:52+00:00

* During the base kernel_do_deploy function the directory is changed to DEPLOYDIR in order to do some cleanup and symlinking. However, the directory is not changed back to the original starting directory ${S} at the end. For append functions this means that the starting directory is not ${S} as expected but instead ${DEPLOYDIR}. For functions like the do_deploy_append in recipes-kernel/linux/linux-dtb.inc there is an assumption that you are still in the source directory and not the DEPLOYDIR. Without this change the .dtb files are not copied because the check for the existence of ${DTS_FILE} which is a relative path from the ${S} directory fails. This means that the .dtb files are not copied into the deploy directory and subsequently the deploy/images directory. In the log.do_deploy file you will see lines like: Warning: arch/arm/boot/dts/xxxxx.dts is not available! (From OE-Core rev: cfac9cc41c98eb1858bd3b0dee3dcc672d53f78b) Signed-off-by: Chase Maupin Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

populate_sdk_base.bbclass:fix toolchain relocation issues

2013-04-23T12:00:52+00:00

When run "autoreconf" in toolchain, there is an error if the host's perl's version is not the same as the one in the SDK, the error says that the executable perl mismatches the perl lib's version. This is because most of the autotools' scripts use the "#!/usr/bin/perl -w" which is host perl, but the gnu-configize uses "#! /usr/bin/env perl" which invokes the perl wrapper in the SDK, and the wrapper will set the PERL5LIB to the SDK which causes the mismatch. We can make all the perl scripts to use the host perl or the SDK perl to fix this problem. Cherry-pick commit aeb53bd78991af9fbb60d64176ec864cfc2ddbb9 [YOCTO #3984] (From OE-Core rev: 9c10356bde6d303d84daadb8c1170e08e774f5af) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

populate_sdk_base: tarball installer: SDK overwrite warning

2013-04-23T12:00:52+00:00

This patch contains two fixes: * if the user wants to install the SDK in a directory that already contains a SDK for the same architecture, a warning will be shown; * when the symbolic links are relocated use -n option. Otherwise, symbolic links to existing directories will be created in the directory itself; Cherry-pick commit b751ec137d0228b40a90e9e32b24f5cb5732225b [YOCTO #3401] (From OE-Core rev: c3b00f18f24c5ff48981ea3645a58cf48eaa94aa) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

toolchain-scripts.bbclass:add PYTHONHOME variable to environment-setup

2013-04-23T12:00:51+00:00

When relocating the SDK, applications using python will search for python modules in the default location and will fail to start. The below errors are thrown by gdb, for example: Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] ImportError: No module named site In order to overcome this, add the PYTHONHOME variable to the environment-setup script for both standalone toolchain and adt-installer. No need to do that for meta-ide-support environment script since this toolchain does not get relocated. Cherry-pick commit db0a02492c2a53c1917b753bcf21c4ee7c0ecf59 [YOCTO #3839] (From OE-Core rev: 15454b99e3cbeaf2e411f1e374b512a19a72995a) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

distutils: Replacing path to native python by path to python in the image to support python packages with console-script setup

2013-04-23T12:00:50+00:00

When using distutils for a python package based on a python-setuptools installation script that sets up a console script, the header of the console script created by setuptools points to the python-native path. The console scripts are commonly executed in the image, but not in the sysroot environment. Therefore, the header of the console scripts should point to the python interpreter in the image. Setuptools does not allow to set the path of the python interpreter via some command-line argument. Hence after the installation script ran, the distutils class replaces the path in the console script files created by the installation. (From OE-Core rev: 55c6f1318fe62f7cec37776853cf8bef82a55f89) Signed-off-by: Lukas Bulwahn sgw - added \ to protect the space. Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

populate_sdk_base.bbclass: add execution permission for self-extracting archive

2013-04-23T12:00:50+00:00

[ CQID: WIND00392947 ] It is not good user experience that the self-extracting archive (.sh file) has no execution permission by default. (From OE-Core rev: aede5db60c1e3111f34bda8ea4bb7e890ca77efc) Signed-off-by: Jackie Huang Signed-off-by: Robert Yang Signed-off-by: Mark Hatle Signed-off-by: Saul Wold Signed-off-by: Richard Purdie