linux/poky.git/meta/classes/toolchain-scripts.bbclass, branch daisy

toolchain-scripts/meta-environment: Further cleanup code duplication

2013-11-06T11:02:27+00:00

There was still duplicated code in toolchain-scripts, this further cleans up the functions to remove it. The now unused includedir parameter is also dropped. The final scripts do end up reordered slightly and the sysroot is parametrised for the IDE scripts which is an improvement but should have no functional difference. (From OE-Core rev: 1dbd65b4d14319e784a66776c1e9943d0179d3ee) Signed-off-by: Richard Purdie

toolchain-scripts: Drop darwin8 code

2013-11-06T11:02:26+00:00

The code was clearly broken and isn't used, even by meta-darwin so we might as well remove it. (From OE-Core rev: b9d51bfe0d4821f5de75085ba8af732c46de3328) Signed-off-by: Richard Purdie

toolchain-scripts/meta-environment: Merge toolchain_create_sdk_env_script and the for_installer variant

2013-11-06T11:02:26+00:00

Having two scripts which do basically the same thing is a nightmare. This merges them together. It also makes the sysroot location a variable in its own right which may be more useful for end users wanting to change sysroot. (From OE-Core rev: 213e0c67e938b802e6bb2246f00b7343a6f77b99) Signed-off-by: Richard Purdie

toolchain-scripts: Fix TARGET_SYS reference

2013-10-11T22:10:58+00:00

There was a fix missing from a previous commit: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=20a86e16bc54b74fbdb2a3a407d54210ea262925 since there was another section of toolchain-scripts needing updating. This patch fixes the missing reference and unbreaks the ADT toolchain. [YOCTO #5340] (From OE-Core rev: e1b8b4859f00b40fb941a07a394ed35e06541663) Signed-off-by: Richard Purdie

cross-canadian: Fix TUNE_PKGARCH references

2013-10-04T17:26:50+00:00

The cross-canadian compilers are now build once per architecture but were being installed into tune specific locations which is incorrect. This adjusts things so they are make TARGET_ARCH specific. We gain the tune specific parts from the target sysroot which remains tune specific, the compiler and tools are independent ot that. binutils/gcc require sysroot options but since we reset at runtime, these shouldn't have dependencies in the sstate checksums. They are therefore also excluded. With these patches, switching machines does not result in a rebuild of *-cross-canadian and the compiler is correctly located and referenced in the target images. (From OE-Core rev: f58acab6414fe96d9e07ebbe86b348d2ac2bed5f) Signed-off-by: Richard Purdie

toolchain-scripts.bbclass:Add CROSS_COMPILE variable to environment-setup file

2013-05-15T21:09:49+00:00

when compiling the linux kernel manually. users need to set CROSS_COMPILE separately. adding the CROSS_COMPILE variable will be nice for using. (From OE-Core rev: b66ec45e5dd9418a6568c04ef30854531a4b66f3) Signed-off-by: Zongchun Yu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

Add kernel arch variable in SDK environment variable list for supporting build external kernel module using SDK

2013-02-28T23:15:46+00:00

(From OE-Core rev: 7fc7e98801bd72b9662528f94b315749e6075666) Signed-off-by: Jessica Zhang Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

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

2013-02-19T22:37: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. [YOCTO #3839] (From OE-Core rev: e7a21cd69a326ab7e2d0e410db28f24956f61208) Signed-off-by: Laurentiu Palcu Signed-off-by: Richard Purdie

toolchain-scripts.bbclass: Export M4

2012-10-05T13:49:54+00:00

some packages use M4 variable from environment and sometimes its hardcoded to /usr/bin/m4 if not found in environment. Lets define it such that it is picked from path (From OE-Core rev: 06c5593d15f206458b9a5b45ed1229abfee16e95) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

toolchain-scripts: Remove extra - from ar/nm command names

2012-07-19T10:44:16+00:00

TARGET_PREFIX already has the dash included. (From OE-Core rev: ca30b6587841f5e9a42aaedb8e0b89ff5a4a6a37) Signed-off-by: Richard Purdie