aboutsummaryrefslogtreecommitdiffstats
path: root/meta/classes/cross-canadian.bbclass
AgeCommit message (Collapse)Author
2012-11-21classes: Drop do_package stamp-extra-infoRichard Purdie
This was needed when do_package for target recipes was target specific however since it now isn't we can remove these stale references. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-22package.bbclass: Switch shlibs to pkgdata directory and make package ↵Richard Purdie
non-machine specific Currently, do_package is machine specific since the shlibs data is installed into each machine specific sysroot. This change moves the shlibs data to the pkgdata structure, at the expense of having to iterate over a set of shlibs directories instead of a single one. It turns out this isn't any particular hardship for the code and as a result, do_package stops being machine specific leading to optimisations for builds that use a common PACKAGE_ARCH. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-05cross-canadian.bbclass: add native chrpath dependencyLaurentiu Palcu
In order for the RPATHs in 32bit toolchain binaries to be relocated properly, chrpath >=0.14 is needed. [YOCTO #3161] [YOCTO #3201] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-31nativesdk: Switch to using nativesdk as a prefix, not a suffixRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-04-26classes: Add recipe class to overridesRichard Purdie
We have currently no override to detect a recipe being build cross, crosssdk or for target at times we can use virtclass-native and virtclass-nativesdk to override stuff in recipes but we dont have way to modify a variables based on recipe type always. This patch adds in such an override and in particular makes a target override class available. With this change now we can say: EXTRA_OECONF_class-target = "...." EXTRA_OECONF_class-native = "..." EXTRA_OECONF_class-nativesdk = "..." EXTRA_OECONF_class-crosssdk= "..." Based of an original patch by Khem Raj Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-31cross-canadian.bbclass: fix rpath for sdk executablesNitin A Kamble
This makes the libraries located in places like this findable: /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib Which avoids linking cross canadian sdk executables with host libraries like this: $ ldd /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/x86_64-oe-linux/x86_64-oe-linux-gdb linux-vdso.so.1 => (0x00007fffb7fff000) libreadline.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/x86_64-oe-linux/../libreadline.so.6 (0x00007fbfb5511000) libdl.so.2 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libdl.so.2 (0x00007fbfb530c000) libncurses.so.5 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libncurses.so.5 (0x00007fbfb50e9000) libtinfo.so.5 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libtinfo.so.5 (0x00007fbfb4ec2000) libz.so.1 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/x86_64-oe-linux/../libz.so.1 (0x00007fbfb4cac000) libm.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libm.so.6 (0x00007fbfb4a2a000) libpthread.so.0 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libpthread.so.0 (0x00007fbfb480d000) libutil.so.1 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libutil.so.1 (0x00007fbfb4609000) libexpat.so.1 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/x86_64-oe-linux/../libexpat.so.1 (0x00007fbfb43e0000) libc.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libc.so.6 (0x00007fbfb4059000) /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x0000003f05000000) [RP: Whitespace tweaks] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-02-26cross-canadian: Set STAGING_DIR_HOST correctlyRichard Purdie
As reported by Martin Jansa, the path to nativesdk sysroot was changing between nativesdk and cross-canadian recipes. The problem was the incorrect deinfition of STAGING_DIR_HOST in cross-canadian.bbclass. Since nothing really uses the cross-canadian output in the sysroot, only the packages, its not surprising this bug has gone un-noticed. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-26getVar/setVar cleanupsRichard Purdie
Complete the bb.data.getVar/setVar replacements with accesses directly to the data store object. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-10Convert to use direct access to the data store (instead of bb.data.*Var*())Richard Purdie
This is the result of running the following over the metadata: sed \ -e 's:bb.data.\(setVar([^,()]*,[^,()]*\), *\([^ )]*\) *):\2.\1):g' \ -e 's:bb.data.\(setVarFlag([^,()]*,[^,()]*,[^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^() ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-05toolchain-scripts & other classes: add TARGET_LD_ARCH & TARGET_AS_ARCH varsNitin A Kamble
This is comming from x32 need to pass special parameters to ld & as. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-07-25bitbake.conf/classes: Variable cleanupRichard Purdie
This patch removes the variables BASE_PACKAGE_ARCH, BASEPKG_HOST_SYS, BASEPKG_TARGET_SYS and also removes the immediate assignments in several core classes as these are no longer required. This should make it clearer what some of the core variables do and simplfy some overly complex and confusing class code. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-28classes/conf: Drop MULTIMACH_ARCH variable, it adds unused complexity and ↵Richard Purdie
serves no useful purpose Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-28cross-canadian.bbclass: Correct deb package arch.Lianhao Lu
Set DPKG_ARCH to make debian package to be generated with correct architecture. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
2011-01-25bitbake: machine specific sysroots implementationDongxiao Xu
This commit changes the sysroots path to be machine specific. Changes includes: 1) STAGING_DIR_TARGET and STRAGING_DIR_HOST points to machine specific paths. 2) task stamp files. Adding ${MACHINE} info into stamp files for do_populate_sysroots and do_package tasks. Add a BB_STAMPTASK_BLACKLIST to keep native, nativesdk, crosssdk, and cross-canadian stamp unchanged. 3) siteconfig path. Separate the site config path for different machines to avoid one machine adopting the cache file of another machine. 4) sstate. Add machine name to sstate manifest file. Change relocation code for sstate paths since sysroot is machine. Keep native, nativesdk, crosssdk, and cross-canadian unchanged. 5) toolchain scripts. Change the environment path to point to machine specific sysroots in toolchain scripts bbclass. 6) Relocate la files when populating to a different machine of the same architecture. 7) Exclude STAGING_DIR_TARGET and STAGING_DIR_HOST parameter from sstate siginfo since they contain ${MACHINE} information. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2010-12-21meta-environment: Added package of meta-environment-${TARGET_ARCH} forLianhao Lu
environment files. [BUGID #565] Fixing bug #565, added package of meta-environment-${TARGET_ARCH} for environment files used by cross-canadian toolchain. Also corrected the situation of empty config site file for target. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
2010-12-10cross-canadian: Update after PN changes to include TARGET_ARCHRichard Purdie
This patch massively simplifies the canadian packaging and allows multiple toolchain targets to be parallel installed into the same nativesdk sysroot without package name conflits. Since we now do this, we can simplify cross-canadian to become more like nativesdk. This is a first pass over this task, similar changes would be desireable to cross and the whole MULTIMACH_ARCH mess can then probably be similified much further. Signed-off-by: Richgard Purdie <rpurdie@linux.intel.com>
2010-12-10Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH.Lianhao Lu
Using TRANSLATED_TARGET_ARCH instead of TARGET_ARCH for cross-canadian packages. This is due to the TARGET_ARCH of x86_64 would results incorrect packaging in cross-canadian packages. The pacakge name appendix of x86_64 target in cross-canadian packages is x86-64. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
2010-11-03cross-canadian bbclass: replace hardcoded -pokysdk with SDK_VENDORKoen Kooi
Signed-off-by: Koen Kooi <k-kooi@ti.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-17cross-canadian.bbclass: Set TOOLCHAIN_OPTIONS to point at the correct sysrootRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-03cross-canadian: Move binaries into a subdirectory of bin to allow ↵Richard Purdie
multimachine installs and update users accordingly Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-25cross-canadian.bbclass: Tweak secondary toolchain path component to account ↵Richard Purdie
for multimachine Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-25cross-canadian.bbclass: Add in the target compiler paths as well as the sdk ↵Richard Purdie
compilers Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-25cross-canadian: Fix toolchain pathRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02meta-toolchain: Improve layoutRichard Purdie
* Switch from /usr/local/poky to /opt/poky * Use a sysroots directory for both the "native" sdk binaries and the target * Drop the meta-toolchain extras packages. These are replaced with packaged-staging. * Change the nativesdk layout to match our usual filesystem layout * Clean up various hardcoded prefix references Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-25cross-canadian: ensure package dependencies are generated correctlyJoshua Lock
cross-canadian packages need to look for their SOLIBS in the nativesdk sysroot so that dependencies are correctly picked up and meta-toolchains are correctly built. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2010-06-08cross/cross-canadian.bbclass: Save target_exec_prefix variableRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-04-28Fix references to CROSS_DIR now that it has been removedJoshua Lock
CROSS_DIR is no longer removed so fix up classes, packages and documentation which refer to it. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2010-01-20gcc-cross-canadian: Fix include paths and hence c++ compiler issuesRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-01-14cross-canadian: Fix gettext issuesRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2009-12-02cross-canadian: Set PKGHIST_DIR to a correct valueRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2009-09-17nativesdk/package_ipk.bbclass: Clean up sdk package architecturesRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2009-09-17cross-canadian: Add cross-canadian class with gcc and binutils recipesRichard Purdie
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-25 06:20:14 +0000