openembedded-core.git/meta/classes/populate_sdk_base.bbclass, branch dizzy

populate_sdk_base/meta-environment: Remove overlap from the two

2014-09-22T11:57:12+00:00

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

classes/populate_sdk_base: enable adding custom commands to SDK install script

2014-09-11T16:44:40+00:00

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 
Signed-off-by: Richard Purdie

populate_sdk_base: Remap TOOLCHAIN_HOST_TASK variable

2014-08-28T14:12:31+00:00

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

classes/populate_sdk_base.bbclass: add a manifest for target sdk

2014-08-27T11:12:06+00:00

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 
Signed-off-by: Richard Purdie

populate_sdk_base: Move toolchain installation script to a separate file

2014-08-15T07:46:40+00:00

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

classes: Combine rootfs_ and populate_sdk_

2014-08-15T07:43:27+00:00

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

populate_sdk_base: Fix grep command usage on old hosts

2014-07-29T08:57:54+00:00

"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 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

populate_sdk_base: Include do_rootfs depends for do_populate_sdk

2014-07-27T07:30:13+00:00

"bitbake core-image-minimal -c populate_sdk; rm tmp -rf; bitbake core-image-minimal -c populate_sdk"
breaks due to missing dependencies on things like update-rc.d. Since
we're effecitvely building a rootfs, we need all the same depends
as do_rootfs has.

The easiest was to achieve this is to simply load them. This resolves
the failure when targeting the task from sstate.

Signed-off-by: Richard Purdie

populate_sdk_base: Extend TOOLCHAIN_TARGET_TASK to include multilib variants

2014-07-25T14:33:32+00:00

Most people expect the toolchain from a multilib build to contain multilib
components. This change makes that happen and is easy for users to override
should they want something different.

Signed-off-by: Richard Purdie

populate_sdk_base: ensure that filenames with empty space character are handled

2014-07-18T23:08:46+00:00

When extracting toolchain, if the list $executable_files has filenames
with empty space character, the list will created but relocate_sdk.sh
will not handle it well. This will lead to the below erro:

    ./tmp/deploy/sdk/buildtools-mytools-x86_64-nativesdk-standalone-1.6.1.0.sh
    Enter target directory for SDK (default: /opt/mydistro/mytoolset/1.6.1.0):
    You are about to install the SDK to "/opt/mydistro/mytoolset/1.6.1.0". Proceed[Y/n]?
    Extracting SDK...done
    Setting it up.../opt/mydistro/mytoolset/1.6.1.0/relocate_sdk.sh: line 2: sintaxe error `token'  `('
    /opt/mydistro/mytoolset/1.6.1.0/relocate_sdk.sh: line 2: `e

The same occurs with replacement of ${SDKPATH} in configs/scripts/etc files.

We should ensure that full path is protected before relocate_sdk.sh
and ${SDKPATH} replacement calls.

Signed-off-by: João Henrique Ferreira de Freitas 
Signed-off-by: Richard Purdie