openembedded-core.git/meta/classes/populate_sdk_base.bbclass, branch jethro Mirror of openembedded-core populate_sdk_base: Ensure PKGDATA_DIR exists 2015-10-24T11:23:42+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2015-10-23T03:30:36+00:00 319c5d55bb0c7e429766f46dd42a15e16a43c4dd The code assumes that PKG_DATADIR exists and will fail if an image has not been generated which creates it. This occurs when something like buildtools-tarball is built which doesn't have target packages, only nativesdk ones. Since this shouldn't be fatal, workaround this by creating the missing directory. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The code assumes that PKG_DATADIR exists and will fail if an image has not been
generated which creates it. This occurs when something like buildtools-tarball
is built which doesn't have target packages, only nativesdk ones.

Since this shouldn't be fatal, workaround this by creating the missing
directory.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base: Simplify postprocess commands 2015-09-29T14:15:47+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2015-09-28T10:56:15+00:00 baa4e43a29e45df17eaa3456acc179b08d571db6 When looking at and trying to build a slightly customised SDK, I realised the code could be simplified and written in a way which was more customisable. This patch moves various function calls into the SDK_POSTPROCESS_COMMAND which was intended for this kind of use. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
When looking at and trying to build a slightly customised SDK, I
realised the code could be simplified and written in a way which was
more customisable.

This patch moves various function calls into the SDK_POSTPROCESS_COMMAND
which was intended for this kind of use.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base: Fix aarch64 OLDEST_KERNEL sdk issues 2015-09-12T21:47:25+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2015-09-11T12:25:46+00:00 522ba4c51fff53566678b2689d0d63c393e417b3 aarch64 sets OLDEST_KERNEL to 3.14. This stops the aarch64 SDK installing on anything with an older kernel which is clearly incorrect. I attempted to extract the correct non-overridden version from the data store but it proved problematic and I was running into data store issues. Those are a separate problem but there isn't time to fix this right now. Instead just code the SDK kernel version separately to work around this for now (and fix the autobuilder tests and SDK usage). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
aarch64 sets OLDEST_KERNEL to 3.14. This stops the aarch64 SDK installing on
anything with an older kernel which is clearly incorrect.

I attempted to extract the correct non-overridden version from the data store
but it proved problematic and I was running into data store issues. Those
are a separate problem but there isn't time to fix this right now.

Instead just code the SDK kernel version separately to work around this for
now (and fix the autobuilder tests and SDK usage).

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
toolchain-shar-extract.sh: better default install path for extensible SDK 2015-09-07T15:10:58+00:00 Brendan Le Foll brendan.le.foll@intel.com 2015-09-07T12:42:18+00:00 5486e76cd8abb946b81cff78719d67cfb87cddc6 Extensible SDK cannot be installed as root so by default offer to install it in user's home directory under distro/distro_version replacing the normal SDK version '+' char with a '_' as that's a restricted character for bitbake Signed-off-by: Brendan Le Foll <brendan.le.foll@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Extensible SDK cannot be installed as root so by default offer to install it in
user's home directory under distro/distro_version replacing the normal SDK
version '+' char with a '_' as that's a restricted character for bitbake

Signed-off-by: Brendan Le Foll <brendan.le.foll@intel.com>
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
extensible sdk: Error when trying to install as root. 2015-07-20T09:39:00+00:00 Randy Witt randy.e.witt@linux.intel.com 2015-07-16T20:34:21+00:00 309e8f4e536148056223f50637ed291c48d148ca Since the extensible sdk uses bitbake, which can't run as root, the sdk shouldn't be installed as root. Previously it would error out late into setup when bitbake errored saying not to run bitbake as root. Now the script errors with a message saying the extensible sdk can't be installed as root. [Yocto #7545] Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Since the extensible sdk uses bitbake, which can't run as root, the sdk
shouldn't be installed as root.

Previously it would error out late into setup when bitbake errored
saying not to run bitbake as root.

Now the script errors with a message saying the extensible sdk can't be
installed as root.

[Yocto #7545]

Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
populate_sdk_base.bbclass: don't inherit toolchain-scripts.bbclass 2015-07-12T21:53:19+00:00 Robert Yang liezhi.yang@windriver.com 2015-07-09T08:49:10+00:00 000ff33729854b1a41206a087cde1e50f49017e0 Fixed when enable multilib: require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake core-image-minimal No lib32 package should be built since we don't build lib32-core-image-minimal, but a lot them are built: lib32-opkg-utils lib32-cryptodev-linux lib32-sqlite3 lib32-libtool-cross lib32-ncurses lib32-db lib32-diffutils lib32-zlib lib32-gcc-cross-i686 lib32-gcc-cross-initial-i686 lib32-flex lib32-libgcc-initial lib32-libffi lib32-linux-libc-headers lib32-expat lib32-openssl lib32-glibc lib32-binutils-cross-i686 lib32-gcc-runtime The are introduced by toolchain-scripts.bbclass' anonymous function (the MULTILIB_VARIANTS), but it doesn't need toolchain-scripts.bbclass, in fact, so remove it to fix the problem. [YOCTO #7961] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Fixed when enable multilib:
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"

$ bitbake core-image-minimal
No lib32 package should be built since we don't build
lib32-core-image-minimal, but a lot them are built:
lib32-opkg-utils
lib32-cryptodev-linux
lib32-sqlite3
lib32-libtool-cross
lib32-ncurses
lib32-db
lib32-diffutils
lib32-zlib
lib32-gcc-cross-i686
lib32-gcc-cross-initial-i686
lib32-flex
lib32-libgcc-initial
lib32-libffi
lib32-linux-libc-headers
lib32-expat
lib32-openssl
lib32-glibc
lib32-binutils-cross-i686
lib32-gcc-runtime

The are introduced by toolchain-scripts.bbclass' anonymous function (the
MULTILIB_VARIANTS), but it doesn't need toolchain-scripts.bbclass, in
fact, so remove it to fix the problem.

[YOCTO #7961]

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base.bbclass: use pbzip2 to compress SDK tarfiles 2015-06-27T21:41:59+00:00 Andre McCurdy armccurdy@gmail.com 2015-06-25T19:46:47+00:00 670f5cda06070ae888d17cca7a07aa74d751c2f7 Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base: also record the host part into manifest 2015-04-28T06:55:58+00:00 Chen Qi Qi.Chen@windriver.com 2015-04-27T10:19:59+00:00 3069641589942f52b11e88cfea564ebba4beb3c2 For now, we can create manifest for the target part for SDK. I think it's nice to have a place for users to look into to examine contents of the host part of SDK. This also affects uninative-tarball and buildtools-tarball as they inherit populate_sdk.bbclass. After this change, we could have a manifest file created in the deploy directory containing a list of packages used to construct them. [YOCTO #7604] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
For now, we can create manifest for the target part for SDK.
I think it's nice to have a place for users to look into to examine contents
of the host part of SDK.

This also affects uninative-tarball and buildtools-tarball as they
inherit populate_sdk.bbclass. After this change, we could have a manifest file
created in the deploy directory containing a list of packages used to
construct them.

[YOCTO #7604]

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base: avoid executing empty function 2015-04-24T10:09:19+00:00 Chen Qi Qi.Chen@windriver.com 2015-04-24T06:26:54+00:00 4c0ae7cce06de15f6881654ecec7f8bb743ff389 `bitbake uninative-tarball' raises the following warning. WARNING: Function doesn't exist This is because SDK_PACKAGING_FUNC is set to "" in its recipe. Anyway, we need to check this variable to avoid executing empty function. [YOCTO #7598] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> 
`bitbake uninative-tarball' raises the following warning.

    WARNING: Function  doesn't exist

This is because SDK_PACKAGING_FUNC is set to "" in its recipe.
Anyway, we need to check this variable to avoid executing empty function.

[YOCTO #7598]

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
classes/populate_sdk_base: Show title in SDK installer 2015-04-24T10:05:57+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2015-04-20T16:47:08+00:00 0af913887f4c0a79c6b950bd5d57c06333520a14 Show a friendly title when running the SDK installer, so the user knows what SDK they are installing. The title is controlled by the SDK_INSTALLER_TITLE variable and includes the distro name and SDK version by default. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Show a friendly title when running the SDK installer, so the user knows
what SDK they are installing. The title is controlled by the
SDK_INSTALLER_TITLE variable and includes the distro name and SDK
version by default.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>