linux/poky.git/meta/classes/populate_sdk_base.bbclass, branch 1.3

SDK: allow toolchain installation from another directory

2012-09-21T10:10:24+00:00

This patch will allow one to run the installer from another directory than the one where it's actually located. Suppose the installer is in /home/user/test/my/sdk and the current directory is in a different place. With this patch, one can run the installer like this: $ sh ~/test/my/sdk/poky-eglibc-x86_64-arm-toolchain-gmae-1.2+snapshot-20120920.sh [YOCTO #3135] (From OE-Core rev: 3c7aac33cb63dc63b989db4e9d7389a7f4d3c18d) Signed-off-by: Laurentiu Palcu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

SDK: relocate symlinks too

2012-09-21T10:10:23+00:00

The directory usr/libexec/ in the SDK sysroot contains the default symlinks to the toolchain binaries and these, too, need to point to the correct toolchain path. [YOCTO #3090] (From OE-Core rev: 6e4923c0c9b218271fd44d78df9987b5cabb1c03) Signed-off-by: Laurentiu Palcu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

SDK: remove references to Poky distro from tarball installer

2012-09-21T10:10:23+00:00

The installer should be generic. (From OE-Core rev: eba5cdf10aa49da844ac141f00b79327da0cb8c3) Signed-off-by: Laurentiu Palcu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

SDK: fix installation into symlinked directories

2012-09-21T10:10:22+00:00

The SDK installation scripts should not canonicalize symlinked directories because the entire relocation would be done to the directory to which the symlink points. Instead, if the installation is a symlink, use that path to relocate the binaries. For example, if we have the following symlink: /opt/sdk -> ~/my/test/sdk the binaries will be relocated to /opt/sdk not ~/my/test/sdk as it is done now. [YOCTO #3102] (From OE-Core rev: 9e6a25e2e9a7f37c3baa0b2949a43ac4127868da) Signed-off-by: Laurentiu Palcu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

Replace "echo -e" with "printf" to have the same behavior in dash or bash

2012-09-20T12:33:50+00:00

oe-core removed the prerequisite to have sh as bash. POSIX doesn't define any options and furthermore allows 'echo -e' to be the default behavior. This means that in dash 'echo -e' will actually print '-e' and interpret backslashes by default. We use instead 'printf' builtin command with or without '\n' to simulate 'echo -e' or 'echo -n'. 'printf' needs format while 'echo' can be used without any arguments. So 'echo >' was replaced by 'printf "" >'. 'echo' without '-n' flag adds a new line by default so to keep the same behavior of two new lines while using 'echo "\n"', 'printf "\n\n"' is used. [YOCTO #3138] (From OE-Core rev: a19880ad10ccb5d7d909dcf9de5c3dc58a0ebcd3) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie

Rename task to packagegroup

2012-09-04T11:52:55+00:00

"Package group" is a much more appropriate name for these than task, since we use the word task to describe units of work executed by BitBake. (From OE-Core rev: 424dcf7046e4ad09dcc664eb1992201195247fcf) Signed-off-by: Paul Eggleton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

nativesdk: Switch to using nativesdk as a prefix, not a suffix

2012-09-02T12:52:06+00:00

As discussed on the mailing lists, using a suffix to package names is hard and has lead to many recipes having to do PKGSUFFIX games. Its looking extremely hard to scale nativesdk much further without hacking many recipes. By comparison, using a prefix like multilib does works much better and doesn't involve "hacking" as many recipes. This change converts nativesdk to use a prefix using the existing multilib infrastructure. (From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c) Signed-off-by: Richard Purdie

populate_sdk_base.bbclass: fix SDK relocation issues

2012-08-17T12:06:41+00:00

The problem appears if multiple setup environment scripts are found. In order to find only the script we're interested in, I removed globbing in matching pattern with ${REAL_MULTIMACH_TARGET_SYS} that will be expanded to the correct string. Also, fix a problem when changing the scripts/configs. The grep pattern matched also files that contained "text" in their name. (From OE-Core rev: d81768560676da201fd730ae3930b080ab8c5c75) Signed-off-by: Laurentiu Palcu Signed-off-by: Richard Purdie

populate_sdk_base.bbclass: create self-extracting archive

2012-08-02T14:28:39+00:00

In order for the SDK to be relocatable, the user would need to call a setup script to change the binaries acordingly. Having an auto-extracting archive has the advantage of being more user friendly and the user does not have to call the setup script separately after extracting the SDK. It is called automatically. (From OE-Core rev: d4e976849da845d595db7029d8089946ae16d982) Signed-off-by: Laurentiu Palcu Signed-off-by: Richard Purdie

classes/populate_sdk_base: don't break existing do_populate_sdk depends

2012-07-31T07:02:09+00:00

We set do_populate_sdk[depends] in populate_sdk_*.bbclass, but since these are inherited at the top of populate_sdk_base.bbclass, those values are wiped out by using = at the end of the latter class. Use += to avoid this. (From OE-Core rev: a87b5d6cab34579cf3abe03f4663d9a72e218397) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie