summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
* qemux86_64: Use the core2-64 tuneDarren Hart2014-01-281-1/+2
| | | | | | | | | | | | | | | | | As x86_64 has been "demoted" to an ABI definition rather than a concrete tune file, replace it with core2-64 for the qemux86-64 machine. (From OE-Core rev: 65c1ba225a410d2ee1913d55c6f986db9f54cc8e) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: README: Typographical correctionsDarren Hart2014-01-281-3/+3
| | | | | | | | | | | | | | | | No new content, just correcting a few typographical errors. (From OE-Core rev: 8df13f5013d92954ee76943dad58db75704c3cc5) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: README: Document best practiceDarren Hart2014-01-281-0/+19
| | | | | | | | | | | | | | | | | Describe the expected usage of base architecture tune files and arch-specific files, specifically the stacking of generations. (From OE-Core rev: 282735d7c8fcbd7e354f544c45461b095700fb77) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: README: Whitespace cleanupDarren Hart2014-01-281-44/+44
| | | | | | | | | | | | | | | | | Before making content changes, cleanup the various whitespace errors in this file. Mostly end-of-line whitepsace. (From OE-Core rev: 112e291c14ce4c3b8d074b71e63500dce609784e) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: Remove tune-x86_64.incDarren Hart2014-01-281-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tune-x86_64.inc file is conceptually flawed. x86_64 is more akin to the x86 and x86-32 ABIs defined in arch-x86.inc than it is a concrete tune file, such as i586 or core2 - to the extent that everything but the default tune is defined in the arch-x86.inc file. This becomes very apparant when attempting to include tune-x86_64.inc in the x86 tune hierarchy. Remove the tune-x86_64.inc tune file in favor of it being an ABI definition in arch-x86.inc and relying on the linear hierarchy of concrete cpu-types in tune-i586, tune-core2, and tune-corei7. core2_64 should suffice in lieu of x86_64 for all but a couple esoteric corner cases involving older pre-core2 CPUs. In these cases, if they exist at all, the BSP can replace the include tune-x86_64.inc with arch-x86.inc and set the default tune to x86_64. (From OE-Core rev: d8884649b2b3e76519bc10f5908f98d940a9c0cb) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-corei7: Add support for cpu-type corei7Darren Hart2014-01-281-0/+35
| | | | | | | | | | | | | | | | | | | | | | | | corei7 offers a significant advancement since the previous core2 cpu-type described in the tune-core2 file. From the GCC(1): Intel Core i7 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1 and SSE4.2 instruction set support. This offers optimizations for Nehalem and Silvermont (e.g. Bay Trail) CPUs (and beyond). (From OE-Core rev: 21f8ce2a4b94034284eb74b9c3b4c9cc638511d6) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: Make 32b or 64b explicit in tune name for core2Darren Hart2014-01-281-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | Core2 has both a 32b and a 64b variant. Currently, core2 implies 32b, while core2_64 is the 64b version. This implicit 32b mode will become confusing in later architectures, such as corei7, where it would be natural for people to assume "corei7" meant 64 bit. Rather than carrying forward an implicit 32b mode and rather than changing the naming scheme part way through the architecture hiearchy, make the 32b and 64b variant explicit in the tune name by changing core2 to core2-32. This patch also standardises on using '-' in the names. (From OE-Core rev: 69e6395b8d11e2940892a6293ecbbe645c2a478b) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-core2: Only add the current ARCH to PACKAGE_EXTRA_ARCHSDarren Hart2014-01-281-1/+2
| | | | | | | | | | | | | | | | | Inherit the PACKAGE_EXTRA_ARCHS from i586 and only explicitly add core2 here. (From OE-Core rev: 2a10d570560c37eb1d23cf853c0e541bc08a2878) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-core2: Replace -mtune=generic with -mtune=core2Darren Hart2014-01-281-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | -march specifies which ISA to use. -mtune specifies which cpu-type to optimize instruction ordering for, but not which ISA to use. There are times when it may make sense to specify mtune=generic and use a more specific march, such as core2, but the opposite makes little sense at all: use cpu-type specific ISA, but order the instructions generically. While the -mtune is implied by -march, gcc does not verify it is using -mtune=core2 with: gcc -Q -march=core2 --help=target Explicitly specify -mtune=core2 to be sure. Add a comment header describing the CPUs targeted by this tune file. (From OE-Core rev: 4cd33193b2db6c281275db2fb5cc169181955217) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* i586: Only add the current tune to PACKAGE_EXTRA_ARCHSDarren Hart2014-01-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The generic x86 build supports i586 by default, so this specific tune file technically doesn't add any specific ARCHes to PACKAGE_EXTRA_ARCHS. For consistency, append the current tune to PACKAGE_EXTRA_ARCHS. Since we do not have specific tune files for i386 and i486, just drop them. These could be added to tune-x86 version if there is a need to maintain them, but they really do not belong here. (From OE-Core rev: 1ff914118bdfb19d7f3d794a92ba3735c06ab97b) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x86: Replace ia32 with x86 when referring to the generic architectureDarren Hart2014-01-286-16/+16
| | | | | | | | | | | | | | | | | | | ia32 implies 32bit, while these files provide descriptions for IA32, X86_64, and X32 architectures. The term "x86" fits this used better without resorting to using the term "Intel" which isn't quite right as it excludes things like the tune-c3 file describing a Via CPU. (From OE-Core rev: f5e0a574d87b7dc6466bfe01593fab5aa13464ff) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Change update-alternatives provider to opkg-utilsPaul Barker2014-01-191-3/+3
| | | | | | | | | | | | | | This allows dependencies to be added to the opkg recipe without causing circular dependency loops. As opkg-utils has minimal dependencies it is the best recipe to provide update-alternatives. This partially solves Yocto Project issue 4836. More work is still needed for a complete solution. (From OE-Core rev: 2f18289493f9c2c67ba343fb8e16743bf5dfee24) Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: db can't use pie flags from gcc for security buildSaul Wold2014-01-141-0/+1
| | | | | | | | | [YOCTO #5721] (From OE-Core rev: 0cfe254e7eafed27f512216cccfb7fee76fc0be7) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* separatebuilddir: Drop cmake lines since cmake class has this as default nowRichard Purdie2014-01-141-2/+0
| | | | | | | | The changes to cmake make this unneeded now. (From OE-Core rev: 92472980b816ee9ada502c1965976cb6eedc0a27) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* separatebuilddir: build libproxy and taglib out of the source treeRoss Burton2014-01-141-2/+2
| | | | | | | | (From OE-Core rev: 706084cedc73612af4feb5dd9075f1efb1b7d58c) 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>
* security_flags: add the rest of the grub-efi related packagesSaul Wold2014-01-061-0/+4
| | | | | | | | | [YOCTO #5515] (From OE-Core rev: 840fd855a47b0a557911ae0542ed24a047af6d7b) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add full stop to default DESCRIPTIONPaul Eggleton2014-01-021-1/+1
| | | | | | | | | | | | | SUMMARY should not end with a full stop; however if DESCRIPTION is not set in a recipe and thus defaulted from SUMMARY, the additional DESCRIPTION values for other standard packages e.g. ${PN}-dev look a bit odd without a full stop separating the SUMMARY value and the rest of the text. Add a full stop to avoid this. (From OE-Core rev: 4b022399815f32166c402d458a40afa6470fc776) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: set a default for MACHINE_FEATURESPaul Eggleton2014-01-021-0/+1
| | | | | | | | | | | | | | Ensure that if MACHINE_FEATURES is not set by the machine config that we don't end up with expansion errors during parsing. Technically since the introduction of MACHINE_FEATURES_BACKFILL = "rtc" this is unlikely to be a problem unless "rtc" is also added to MACHINE_FEATURES_BACKFILL_CONSIDERED, however we should be consistent with DISTRO_FEATURES which is defaulted in bitbake.conf. (From OE-Core rev: bf2c8946d96524aaa91ab43762c963ea38ccc342) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Exclude WORKDIR changes from sstate checksumsRichard Purdie2013-12-201-1/+1
| | | | | | | | | | | | | | | The layout of stamp files ensures that changes to WORKDIR mean recipes get rebuilt correctly. Since WORKDIR usually contains MULTIMACH_TARGET_SYS and that depends on tune variables, including WORKDIR in sstate checksums adds a lot of noise to the system for what amounts to no gain. On the other hand, removing it reduces noise, reduces the size of the siginfo files and reduces the amount of processing bitbake has to do. It therefore seems like dropping it from the checksums is an all around win. (From OE-Core rev: 453353e05d027c6a505d1e13a7982718a13bca8b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf-notes: remove meta-toolchain-sdk referencesSaul Wold2013-12-201-1/+0
| | | | | | | | | | | [YOCTO #5676] (From OE-Core rev: 4c81f743eb15604eb389f3ceafe7af7567a02e0d) (From OE-Core rev: 987802907ef702bfec65507b276e166f0aee59ec) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.conf: Require bitbake 1.21.1 as a minumum version for deltask ↵Richard Purdie2013-12-201-1/+1
| | | | | | | | functionality (From OE-Core rev: cdc6dfd497c7a96f8ccd666fe0b8970d5b906786) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: more relocation issuesSaul Wold2013-12-181-0/+6
| | | | | | | | | | | | These are similar relocation R_X86_64_PC32 issues that are solved by removing the -pie flags. [YOCTO #5515] (From OE-Core rev: cd94dd3d9bba32c3fd55959586128b236d1d4e34) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pointercal-xinput: Mark as SIGGEN_EXCLUDERECIPES_ABISAFEOtavio Salvador2013-12-181-0/+1
| | | | | | | | | | | | When including xinput-calibrator, in commit "xinput-calibrator: move it from meta-oe to oe-core" the pointercal-xinput has not been added to the SIGGEN_EXCLUDERECIPES_ABISAFE. This changes adds it to the meta/conf/layer.conf's file list. (From OE-Core rev: 9582ed663d12e635c02c59bff8665c929fa35656) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* external-sourcery-toolchain: removePaul Eggleton2013-12-124-238/+1
| | | | | | | | | | | | | | | | | As per discussion on the mailing list [1], remove this largely unmaintained external toolchain support in favour of the maintained version in meta-sourcery [2]. Also correct the example and documentation.conf entries for TCMODE to match up with this change. [1] http://lists.openembedded.org/pipermail/openembedded-core/2013-December/087133.html [2] https://github.com/MentorEmbedded/meta-sourcery/ (From OE-Core rev: 7603b15415301679bccbcb89af688c211704a43a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: set PREFERRED_PROVIDER and rename runtests_noltp.sh scriptMartin Jansa2013-12-101-0/+2
| | | | | | | | | | | | | | | | | | * ltp installs 2 different runtests_noltp.sh files from different directories into /opt/ltp/testcases/bin/runtests_noltp.sh last one installed wins and causes unexpected changes in buildhistory's files-in-image.txt report, rename them to have unique name as other ltp scripts have. * also define PREFERRED_PROVIDER to resolve note shown when building with meta-oe layer: NOTE: multiple providers are available for ltp (ltp, ltp-ddt) NOTE: consider defining a PREFERRED_PROVIDER entry to match ltp (From OE-Core rev: ec3bb2c2203b2e8bafc1a631f623f858779e20b7) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: update for new image testing variablesRoss Burton2013-12-091-3/+1
| | | | | | | | | | | IMAGETEST is now TEST_IMAGE, and TEST_SCEN and TEST_SERIALIZE don't exist anymore. (From OE-Core rev: ce0b1ea834ee3ab2256b55fcd8b4092e091cf556) 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>
* bitbake.conf/native.bbclass: Use FC instead of F77 for fortranRichard Purdie2013-12-051-2/+2
| | | | | | | | | | | | | gcc tooling appears to be standardising around the FC variable naming. This patch changes the F77 namespace to FC instead and use the default gfortran compiler. If anyone needs the F77 variables or tools, those can still be made on a case by case basis. Also updates local.conf.sample.extended accordingly. (From OE-Core rev: ae8c17be2845eff2be8394a5d9a45e6aa321c33d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Add entry for opensslSaul Wold2013-12-051-0/+1
| | | | | | | | | | | | | | | | | | | | | | It seems we might be stumbling over an obscure linkage issues possibly similar to http://marc.info/?l=openssl-dev&m=130132183118768&w=2 This issue appears for x86-64 systems with the PIE related compiler flags. libcrypto.a(cryptlib.o): relocation R_X86_64_PC32 against symbol `OPENSSL_showfatal' can not be used when making a shared object; recompile with -fPIC The error suggests recompiling with -fPIC, but it is already compiled that way. Disable the PIE flags makes it work for now, I have posted to openssl ML [YOCTO #5515] (From OE-Core rev: 55e1c0e66fd16612016b3e415cbfa4e3051e5a8f) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: grub-efi-natve does not build with flags enabledSaul Wold2013-11-241-0/+2
| | | | | | | | | [YOCTO #5505] (From OE-Core rev: db628ccad9db49d0e83fb534ddfb05a57132f2fa) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ia32-base: Remove cpio and ext3 defaultsRichard Purdie2013-11-221-1/+1
| | | | | | | | | | | | | | | On real IA hardware, neither the ext3 or cpio images are particularly useful or used. cpio is legacy from initramfs and that specific image now overrides FSTYPES accordingly. The size difference in filesystems makes ext3 as a file format less useful, mainly being useful in the qemu case. When needed users can still override the default FSTYPES so having saner defaults makes sense. This improves build times and uses less network bandwidth for builds and releases. (From OE-Core rev: 42484d72ed52a1a6f9d3f5b4bf46a72fbfbc490e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libjson: update to 0.11 and rename to json-cJack Mitchell2013-11-201-1/+1
| | | | | | | | | | | | libjson is now known as json-c. Config.status is removed as it breaks seperate build dir builds. Built without parallel make as it fails, official word is not to bother trying. (From OE-Core rev: 533c1db22eddaaaea7d58d1fc75d608b9ba8122a) Signed-off-by: Jack Mitchell <jmitchell@cbnl.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Remove obsolete/unused MIRROR cruftPhil Blundell2013-11-201-11/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | ADOBE_MIRROR, HANDHELDS_CVS and E_SVN were broken links and not used by any recipe in oe-core. FREEDESKTOP_CVS is no longer useful because all the source code that matters is in git; no recipe in oe-core still uses the CVS repository. E_MIRROR, FREEBSD_MIRROR, FREESMARTPHONE_GIT still point to valid-seeming locations but there are no recipes in oe-core that use them. Any layers which need these variables can define them for themselves. GPE_SVN, GPE_EXTRA_SVN, GPEPHONE_MIRROR and GPEPHONE_SVN are not used by any recipe in oe-core and the corresponding projects seem to be mostly dead upstream. Again, any layers which still wish to use these variables can define them locally. All the above are just wasting space in bitbake's datastore and would be better deleted. (From OE-Core rev: 3b333896c71689c664475d53daed52404bf6b21b) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ia32-base.inc: remove eee-acpi-scripts from MACHINE_EXTRA_RRECOMMENDSPaul Eggleton2013-11-201-1/+1
| | | | | | | | | | We shouldn't bring this in unconditionally for all ia32 machines. (From OE-Core rev: d573d424788d56c6fee02c1ee0cdeb96fe610b85) 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>
* bitbake.conf: remove CPU_FEATURES defaultsPaul Eggleton2013-11-141-3/+0
| | | | | | | | | | This variable has been unused since the tune file overhaul two years ago. (From OE-Core rev: a1d9f2374ede768057fd364da6c0e1eeeb10499f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: remove BOOTSTRAP_EXTRA_* variable defaultsPaul Eggleton2013-11-141-7/+0
| | | | | | | | | | These were for task-bootstrap in OE-Classic and have never been used in OE-Core. (From OE-Core rev: f4692afb518f07e17fbd35a2023877b7041abef9) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Default DISTRO to nodistroRichard Purdie2013-11-122-2/+6
| | | | | | | | | | | | | | | | | An empty distro value leads to OVERRIDES and FILESOVERRIDES containing "::" entries which causes odd issues such as files being included when they shouldn't be. We could put in anonymous python to guard against empty entries but its messy and setting a default value for DISTRO to something harmless is much easier. This patch adds a weak default and ensures the sanity test doesn't complain about it. DISTRO_VERSION and SDK_VERSION are also updated to match. (From OE-Core rev: b7279f99639774674da806d37d252f388f33055f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: update contentsBelen Barros Pena2013-11-041-9/+14
| | | | | | | | | | | | | | | This patch updates descriptions and brings more info for the variable configurations as documented in the OE-Core manual. This file is used by Toaster to display help for the configuration variables. (From OE-Core rev: 98405beddb93490c8a2e9903adc2a510969ed6a9) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add WARN_QA and ERROR_QA to the hash whitelistRoss Burton2013-10-161-1/+2
| | | | | | | | | | I discovered bitbake rebuilding packages because WARN_QA had changed. These variables don't influence the output, so add them to the whitelist. (From OE-Core rev: 96204ae6e1b19783d6a3f8c590890714eaa9e2d9) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* separatebuilddir: remove entries for imake and xorg-cf-filesCristiana Voicu2013-10-141-4/+0
| | | | | | | | | | Imake and the associated xorg-cf-files recipes were removed. (From OE-Core rev: d4e627b846f5b0f435748e9403cb51b553271047) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Remove double slash from PATH_prepend and PKG_CONFIG_DIRMartin Jansa2013-10-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * we correctly have ${STAGING_DIR_NATIVE}${base_sbindir_native} and then double slash in ${STAGING_DIR_NATIVE}/${base_bindir_native} * similar in PKG_CONFIG_DIR where libdir also starts with slash ${STAGING_DIR_HOST}/${libdir}/pkgconfig * also fix double slash in insane.bbclass and staging.bbclass * I was a bit nervous about staging change (in case the / was important in some weird use-case, but the extra slash is there since following commit where other extra slashes were removed only the one before libdir was kept: commit 6ea78d648951e5bbe9669412c0863daaf7f49ca5 Author: Richard Purdie <rpurdie@linux.intel.com> Date: Mon Nov 2 17:10:51 2009 +0000 autotools.bbclass: Separate out useful staging functions into base.bbclass and call from autotools classes * this isn't fixing any real-world issue AFAIK, I was just trying to debug one weird case where debugedit fails with canonicalization unexpectedly shrank by one character and it's easier to grep for '//' without many harmless instances already in run* scripts etc (From OE-Core rev: 0ddaf52e9e344986ae2b016cc068d9eee71b4347) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: update contentsBelen Barros Pena2013-09-241-97/+238
| | | | | | | | | | | | | Documentation.conf is used in WebHob to display information strings about the collected variables. This patch brings the file up-to-date with latest information available from the manual. (From OE-Core rev: b9743c7b130bda3e50cdba4cf260232f1c24abcd) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: don't claim support for IrDA and PCMCIARoss Burton2013-09-241-1/+1
| | | | | | | | | | | QEMU machines don't have virtual IrDA or PCMCIA hardware, so don't claim to support them. (From OE-Core rev: 694ca965eea971077e135cda4e54fa1cb0243233) 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>
* classes/imagetest-qemu: remove old image testing classPaul Eggleton2013-09-221-3/+0
| | | | | | | | | This has now been superseded by testimage. (From OE-Core rev: d469c92394a1a95ae7a45b8b80dc4c2918e0e9a6) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: define WORKDIR in terms of BASE_WORKDIRRoss Burton2013-09-221-1/+2
| | | | | | | | | | To make it easier to move WORKDIR, define it using the new variable BASE_WORKDIR, which is the root of the work directory. (From OE-Core rev: 1eee097f2e29b9d6934711c0b1d32e59e9542f53) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: add virtual/mesa providerRoss Burton2013-09-171-0/+1
| | | | | | | | | | | As there are two alternative mesa recipes (mesa and mesa-gl), there needs to be a virtual provider that recipes that explicitly need Mesa (such as xserver-xorg) can depend on. (From OE-Core rev: 4a407568472d3c87cd2ce11baf199568249640b6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi: fix and enable out-of-tree buildsRoss Burton2013-09-171-3/+2
| | | | | | | | (From OE-Core rev: 6112a07f4e9865f7ae0e5a953669c1adf789f9f0) 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>
* mesa-gl: add GL-only Mesa recipeRoss Burton2013-09-172-0/+2
| | | | | | | | | | | | | | | | | Some machines have hardware-specific GL drivers that do EGL and GLES (many ARM boards). Others have their own EGL/GLES drivers and provide a Mesa DRI driver (EMGD). Previously adding Mesa, for software GL/GLX rendering in the first case and hardware GLX in the second, involved bbappends and changing Mesa to be machine-specific. By adding a just-GL Mesa the machine definition can combine it with the hardware drivers cleanly. (From OE-Core rev: f5a3a4bc33109181c741a2e66c13d0b45566e8fa) 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>
* bitbake.conf/package: Collapse PKGDATA_DIR into a single machine specific ↵Richard Purdie2013-09-142-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | directory Currently we have a hierarchy of pkgdata directories and the code has to put together a search path and look through each in turn until it finds the data it needs. This has lead to a number of hardcoded paths and file globing which is unpredictable and undesirable. Worse, certain tricks that should be easy like a GL specific package architecture become problematic with the curretn search paths. With the modern sstate code, we can do better and construct a single pkgdata directory for each machine in just the same way as we do for the sysroot. This is already tried and well tested. With such a single directory, all the code that iterated through multiple pkgdata directories and simply be removed and give a significant simplification of the code. Even existing build directories adapt to the change well since the package contents doesn't change, just the location they're installed to and the stamp for them. The only complication is the we need a different shlibs directory for each multilib. These are only used by package.bbclass and the simple fix is to add MLPREFIX to the shlib directory name. This means the multilib packages will repackage and the sstate checksum will change but an existing build directory will adapt to the changes safely. It is close to release however I believe the benefits this patch give us are worth consideration for inclusion and give us more options for dealing with problems like the GL one. It also sets the ground work well for shlibs improvements in 1.6. (From OE-Core rev: 1b8e4abd2d9c0901d38d89d0f944fe1ffd019379) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Version bump for DEPLOY_DIR layout changeRichard Purdie2013-09-141-1/+1
| | | | | | | | | Increase the version to signify the layout change of the images in the deploy directory. (From OE-Core rev: 4246e7dd59800a1d6c6d02c00f4e86eeac020767) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: include machine name in DEPLOY_DIR_IMAGEPaul Eggleton2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | This allows a clean seperation between image outputs from different machines, and makes it possible to have convenience symlinks to make the output ready to deploy. This did require some surgery in runqemu; if explicit paths to the image and kernel are not supplied then DEPLOY_DIR_IMAGE needs to be determined from bitbake or set in the environment. However the script does try to avoid requiring it unless it really is needed. Corresponding changes were made in the automated testing code as well. Based on an RFC patch by Koen Kooi <koen@dominion.thruhere.net> (From OE-Core rev: 7e90261aec61f79680b5eaeaf5b18c7b795412a4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-27 12:14:43 +0000