openembedded-core.git/meta/classes/populate_sdk_base.bbclass, branch 2015-4 Mirror of openembedded-core toolchain-shar-template.sh: Make relocation optional. 2015-02-23T18:00:11+00:00 Randy Witt randy.e.witt@linux.intel.com 2015-02-23T17:00:40+00:00 9721378688a05cd8d8443c6ee4be823e5c0688f6 If the buildsystem is copied into the sdk and its toolchain is to be used, then the relocation provided in toolchain-shar-template.sh isn't needed and will actually fail. So break the relocation aspect out and essentially make it another SDK_POST_INSTALL_COMMAND script. Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
If the buildsystem is copied into the sdk and its toolchain is to
be used, then the relocation provided in toolchain-shar-template.sh
isn't needed and will actually fail.

So break the relocation aspect out and essentially make it another
SDK_POST_INSTALL_COMMAND script.

Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk: Handle OLDEST_KERNEL 2015-02-17T13:42:21+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2015-02-16T16:24:29+00:00 b4caa8085aa15674162ff5135b13409998db9510 Add a check to the SDK so that it only runs on systems with kernel versions it supports. [YOCTO #6856] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Add a check to the SDK so that it only runs on systems with kernel versions
it supports.

[YOCTO #6856]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
sed-native: drop 2015-02-02T12:41:08+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2015-01-29T13:24:09+00:00 863a3966e1a200e7a15fbdbb8e04dce6e3f6c1a2 This was added back in the depths of history (around 2006 in OE-Classic) when apparently the host sed couldn't always be relied upon. We now call the host sed all over the place without this dependency and don't have any problems. On the other hand, having it around can lead to races where we're calling sed in one task and staging it to the sysroot in another, the result being nasty failures compiling binutils for example. Since it isn't needed, let's just drop it completely. Fixes [YOCTO #7264]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
This was added back in the depths of history (around 2006 in OE-Classic)
when apparently the host sed couldn't always be relied upon. We now call
the host sed all over the place without this dependency and don't have
any problems. On the other hand, having it around can lead to races
where we're calling sed in one task and staging it to the sysroot in
another, the result being nasty failures compiling binutils for example.
Since it isn't needed, let's just drop it completely.

Fixes [YOCTO #7264].

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base/meta-environment: Remove overlap from the two 2014-09-22T11:57:12+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-09-19T17:09:12+00:00 063355e5965439c7b3253d692d7ab0ed1189d123 Currently we have the horrible situation where meta-environment packages the toolchain environment files and they get included in the SDK but are broken, then, the SDK code overwrites them with good versions. This is suboptimal. This change fixes the code in meta-environment to create working files and adds in the multilib support from populate_sdk_base, then we remove the code in that base bbclass and rely on the packages being installed if/as/when needed. This removes the duplication and the broken versions of the files, hopefully making all well. [YOCTO #6608] [YOCTO #6613] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Currently we have the horrible situation where meta-environment packages
the toolchain environment files and they get included in the SDK but are
broken, then, the SDK code overwrites them with good versions. This is
suboptimal.

This change fixes the code in meta-environment to create working
files and adds in the multilib support from populate_sdk_base, then
we remove the code in that base bbclass and rely on the packages
being installed if/as/when needed. This removes the duplication
and the broken versions of the files, hopefully making all well.

[YOCTO #6608]
[YOCTO #6613]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
classes/populate_sdk_base: enable adding custom commands to SDK install script 2014-09-11T16:44:40+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2014-09-10T17:19:31+00:00 10df0718d6a626d99beb68cde8d914ee0820d7eb Add an SDK_POST_INSTALL_COMMAND variable which allows additional commands to be added towards the end of the SDK install script, for e.g. additional processing that needs to be done as part of installing the SDK. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Add an SDK_POST_INSTALL_COMMAND variable which allows additional
commands to be added towards the end of the SDK install script, for e.g.
additional processing that needs to be done as part of installing the
SDK.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base: Remap TOOLCHAIN_HOST_TASK variable 2014-08-28T14:12:31+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-08-28T10:27:44+00:00 d2fbc55d6863a767e69092bac686c02c3ec34650 Currently this variable isn't passed through the magic rename mangling. This means that if you try adding "nativesdk-eglibc" to an image directly, you can't since the package is renamed by debian.bbclass and nothing sees the renaming. This is annoying since I wanted to exactly that. This code change passes it through the standard renaming function, the tricky part is that we have to set PKGDATA_DIR to point to the correct sysroot during the call. We create a copy of the datastore for the purposes of the call to do this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Currently this variable isn't passed through the magic rename
mangling. This means that if you try adding "nativesdk-eglibc"
to an image directly, you can't since the package is renamed
by debian.bbclass and nothing sees the renaming.

This is annoying since I wanted to exactly that. This code
change passes it through the standard renaming function, the
tricky part is that we have to set PKGDATA_DIR to point to
the correct sysroot during the call. We create a copy of the
 datastore for the purposes of the call to do this.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
classes/populate_sdk_base.bbclass: add a manifest for target sdk 2014-08-27T11:12:06+00:00 Corneliu Stoicescu corneliux.stoicescu@intel.com 2014-08-26T10:05:41+00:00 3d42fd1f050a1382b15c3c4d59fd02d0ed7091b2 Similar to the way BSP images have rootfs a manifest, the toolchain now also has a manifest file created alongside the sdk image. Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Similar to the way BSP images have rootfs a manifest, the toolchain now also has a manifest file created alongside the sdk image.

Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base: Move toolchain installation script to a separate file 2014-08-15T07:46:40+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-08-14T13:33:33+00:00 f99732a29689c65083ad09abb302f372042c8cd4 It makes sense to move the script to a separate file, making the bbclass clearer and allowing the end user to more easily customise or replace it. There are no functionality changes, just the addition of some substitution variables. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
It makes sense to move the script to a separate file, making the bbclass
clearer and allowing the end user to more easily customise or replace
it. There are no functionality changes, just the addition of some
substitution variables.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
classes: Combine rootfs_<pkgtype> and populate_sdk_<pkgtype> 2014-08-15T07:43:27+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-08-14T13:31:40+00:00 2cf42b49003494e1b10775523c9a2547eaf16ea4 There is no real reason to have these separate files any longer. It does mean in meta-toolchain type recipes some extra variables are defined but it also means the common code can be grouped and maintained together which I believe is more beneficial. We therefore merge the classes. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
There is no real reason to have these separate files any longer. It does
mean in meta-toolchain type recipes some extra variables are defined but
it also means the common code can be grouped and maintained together
which I believe is more beneficial. We therefore merge the classes.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk_base: Fix grep command usage on old hosts 2014-07-29T08:57:54+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-07-28T16:55:05+00:00 7986adeac16550b33f65fded39a55f668e0e543f "man grep" on centos: -R, -r, --recursive Read all files under each directory, recursively; this is equivalent to the -d recurse option. "man grep" on a more recent ubuntu system: -r, --recursive Read all files under each directory, recursively, following symbolic links only if they are on the command line. This is equivalent to the -d recurse option. So we have an issue when the SDK installer (even with buildtools-tarball) is used on old hosts since it may try and dereference paths which it should not. This is caused by differences in the behaviour of grep -r on older systems. The fix is to wrap this in find so that only real files are found (as elsewhere in the script. [YOCTO #6577] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
"man grep" on centos:

       -R, -r, --recursive
              Read all files under each directory, recursively; this is equivalent to the -d recurse option.

"man grep" on a more recent ubuntu system:

       -r, --recursive
              Read all files under each directory, recursively, following symbolic links only if they are on the command line.  This
              is equivalent to the -d recurse option.

So we have an issue when the SDK installer (even with
buildtools-tarball) is used on old hosts since it may try and
dereference paths which it should not. This is caused by differences in
the behaviour of grep -r on older systems.

The fix is to wrap this in find so that only real files are found (as
elsewhere in the script.

[YOCTO #6577]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>