summaryrefslogtreecommitdiff
path: root/meta/classes
AgeCommit message (Collapse)AuthorFiles
2011-01-26staging.bbclass: No need to create these directories any more, also remove ↵Richard Purdie1
invalid comment Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-25sanity/sstate: Due to the sysroot layout changes, the toolchain bootstrap ↵Richard Purdie2
process changes and the recent pseudo bug, bump the tmpdir layout version number and the sstate version numbers Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-25base/sstate.bbclass: Rename fetcher "go" method to "download" when using ↵Yu Ke2
fetch v2 Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25base.bbclass: use bb.fetch2 unpack APIYu Ke1
Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25bitbake: machine specific sysroots implementationDongxiao Xu11
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>
2011-01-25gcc/libc: Change bootstrap to use an intermediate sysroot and hence no ↵Richard Purdie1
longer overwrite files Based upon patches from Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-25sstate.bbclass: allow each step of toolchain bootstrap processes to do ↵Dexuan Cui1
populate_sysroot independently Some steps (like gcc-cross-initial, gcc-cross-intermediate and eglibc-initial) will install to new locations to avoid file overwriting. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
2011-01-25cross.bbclass: make MULTIMACH_TARGET_SYS adjustable for bindir, libdir, ↵Dexuan Cui1
libexecdir This will be used by gcc-cross-initial and gcc-cross-intermediate. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
2011-01-24linux-yocto: allow multiple BSPs per branchBruce Ashfield1
By default the linux-yocto recipes operate on the current branch and use it as a trigger to locate the description of a board. This model works well when using the git repo outside of a build system since the commands can be simply invoked and will do something useful. However, it does mean that you can't have two BSPs that differ only by configuration, building out of a single branch in the repository. This means that you must have many branches for very similar BSPs. This model is still preferred, but having the choice of branching strategies is better. With this change we can have multiple BSPs using a single branch with the preferred description being hinted from the build system by passing the $machine value to updateme/configme. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-24update-rc.d.bbclass: Changed RDEPENDS for nativeSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-21package_deb: Remove access to the D directory which isn't used and might not ↵Richard Purdie1
exist (same problem as the previous patch to package_ipk fixes) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21package_ipk: Do not depend on the existence of "D" to create ipk packageDongxiao Xu1
If build from sstate results, the ${D} will not be installed. In this case the creation of ipk package will be skipped, which will cause the build failure. Fix the issue by removing the judgement of ${D} existence. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-01-21staging: Use relative path in sysroot-destdir for target recipesDongxiao Xu6
Original we used absolute path in sysroot-destdir for both native and target recipes. This commit changes target recipes to use relative path which is same as the image directory. [sgw: merged with libtool sysroot work] Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-21insane.bbclass: skip checks on .la installed statusScott Garman1
Enabling libtool sysroot support triggers these errors but they are a valid change in behavior. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21staging.bbclass, utils.bbclass: remove la mangling codeScott Garman2
libtool v2.4 --with-libtool-sysroot eliminates the need for la mangling. Based on Khem Raj's OE commits. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21autotools.bbclass: libtool sysroot support changesScott Garman1
We do not do it for native recipes, as the native compiler should fall back to a prefix of /usr and not solely depend on the sysroot. Otherwise we end up staging everything in the native sysroot before we start to build target recipes. Also remove la mangling code, which is no longer necessary. Commit derived from Khem Raj's OE commits. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-20distrodata.bbclass: add .xz file typeSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-20qt4: Enable accessibility and sm option for LSB.Jingdong Lu1
LSB library checks will look for some symbols of qt4 libraries. Enable "accessibility" and "sm" in order to pass the LSB test. Signed-off-by: Jingdong Lu<jingdong.lu@windriver.com>
2011-01-20distutils(-common-base) bbclass: sync with OEKoen Kooi2
When using python recipes imported from OE (e.g. python-cheetah) parsing only succeeds when python has already been built due to the PYTHON_DIR references. This commit syncs the classes with OE to make it work, but keeps the *.pyo removal from yocto. Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-20python-dir bbclass: import from OEKoen Kooi1
This will be used later on when updating the distutils classes A small deviation from OE is the use of PYTHON_BASEVERSION instead of non-deterministic python code. See https://lists.yoctoproject.org/pipermail/poky/2011-January/002320.html for some background info Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-20setuptools bbclass: import from OEKoen Kooi1
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-20sanity.bbclass: remove SDK_ARCH checkJessica Zhang1
remove sanity check for SDK_ARCH=i686 due to recent fixes in cross toolchain areas, etc. the old issue no longer exists Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
2011-01-20base.bbclass: fix parse error on recipes with '++' in their namePaul Eggleton1
Fixes "multiple repeat" or "nothing to repeat" errors when parsing recipes with '++' in the file name. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-20sanity.bbclass: Disable TERMCMD checking with noop patchingMark Hatle1
If PATCHRESOLVE is set to "noop", then it isn't supposed to try and resolve patches at all, and thus does not need TERMCMD. Therefore, make sure Poky doesn't check for (and possibly fail at finding) TERMCMD if it isn't needed in the first place. Signed-off-by: Derek Buitenhuis <dbuitenh@windriver.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2011-01-20qemuimagetest: Use same image during sanity testing instead of copying a new ↵Jiajun Xu1
image for each case To reduce the time on sanity testing, we remove variable SHARE_IMAGE and use a new variable TEST_SERIALIZE in local.conf. It is by default set to 1. Poky will copy and boot the to-be tested image for only once. It will not remove or kill the image and test cases will be serialized executed against the same image. If it is set to 0, image is always be copied for each cases, which takes much time. I had a experiment that latest qemuppc sato only takes 7 minutes to finish 9 sanity test cases, which takes more than 20 minutes before. I also removed sanity case "boot" from sato/sdk/lsb because the other cases for these targets already cover the check point of "boot". Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-20gdk-pixbuf: Add 2.22.1 as new recipeZhai Edwin1
Updating gtk+ to 2.23.2 requires gdk-pixbuf, which is originaly a module in gtk+. Borrow hardcoded_libtool.patch from original gtk+, and add configure_fix.patch to fix build failure in cross-compile environment. As gdk-pixbuf is a stand-alone package now, gdk-pixbuf-csource-native can be safely removed. So extend gdk-pixbuf with native support, and make related packages depend on it. Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
2011-01-19linux-yocto: update validate_branches to detected invalid commit IDsBruce Ashfield1
The previous implementation of invalid commit ID checks would error early when a bad object was detected. Rather than changing to set +e for the entire routine, we'll capture the output and do an explicit check for a bad object and throw a useful error message when it is detected. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-19linux-yocto: streamline new BSP creationBruce Ashfield1
By setting BOOTSTRAP to the branch that should be used for a currently undefined BSP a build can be completed and an environment for streamlining the BSP created. With the appropriate machine.conf, and a defconfig any MACHINE can be built against and inherit the configuration of the standard yocto kernel. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-19sstate.bbclass: Ensure clean/setscene sstate functions run under appropriate ↵Richard Purdie1
locking Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-19package.bbclass: Take a shared lock when reading to improve do_package ↵Richard Purdie1
parallelism Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-17staging: relocate *.la paths in destination dirsDongxiao Xu1
Keep the la files in source directories unchanged, and do relocation in destination directories (sysroot-destdir). Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-01-17libc-package.bbclass: should not rm scsi/*.hDexuan Cui1
{e}glibc should install the scsi/*.h files, which are needed by hal. Currently hal can build because eglibc-initial (which has its own do_install) installs the files. In future eglibc will have its own sysroot, so hal won't build. BTW: in OE side, eglibc's do_install also doesn't remove the files. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
2011-01-14qemuimagetest: Use the same image in sanity testing to fix the timeout issue ↵Jiajun Xu1
on autobuilder Fixes [BUGID #595] Because of the QEMU booting slowness issue(see bug #646 and #618), autobuilder may suffer a timeout issue when running sanity test. We introduce variable SHARE_IMAGE here to fix the issue. It is by default set to 1. Poky will copy latest built-out image and keep using it in sanity testing. If it is set to 0, latest built-out image will be copied and tested for each case, which will take much time. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-14image.bbclass: Use the dedicated BB_WORKERCONTEXT, not bitbake internals to ↵Richard Purdie1
detect context Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-13insane.bbclass: Make sure QA issues are reported as warningsRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-12kernel.bbclass: Remove a binary generated by recent kernel versionsRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-12kernel bbclass: add 'perf' to kernel-modules blacklistKoen Kooi1
This makes 'kernel-modules' installable again when perf isn't enabled in the kernel config Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-12Adding check for DL_DIR permissions: sanity.bbclassBeth Flanagan1
Check to ensure that DL_DIR is set and that if it exists that it is user writeable. Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
2011-01-12meta-environment: Remove c++ include dir from CXXFLAGS.Lianhao Lu1
[BUGID #651]. c++ include dir is no longer needed in the environment files due to commit f13cb20. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
2011-01-12cpan.bbclass: add a new parameter EXTRA_PERLFLAGSNitin A Kamble1
We use host perl while building target perl modules. When some of the prebuilt perl modules such as scalar::util are used in the build process directly or indirectly, perl needs to load the arch specific .so library file. If perl can not find the .so library files, then perl tries to use the target pm files which ends up in circular perl module depedancy causing build time perl invocation to fail. Adding this new parameter viz EXTRA_PERLFLAGS to cpan.bbclass allows perl module recipes to specify the location of such host .so files for hostperl, so that build time invocation of perl does not fail. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-01-12cpan.bbclass: use LIBDIR instead of DATADIRNitin A Kamble3
perl 5.12.2 does not use /usr/share/perl path, and all that stuff goes in /usr/lib/perl. This commit fixes cpan class which depends on /usr/share/perl. cpan.base/build.bbclass: change /usr/lib/perl5 to /usr/lib/perl Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-01-10kernel-yocto: pass the build directory to configmeBruce Ashfield1
configme used to be able to calculate the output/build directory when branches were always <machine>-<kernel type>. Branch names can now be widely different and to avoid embedding complexity in the scripts it is easier to just pass ${B} from the build system down to the scripts. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-07insane.bbclass: Enable the package_qa_hash_style checkRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-06base.bbclass: Use the new stampfile function in bitbake to determine the ↵Richard Purdie1
path to the stampfile Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-06insane.bbclass: Fix message for LIC_FILES_CHKSUM ErrorsSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-05rootfs_rpm: fix rootfs generation rm errorDarren Hart1
During a poky-image-minimal build I ran into the following error: rm: cannot remove `/vol/1/dvhart/poky.git/build/tmp/work/atom-pc-poky-linux/poky-image-minimal-initramfs-1.0-r0/rootfs/install': Is a directory This is caused by a missing -r (recursive) argument to rm. This patch adds that to the rm command of rootfs_rpm.bbclass. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-05rootfs_rpm.bbclass: Remove temporary work files in install directory, saving ↵Richard Purdie1
the manifests as logfiles into ${T} Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-04base.bbclass: add lock file for do_unpack taskYu Ke1
This patch intend to fix the random unpack failure of linux-libc-headers-yocto and linux-yocto. The root cause of the unpack failure is that: these two recpies has the same URL, thus has the same dest file during the fetch and unpack phase: do_fetch : create tar ball ${DL_DIR}/git_git.pokylinux.org.linux-yocto-2.6.37.tar.gz do_unpack : extract tar ball ${DL_DIR}/git_git.pokylinux.org.linux-yocto-2.6.37.tar.gz fetch phase is protected by lockfile, so it works fine. but unpack phase is not lock protected, thus there is race condition like: when linux-yocto do_unpack is extracting the tar ball, linux-libc-headers-yocto do_fetch starts to create tar ball thus overwrite linux-yocto's tar ball and cause linux-yocto do_unpack failure To fix this issue, do_unpack also need to be protected by lock Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-04sstate.bbclass: fix multimachine builds when PACKAGE_ARCH = MACHINE_ARCHKoen Kooi1
previously you could only build one set of packages for multiple machines: MACHINE=foo bitbake task-base MACHINE=bar bitbake task-base would only create task-base packages for foo, but not for both foo and bar. Doing MACHINE=bar bitbake task-base -c cleanall would remove the packages for foo. The solution is to use MULTIMACH_ARCH as suggested by Richard Purdie. Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2010-12-31base.bbclass: Add error message for base_do_unpack failuresRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-19 04:57:46 +0000