summaryrefslogtreecommitdiff
path: root/meta/classes
AgeCommit message (Collapse)AuthorFiles
2011-01-28cross-canadian.bbclass: Correct deb package arch.Lianhao Lu1
Set DPKG_ARCH to make debian package to be generated with correct architecture. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
2011-01-28Initial commit of license reporting:Beth Flanagan1
This is an intial commit for the license reporting system. A few notes: The LICENSE fields needs to be standardized throughout poky. As it stands, we throw a warning if the license file is not found (either because it does not exist or because LICENSE_FILE_CHKSUM is munged) in the generic license directory. This should eventually become an error. I've seen a few places where Apache-v2.0 is written differently and I'm sure this will throw the above warning. This does not put the license data on the rootfs. Also, I provide both the actual license text and a link to the best guess of the generic_license. That guessing is not very robust and I'm loath to get into a bunch of pattern matching rather than standardize LICENSE. This adds one new param to poky.conf and one new to license.bbclass: LICENSE_DIR: the base directory we copy all the license results to (set in license.bbclass) COMMON_LICENSE_DIR: this is the directory that holds all the common generic license files. currently meta/files/common-licenses (set in poky.conf) TODO: - We should verify the common-licenses. I stripped these from my Ubuntu 10.10 system. - We should allow the capability of licenses on the rootfs, although the resulting image created would be a lot larger. - More common-licenses. I don't include bzip, zlib, ICS.... I should, but that means tracking down a lot of licenses. - General cleanup of licensing and standardization of names. We should standardize on a naming convention. What's in licenses.conf should match up with what is in the recipes which should match with what is in common-licenses. Outside the scope of this though. See: http://bugzilla.pokylinux.org/show_bug.cgi?id=650
2011-01-28staging.bbclass: Only clean out the sysroot if we rerun configure, not at ↵Richard Purdie2
setscene time Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-28sstate: Ensure stale stamp files are removed as part of sstate_clean()Richard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27sstate.bbclass: Fix stupid typoRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27sstate.bbclass: No need to dump the contents of the sstate package to stdoutRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27sstate.bbclass: Handle whitespace in the list of files to 'fixup' to resolve ↵Richard Purdie1
log warning Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27sstate.bbclass: Optimise to check if the manifest exists without taking locksRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27rm_work.bbclass: Update to convert stamps to setscene stampsRichard Purdie1
We need to manipulate the stamps when removing WORKDIR to indicte that tasks like compile or install can't just rerun. The most effective method to do this is to convert the layout to match that which would have been the case had the system been build from sstate packages. For example, we'd task stamps like: xxx-1.4.7-r3.do_compile xxx-1.4.7-r3.do_configure xxx-1.4.7-r3.do_fetch xxx-1.4.7-r3.do_generate_toolchain_file xxx-1.4.7-r3.do_install xxx-1.4.7-r3.do_package.emenlow xxx-1.4.7-r3.do_package_write xxx-1.4.7-r3.do_package_write_ipk xxx-1.4.7-r3.do_package_write_rpm xxx-1.4.7-r3.do_patch xxx-1.4.7-r3.do_populate_sysroot.emenlow xxx-1.4.7-r3.do_setscene xxx-1.4.7-r3.do_unpack and after rm_work, we'd have stamps of: xxx-1.4.7-r3.do_package_setscene.emenlow xxx-1.4.7-r3.do_package_write_ipk_setscene xxx-1.4.7-r3.do_package_write_rpm_setscene xxx-1.4.7-r3.do_populate_sysroot_setscene.emenlow We also need to handle stamps in the form xxx-1.4.7-r3.do_package.MACHINE.TASKHASH as used by some signature generators. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27autotools.bbclass: Drop unused autotools_stage_dir dummy functionRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27autotools.bbclass: Only include aclocal directories if the exist, no point ↵Richard Purdie1
in creating them Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26crosssdk: Drop PACKAGES setting as its set in cross.bbclass alreadyRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26sstate.bbclass: Correctly handle empty sstate packagesRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26cross.bbclass: Move sysroot_stage_all function to the only place that uses ↵Richard Purdie1
it now (gcc-cross-intermediate) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-03 08:03:35 +0000