summaryrefslogtreecommitdiffstats
path: root/meta/classes
Commit message (Collapse)AuthorAgeFilesLines
* staging.bbclass: Also don't bother staging locale files, its pointlessRichard Purdie2012-07-191-2/+2
| | | | | | (From OE-Core rev: 782ce542a8250133cf1b1bc32927c17cd09cfca3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Ensure the task starts from a clean directoryRichard Purdie2012-07-191-0/+1
| | | | | | | | | | | I found that some files were not getting removed from the sysroot, despite them clearly being removed by the recipe. I found SYSROOT_DESTDIR is only ever copied into, not cleaned. This patch ensures its empty when the task starts so that stale files are removed and not persisted. (From OE-Core rev: 8a313f6d32ae0bdac0393887712b09f1b685aaa5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Don't stage doc/manpage/info filesRichard Purdie2012-07-191-0/+2
| | | | | | | | | | | | There is no point in having doc, manpage or info files in the staging directory. They just bloat the sstate package size and waste time as they're copied around. We never used to stage these but it crept in when we started staging $datadir. This patch corrects that so they're removed and stop making it into the sysroot. (From OE-Core rev: ec4fea852bde2294ad7a7a703ccf11eb9a109c31) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory.bbclass: Fix python whitespaceRichard Purdie2012-07-191-247/+247
| | | | | | (From OE-Core rev: 51d402fa0ec9e4adf10c3dac2a69a385ee720fa1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_ipk.bbclass: Fix python whitespaceRichard Purdie2012-07-191-219/+219
| | | | | | (From OE-Core rev: 8a6c2278377edd63af54a469f0fb2b23f90e056b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove a number of unneeded import os/bb callsRichard Purdie2012-07-1916-92/+54
| | | | | | | | | | The bb and os modules are always imported so having these extra import calls are a waste of space/execution time. They also set a bad example for people copy and pasting code so clean them up. (From OE-Core rev: 7d674820958be3a7051ea619effe1a6061d9cbe2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-scripts: Remove extra - from ar/nm command namesRichard Purdie2012-07-191-4/+4
| | | | | | | | TARGET_PREFIX already has the dash included. (From OE-Core rev: ca30b6587841f5e9a42aaedb8e0b89ff5a4a6a37) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove the - between ${TARGET_PREFIX} and ar/nm for the env script, as this ↵Martin Ertsaas2012-07-191-2/+2
| | | | | | | | | will make autotools look for arm-none-linux-gnueabi--ar instead of arm-none-linux-gnueabi-ar. (From OE-Core rev: 6434fc102e73ed81d2092e4c4ba5f9fb806545c8) Signed-off-by: Martin Ertsaas <mertsas@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert tab indentation in python functions into four-spaceRichard Purdie2012-07-1935-3648/+3647
| | | | | | (From OE-Core rev: 604d46c686d06d62d5a07b9c7f4fa170f99307d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Fix kernel location after STAGING_KERNEL_DIR changeRichard Purdie2012-07-181-1/+1
| | | | | | | | | | | This catches up with the STAGING_KERNEL_DIR location change and uses the correct variable to future proof this issue. [YOCTO #2783] (From OE-Core rev: 28715eff6dff3415b1d7b0be8cbb465c417e307f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity: display the parsed PATH when complaining about CWD elementsRoss Burton2012-07-181-1/+2
| | | | | | | | | | Many people don't understand the nuances of PATH, so help them by clarifying the warning and displaying the parsed PATH element-by-element. (From OE-Core rev: 47e6ab41f0f84e6bed7d337ebf96c954ec6909e8) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add git-native to ASSUME_PROVIDEDRichard Purdie2012-07-181-1/+1
| | | | | | | | | | | | | | | Originally, git was something new, not installed everywhere and had commandline stability problems. This has changed and git it no longer makes sense to continually build this when the system installed version is likely sufficient. This speeds up build since recipes no longer have to wait for git-native to build if they're fetched from a git:// SRC_URI. Also add git to the sanity checks and drop the no unneeded svn reference. (From OE-Core rev: 79e24186481770181565a18d177584d0d72399fe) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-ide-support: Add native qemu support for meta-ide-supportJessica Zhang2012-07-181-1/+1
| | | | | | | | | | | | [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. (From OE-Core rev: 3ea597249c18d73417abe7d7a9d32bba00499914) Signed-off-by: Jessica Zhang <jessica.zhang@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-scripts: Sync the SDK/ADT values to the build systemMark Hatle2012-07-171-18/+45
| | | | | | | | | | | | | 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. (From OE-Core rev: 2bd0aaf98c5d586638d82f5f22c1c24122a889a3) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* useradd.bbclass: Fix for multilib buildsRichard Purdie2012-07-171-1/+1
| | | | | | | | | | | | | | The class adds a setscene dependency on base-passwd as well as adds this to DEPENDS. The DEPENDS version will be auso-converted to include MLPREFIX whilst the setscene dependency will not. This result in errors about non-existent tasks. This patch ensures MLPREFIX is added when it is needed and fixes various build failures. Whether we should have two base-passwd recipes in a multilib system is a question which would need to be addressed by future changes. (From OE-Core rev: 22dff7f36e985f9f7275b47e874147bc7bdc9473) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: Dont package kxgettext.oKhem Raj2012-07-171-1/+1
| | | | | | | | | | | | | | kxgettext.o is generated when building ppc kernels so we end up with packaging errors like > ERROR: QA Issue: Architecture did not match (20 to 62) on > /work/virtex5-poky-linux/linux-xilinx-2.6.38-r00/packages-split/kernel-dev/usr/src/kernel/scripts/kconfig/kxgettext.o (From OE-Core rev: 77278bd23617834c7f90b3b24a9945ec081dbb38) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mirrors: Add debian archive snapshot mirrors to search listKhem Raj2012-07-171-1/+3
| | | | | | | | | | | | | I ran across this problem when apt 0.7.14 was not fetchable from regular debian mirrors and existing snapshot mirror did not have it either since we did not use proper syntax so it was not hitting that. (From OE-Core rev: 5a5f67e5486837b4d7e5a89cc27a5c8f8c8598ef) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: add GNUmakefile to the list of possible makefile namesRoss Burton2012-07-171-1/+1
| | | | | | | | (From OE-Core rev: b753eab1028ba48dfdcdeefa07f3f30743f3ee45) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* crosssdk/nativesdk: Ensure EXTRA_OECONF_FPU is unsetRichard Purdie2012-07-172-0/+4
| | | | | | | | | | | | | | | | If EXTRA_OECONF_FPU is left set, certain ARM variables related to hard-float can get pulled in and trigger rebuilds of the crosssdk code. The best solution is to simply force the variable to a known correct value for the SDK targets currently supported in the same way as TARGET_FPU. There is some slight rearrangement of the gcc code to ensure the variable is always used to call the fpu function. (From OE-Core rev: 410990445ada8cdcfaec4e6fa5791cee9a5b8983) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Move crosssdk before cross to ensure correct variables are setRichard Purdie2012-07-171-2/+2
| | | | | | | | | | | | | | | | There was a bug showing up where the crosssdk recipes were being installed as machine specific in the sstate-control directory. This turned out to be due to the architecture fields used by sstate being set incorrectly. The problem is that the crosssdk inherits the cross class. It therefore needs to be listed in this if statement block before the cross check, not after. This should resolve some package architecture issue of crosssdk sstate files. (From OE-Core rev: 79fe28e6033273f9632ca7549d1599d3fd1463ef) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image_types.bbclass: Default XZ_COMPRESSION_LEVEL to -e -6Andrei Gherzan2012-07-171-1/+1
| | | | | | | | | | | | | Having XZ_COMPRESSION_LEVEL on -e -9 and -T 0 will make xz eat more than 6Gb memory. Reduce this to -6 to make xz to use about 471Mb on the tested machine. (From OE-Core rev: cfd201ecda95d00bc5d70aa5045c649b98ffe8b8) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image_types.bbclass: Add XZ variable to set number of threads to be used ↵Andrei Gherzan2012-07-171-1/+2
| | | | | | | | | | | | | | while compressing Default this variable to 0. This will make xz use as many threads as there are CPU cores on the system. (From OE-Core rev: 81c8e8a81e90ce95042e9fff8bac6fa011c416d1) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image_types.bbclass: Fix COMPRESS_CMD for xz to redirect compressed data to fileAndrei Gherzan2012-07-171-1/+1
| | | | | | | | | | | | Having -c modifier makes xz to output the compressed data to stdout. In this way the needed data will be in the do_rootfs log. Redirect data to ${IMAGE_NAME}.rootfs.${type}.xz . (From OE-Core rev: 7ceea61636d6a6f886002e3c29941da3356157ac) Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cpan.bbclass: Fix CCFLAGS.Xin Ouyang2012-07-171-1/+2
| | | | | | | | | | | | | | | | | | | We should not just replace CCFLAGS with CFLAGS while compiling, because this may cause run-time errors with perl's DynaLoader.pm. Tested on qemux86 with new libnet-libidn-perl bb recipe: root@qemux86:~# perl -e "use Net::LibIDN" Not a CODE reference at /usr/lib/perl/5.14.2//DynaLoader.pm line 213. END failed--call queue aborted at /usr/lib/perl/vendor_perl/5.14.2//Net/LibIDN.pm line 213. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. (From OE-Core rev: 855211ae7a224f96663862d4a0e58a90d945dd48) Signed-off-by: Xin Ouyang <Xin.Ouyang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/rootfs_deb: use more reliable check for package existencePaul Eggleton2012-07-171-1/+1
| | | | | | | | | | | | | It turns out "apt-cache showpkg" does return some information when a package does not exist but another package recommends it, which can occur for empty *-dev packages; so use "apt-cache policy" with a different line count instead. (From OE-Core rev: ac62761a9cacdfd0225d2db5a75584e6c85469a8) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: Allow overriding of debugedit starting pathPeter Seebach2012-07-171-1/+1
| | | | | | | | | | | | | | | In the usual case, the computed path used for debugedit to fix up path references for the target filesystem is correct. However, prebuilt binary components, such as prebuilt toolchains, can have debug paths that do not reflect paths within the local build directory. Providing an override lets us continue to use the standard debugedit logic in package.bbclass. (From OE-Core rev: 32b1fde106bf423873a4a56e1111f230494e2d4a) Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package install failure on systems without /sbin/ldconfigAmy Fong2012-07-171-2/+2
| | | | | | | | | | | | | | | | | | Package install failures due to issues in post install rules. package_do_shlibs only looks for libraries in a directory "lib", this should be modified to the variable baselib. ldconfig_postinst_fragment failure observed on systems without /sbin/ldconfig [ -x /sbin/ldconfig ] && /sbin/ldconfig results in the post install rule returning a failure. Modify to if [ -x /sbin/ldconfig ]; then /sbin/ldconfig; fi (From OE-Core rev: 3f85ab6d0d05a4e34fe73fa343d2b3b942fc69b7) Signed-off-by: Amy Fong <amy.fong@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache: Ensure CCACHE_DIR is cleaned by do_clean taskRichard Purdie2012-07-101-0/+2
| | | | | | | | | | This ensures a rebuild does really build from scratch when ccache is in use. [YOCTO #2696] (From OE-Core rev: ddf52d0161096b089fad8f3ace69b6515d7b7226) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: add non-santized kernel providesBruce Ashfield2012-07-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the kernel version string uses characters or symbols that need to be santized for the package name, we can end up with a mismatch between module requirements and what the kernel provides. The kernel version is pulled from utsrelease.h, which contains the exact string that was passed to the kernel build, not one that is santized, this can result in: echo "CONFIG_LOCALVERSION="\"MYVER+snapshot_standard\" >> ${B}/.config <build> % rpm -qp kernel-module-uvesafb-3.4-r0.qemux86.rpm --requires update-modules kernel-3.4.3-MYVER+snapshot_standard % rpm -qp kernel-3.4.3-myver+snapshot-standard-3.4-r0.qemux86.rpm --provides kernel-3.4.3-myver+snapshot-standard = 3.4-r0 At rootfs assembly time, we'll have a dependency issue with the kernel providing the santizied string and the modules requiring the utsrelease.h string. To not break existing use cases, we can add a second provides to the kernel packaging with the unsantized version string, and allowing the kernel module packaging to be unchanged. RPROVIDES_kernel-base += "kernel-${KERNEL_VERSION}" % rpm -qp kernel-3.4.3-myver+snapshot-standard-3.4-r0.qemux86.rpm --provides kernel-3.4.3-MYVER+snapshot_standard kernel-3.4.3-myver+snapshot-standard = 3.4-r0 (From OE-Core rev: 7be043178f5b9d16d9a06696bc0b96689f202a8d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* utils.bbclass: add helper function to add all multilib variants of a ↵Richard Purdie2012-07-091-0/+9
| | | | | | | | | | | | specific package This is useful for the scenario where we want to add 'gcc' to the root file system for all multilib variants (From OE-Core rev: 7cd54693363882854cd026ebe071e9f2e03d364e) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/license: fix manifest to work with debPaul Eggleton2012-07-091-1/+1
| | | | | | | | | | | | | | Prepend the license manifest creation call to ROOTFS_POSTPROCESS_COMMAND instead of appending to ROOTFS_POSTINSTALL_COMMAND. The latter is not implemented for the deb backend (and probably ought to just be removed completely), and by using _prepend we can still ensure it occurs before package info is removed (and before buildhistory in case it is needed there in future). (From OE-Core rev: 56fafe083fdb63f156a081344fb1d836e3182bf0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.bbclass: the tmpdir can't be longer than 410Robert Yang2012-07-091-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There will be errors when the length of the tmpdir is longer than 410: 1) Longer than 420: Can't exec "/bin/sh": Argument list too long at /usr/lib/perl/5.10/IO/File.pm line 66. This error happens on both Ubuntu 10.04 and 10.10 when the pkg needs run "autoreconf", this is because it passes many files with absolute path to aclocal, aclocal passes them to perl, this is a limitation of the perl on Ubuntu 10.04 and 10.10, and the perl-native is not ready at this very early stage. 2) Longer than 490: bitbake/lib/bb/persist_data.py", line 197, in connect(database=...) > return sqlite3.connect(database, timeout=5, isolation_level=None) OperationalError: unable to open database file This error happens on Ubuntu 10.04, 10.10 and Fedora 17. This is because the length of the database in sqlite3 module (host's) can't be longer than 490 (or little smaller). The python-native is not ready at this very early stage. The 2 errors are host related, I think that limit the length of the TMPDIR to 410 is OK for most of the build, rarely build sets TMPDIR's longer than 410. [YOCTO #2434] (From OE-Core rev: ebcf949853ff667478a1ea1d3f1f8f41d643e708) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib: Enable multilib remapping for SDK generationMark Hatle2012-07-091-0/+6
| | | | | | | | | | | | Enable the remapping for SDK generation, this is required to be able to create an SDK that targets an alternative multilib. Note, this work does not finish SDK/multilib support, but it is one more step toward making it work properly. (From OE-Core rev: d66d2bdf6214939e8b131f47db2f35d3c64e7dd2) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_rpm: Avoid duplicate package generation failuresMark Hatle2012-07-091-5/+5
| | | | | | | | | | | | | When constructing a multilib based image, it's possible to end up with the same package listed in multiple steps of the install. During resolution we use the --replacepkgs option to avoid errors, as the resulting install solution will be as expected. (We do not enable the replacepkgs option for the final install step, only the generation of the install solution.) (From OE-Core rev: 68ea7d827710ae7c5cf402887d4c12319038e064) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_rpm: Sync multilib configuration with rootfs_rpmMark Hatle2012-07-092-5/+11
| | | | | | | | | | | | An anonymous python chunk configures some multilib settings for both populate_sdk_rpm and rootfs_rpm. The two classes should contain identical versions to ensure that the generated multilib configuration is the same for the SDK and the rootfs. (From OE-Core rev: 0f60722ef460fa826e4f02e7457004e64ca41d76) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bootimg: Use STAGING_KERNEL_DIRDarren Hart2012-07-061-1/+1
| | | | | | | | | | | | | | | bootimg.bbclass using STAGING_DIR_HOST/kernel instead of STAGING_KERNEL_DIR, resulting in build failure of live images. | install: cannot stat `/usr/local/dev/yocto/fishriver-test/build/tmp/sysroots/fishriver/kernel/bzImage': No such file or directory Replace it with STAGING_KERNEL_DIR. (From OE-Core rev: 8f16811a8d51982a8b3d70e6087aef4a41926840) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Tested-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* prexport.bbclass: Fix typo in warning: "AUROPR" -> "AUTOPR".Robert P. J. Day2012-07-041-1/+1
| | | | | | | (From OE-Core rev: 0b79c730f3e5c3c5329e439dffd137f2605b6cba) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image_types: Add elf image typeRaymond Danks2012-07-041-1/+17
| | | | | | | | | | | | On x86, an ELF image file may be stored as a coreboot payload. The image file is constructed, using the mkelfimage utility, from a kernel and an initrd. (From OE-Core rev: 93e9de4e27919f59b6783d53f314df6e49ccb436) Signed-off-by: Raymond Danks <ray.danks@se-eng.com> Acked-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: enable the use of package_qa_handle_errorSaul Wold2012-07-041-3/+7
| | | | | | | | | | | | | | | This will allow the reporting of these errors as either WARNINGs (default) or ERRORs if installed_vs_shipped is added to the ERROR_QA of the policy file (such as a <distro_name>.conf file. V2: found the code I had intended to send instead of that other junk, was just not watching what I pushed on that one, sorry. (this is edit in no in the actual commit message) (From OE-Core rev: 20d4205a4e408b6a99db392d4df458156113106a) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib_package: use PACKAGE_BEFORE_PNSaul Wold2012-07-041-2/+1
| | | | | | | | | | | Since this check effective is not a change becase the package order that was in this file has not really changed no PR Bumps are needed. (From OE-Core rev: d807d5dd5bd0e161057ee115256dc050dbe8609b) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel: Add kernel headers to kernel-dev packageDarren Hart2012-07-041-15/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [YOCTO #1614] Add the kernel headers to the kernel-dev package. This packages what was already built and kept in sysroots for building modules with bitbake. Making this available on the target requires removing some additional host binaries. Move the location to /usr/src/kernel Before use on the target, the user will need to: # cd /usr/src/kernel # make scripts This renders the kernel-misc recipe empty, so remove it. As we use /usr/src/kernel in several places (and I missed one in the previous version), add a KERNEL_SRC_DIR variable and use that throughout the class to avoid update errors in the future. Now that we package the kernel headers, drop the kernel_package_preprocess function which removed them from PKGD. All *-sdk image recipes include dev-pkgs, so the kernel-dev package will be installed by default on all such images. (From OE-Core rev: 6125ea40d4483965f793bd847b3ce14b668a5b1e) Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/classes: Update recrdeptask fields for recursive dependency handling ↵Richard Purdie2012-07-043-14/+7
| | | | | | | | | | changes in bitbake This also deletes the buildall task since I seen usecases for it. (From OE-Core rev: 8229fb5d7205f5e5b198ab2860fbcc02054476eb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image/core-image: Handle conflicting IMAGE_FEATURES.Lianhao Lu2012-07-032-1/+27
| | | | | | | | | | | | | | | | | IMAGE_FEATURES such as 'ssh-server-dropbear' and 'ssh-server-openssh' can't be both enabled. User can use the following variables to define the relationship of image features: IMAGE_FEATURES_REPLACES_foo = "bar" means including image feature "foo" would replace the image feature "bar". IMAGE_FEATURES_CONFLICTS_foo = "bar" means including both image features "foo" and "bar" would cause an parsing error. (From OE-Core rev: e36d12a9c1cf69540079e48a1dfadbc343758e48) Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Add cross-canadian-${TRANSLATED_TARGET_ARCH} to the license ↵Mark Hatle2012-07-031-1/+1
| | | | | | | | | | | | exclusion list This appears to be an oversight in the original implementation. All of the host package types were being ignored except for the SDK cross-canadian type. (From OE-Core rev: 750f99d4e2c805985cd87a2358b0625a808ecf4d) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: Add support to build the SDK in parallel with the imageMark Hatle2012-07-036-0/+14
| | | | | | | | | | | | | | | | | | When building an image recipe, you can now build a companion SDK by calling the populate_sdk task: bitbake -c populate_sdk core-image-minimal Note: there are still issues w/ the SDK not working completely with multilibs. A lock is required between rootfs and populate_sdk activities to prevent configuration file clashes and similar package management problems in ipk and deb based systems. (RPM already had a lock for a different reason.) (From OE-Core rev: a0de2a56f19ae4d8cd88e46e96917a7a019fe1ab) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: Allow a package to skip per file dependency generationMark Hatle2012-07-031-0/+3
| | | | | | | | | | | | | Most of the time skipping per file dependency generation is a bad idea, but when building a nativesdk or similar you may be required to pickup host dependencies. These host dependencies can not always be reconciled within the scope of other nativesdk components, so if we skip them we can facilitate this unique situation. (From OE-Core rev: a1ca125de55a8e7cab402e2ba5737a56d4e890c2) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libc-common: Allow -dbg package to append, and not just set package variablesMark Hatle2012-07-031-3/+3
| | | | | | | | | | | | | The libc-common attempts to rewrite the package information in a way similar to debian.bbclass. When it does this, it should be appending to the dependency variables (RPROVIDES, RREPLACES, and RCONFLICTS), instead of simply setting a hard coded value. Otherwise the lib package can not tailor the dependency variables to suite it's needs. (From OE-Core rev: fa1c7b797593cbd5e82dc264bde2667620eb0515) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools.bbclass: When configure fails, dump the config.log files the logsRichard Purdie2012-07-031-1/+8
| | | | | | | | | | | | | | | | | When configure fails, it usually says "see config.log" yet nobody ever shares the config.log file meaning the person trying to help invariably has to ask for more information. This patch dumps all the config.log files into the main bitbake log files when configure fails, meaning all the information is present to help someone debug such failures. It does make the log rather larger but this is preferable to not having enough information in most cases. [YOCTO #2463] (From OE-Core rev: 7ad08f5b73aa949a877adc5641b4bb1d007de750) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk: enable basic multilib supportMark Hatle2012-07-032-10/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. (From OE-Core rev: 42545ffbb37f2646a2a8c20999c21d3300e24f59) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base.bbclass: Change to using task specific dependsMark Hatle2012-07-031-2/+4
| | | | | | | | | | | | If we combine the do_populate_sdk with the image generation, we want to avoid the dependency processing unless do_populate_sdk is run. This requires the bitbake change to implement task based rdepends. (From OE-Core rev: 5fa9f980248e7813ce74f48a29c4b7d94e308cf9) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-24 23:56:20 +0000