openembedded-core.git/meta/classes/toolchain-scripts.bbclass, branch dylan Mirror of openembedded-core Add kernel arch variable in SDK environment variable list for supporting build external kernel module using SDK 2013-02-28T23:14:04+00:00 Jessica Zhang jessica.zhang@intel.com 2013-02-25T22:20:52+00:00 7fc7e98801bd72b9662528f94b315749e6075666 Signed-off-by: Jessica Zhang <jessica.zhang@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
toolchain-scripts.bbclass: add PYTHONHOME variable to environment-setup 2013-02-19T22:37:40+00:00 Laurentiu Palcu laurentiu.palcu@intel.com 2013-02-19T14:15:03+00:00 e7a21cd69a326ab7e2d0e410db28f24956f61208 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 <prefix> Could not find platform dependent libraries <exec_prefix> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] 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] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
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 <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
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]

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
toolchain-scripts.bbclass: Export M4 2012-10-05T13:39:20+00:00 Khem Raj raj.khem@gmail.com 2012-10-04T23:47:39+00:00 06c5593d15f206458b9a5b45ed1229abfee16e95 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 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
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

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
toolchain-scripts: Remove extra - from ar/nm command names 2012-07-19T10:42:09+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2012-07-19T10:42:07+00:00 ca30b6587841f5e9a42aaedb8e0b89ff5a4a6a37 TARGET_PREFIX already has the dash included. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
TARGET_PREFIX already has the dash included.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove the - between ${TARGET_PREFIX} and ar/nm for the env script, as this will make autotools look for arm-none-linux-gnueabi--ar instead of arm-none-linux-gnueabi-ar. 2012-07-19T10:16:25+00:00 Martin Ertsaas mertsas@cisco.com 2012-07-19T10:00:51+00:00 6434fc102e73ed81d2092e4c4ba5f9fb806545c8 Signed-off-by: Martin Ertsaas <mertsas@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Martin Ertsaas <mertsas@cisco.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta-ide-support: Add native qemu support for meta-ide-support 2012-07-18T07:34:37+00:00 Jessica Zhang jessica.zhang@intel.com 2012-07-16T22:29:07+00:00 3ea597249c18d73417abe7d7a9d32bba00499914 [YOCTO #2761] This patch fixed the issue that after "bitbake meta-ide-support" and try to start qemu and it will fail. This is due to the meta-ide-support lacking dependency for qemu native and ended up using qemu under /usr/bin. Fix the issue by adding dependency for qemu native in meta-ide-support and also add the path info in the environment-setup script. Signed-off-by: Jessica Zhang <jessica.zhang@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
[YOCTO #2761]

This patch fixed the issue that after "bitbake meta-ide-support" and try to start qemu and it will fail.  This is due to the meta-ide-support lacking dependency for qemu native and ended up using qemu under /usr/bin.  Fix the issue by adding dependency for qemu native in meta-ide-support and also add the path info in the environment-setup script.

Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
toolchain-scripts: Sync the SDK/ADT values to the build system 2012-07-17T17:02:10+00:00 Mark Hatle mark.hatle@windriver.com 2012-07-10T20:54:38+00:00 2bd0aaf98c5d586638d82f5f22c1c24122a889a3 The build system passes specific TUNE (fundamental) flag values to various tools instead of using a shell wrapper or similar. It is important that the build system and ADT/SDK match the behaviors exactly, or we are likely to have differences in the way build-system and external components are built leading to configuration, compilation and/or run-time problems. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The build system passes specific TUNE (fundamental) flag values to various
tools instead of using a shell wrapper or similar.  It is important that the
build system and ADT/SDK match the behaviors exactly, or we are likely to
have differences in the way build-system and external components are built
leading to configuration, compilation and/or run-time problems.

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
populate_sdk: enable basic multilib support 2012-07-03T07:05:30+00:00 Mark Hatle mark.hatle@windriver.com 2012-06-22T23:44:06+00:00 42545ffbb37f2646a2a8c20999c21d3300e24f59 In order to enable basic multilib support for the export of an SDK image, a number of minor changes had to be made: The value of MULTIMACH_TARGET_SYS needs to be variable. This way we can define the value to the appropriate multilib. (Also in some cases the default PACKAGE_ARCH is set to MACHINE_ARCH which is incorrect for the SDK.) Add a companion REAL_MULTIMACH_TARGET_SYS, based on code from meta-environment, to allow for this. We have to convert the do_populate_sdk into a python call, and then break up the previous items into three parts. * Image construction * Setup of environment files * Generation of the tarball Then we can iterate over the multilibs to populate the environment files. Finally, matching changes were needed in the toolchain-scripts file. And what I presume is an optimization of immediate evaluation for TOOLCHAIN_CONFIGSITE_NOCACHE and ..._SYSROOTCACHE needed to be done at runtime, otherwise the wrong values may be used. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> 
In order to enable basic multilib support for the export of an SDK
image, a number of minor changes had to be made:

The value of MULTIMACH_TARGET_SYS needs to be variable.  This way we
can define the value to the appropriate multilib.  (Also in some cases
the default PACKAGE_ARCH is set to MACHINE_ARCH which is incorrect for
the SDK.)  Add a companion REAL_MULTIMACH_TARGET_SYS, based on code
from meta-environment, to allow for this.

We have to convert the do_populate_sdk into a python call, and then
break up the previous items into three parts.
  * Image construction
  * Setup of environment files
  * Generation of the tarball

Then we can iterate over the multilibs to populate the environment files.

Finally, matching changes were needed in the toolchain-scripts file.  And
what I presume is an optimization of immediate evaluation for
TOOLCHAIN_CONFIGSITE_NOCACHE and ..._SYSROOTCACHE needed to be done at
runtime, otherwise the wrong values may be used.

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
meta-toolchain: Popluated the libc siteconfig files. 2012-03-23T12:00:58+00:00 Lianhao Lu lianhao.lu@intel.com 2012-03-23T08:33:05+00:00 eeee4b8c097e60070e4654a223b41fea0c96a12b Fixed bug [YOCTO #2159] by correctly populate the libc's siteconfig files. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Fixed bug [YOCTO #2159] by correctly populate the libc's siteconfig
files.

Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes: Convert to use appendVar and appendVarFlags 2012-03-05T18:33:18+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2012-03-03T10:41:41+00:00 3b57de68e70e77dbc03c0616a83a29a2e99e40b4 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>