summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* bitbake.conf: Stop providing ${P} and ${PF} by defaultRichard Purdie2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This looks nice at first glance however it turns out to be a bit problematic. Taking make as an example where there are two versions, 3.81 and 3.82, what should "bitbake make-3.81" do? Currently it builds make-3.81 and make-3.82 and breaks in interesting ways. Is that a bitbake bug? Well, it certainly shouldn't try and run the build. Why is it building 3.82 though? Its due to finding a dependency on "make-dev" and then trying to figure out what provides it? The answer is "make" and the default version of "make" is 3.82. So arguably, finding "make-3.81" should infer PREFERRED_VERSION_make = "3.81". Doing so resolved the above problem since now "make" resolves to "make-3.81". So what about if we have Recipe A: DEPENDS = "make-3.81" and Recipe B: DEPENDS = "make-3.82" That is clearly an error, easy. So finally what about if we have Recipe A: DEPENDS = "make-3.81" and Recipe B: DEPENDS = "make" The first recipe infers the PREFERRED_VERSION_make = "3.81" and then forces that version on everything else. Is that desired? Probably not in most cases, at least not silently. As mitigation, we could print a WARNING about this happening. The final part of the problem is that we can ony figure this out within bitbake itself. That means we'd have to teach bitbake about the PN-PV format of PROVIDES which is breaking the separation between bitbake and the metadata. We can't win :(. Nobody that I know of is using or relying on this functionality so perhaps we should just remove it instead which is what this patch does. Opinions? (From OE-Core rev: a87c205bb6cefd5e1a41b8e7ef02b5bfa380e3b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ia32-base: only depend on GL if opengl DISTRO_FEATURE enabledRoss Burton2013-09-111-3/+3
| | | | | | | | | | | As Mesa refuses to compile if the "opengl" DISTRO_FEATURE isn't enabled, mesa-driver-i9xx and the GLX X module have to be conditional in the ia32 machine defintion too. (From OE-Core rev: 8b5c07e6c3b492f56ce9c5f99a732793403d6b36) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: only depend on mesa-driver-swrast if opengl is enabledRoss Burton2013-09-113-3/+3
| | | | | | | | | | As Mesa refuses to compile if the "opengl" DISTRO_FEATURE isn't enabled, mesa-driver-swrast has to be conditional in the QEMU machine defintions too. (From OE-Core rev: 9951e1da6a755f9a46d3a595aa4c2f975aee8f46) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu.inc: remove apm as a MACHINE_FEATURESaul Wold2013-09-091-1/+1
| | | | | | | | | | | APM is not only obsolete, but requires a kernel config enabled and is meaningless for QEMU VM [YOCTO #5121] (From OE-Core rev: b0f8c47b1e808421f03308527beb8bde15644acd) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add SDKPKGSUFFIX to hash whitelistRichard Purdie2013-09-041-1/+1
| | | | | | | | | | The gcc recipes reference this however we account for it in the work directory paths and we don't want recipes depending on the value changing. This avoids unecessary rebuilds when switching SDKs. (From OE-Core rev: 6cdcc543ce8f532a4f66246114241b43821a111e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Don't use deprecated bitbake APIRichard Purdie2013-09-011-1/+1
| | | | | | | | | | These have been deprecated for a long time, convert the remaining references to the correct modules and prepare for removal of the compatibility support from bitbake. (From OE-Core rev: 6a39835af2b2b3c7797fe05479341d71a3f3aaf6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* web-webkit: Drop, we have midori nowRichard Purdie2013-08-301-1/+0
| | | | | | | | | | | This was never a particularly useful browser and is a dead codebase, retire it and suggest midori instead. [YOCTO #2318] (From OE-Core rev: 3883d2cb03fb79fa39a7d85505c79784a996f178) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* SPDX:real-time license scanning and SPDX output.liangcao2013-08-261-1/+50
| | | | | | | | | | | | | | | SPDX integrates real-time license scanning, generates SPDX standard output and license verification information during the OE-Core build process. The existing module includes scanning patched packages and creating package and file level SPDX documents. (From OE-Core rev: 7a37cc81fb95d56b5ac5e5ca22a1900e45717911) Signed-off-by: liangcao <liangcao@unomaha.edu> Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to v3.10Bruce Ashfield2013-08-261-1/+1
| | | | | | | | | | | | Now that the 3.10 kernel has been released we can bump the libc-headers to that version and remove the 3.8 variant. Userspace compatibility is maintained through kernel versions, we also make the single 3.10 version the toolchain default. (From OE-Core rev: 4e79a46254e778f85c00efd4b0085cbaeb6e0d4d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Set the preferred provider for bluezCristian Iorga2013-08-231-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a need for a default provider for bluez now that bluez5 recipe is also present. After the introduction of bluez5 recipe, the following warnings are displayed: "NOTE: multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) NOTE: consider defining a PREFERRED_PROVIDER entry to match libasound-module-bluez" Upon debug, bitbake shows: DEBUG: checking PREFERRED_PROVIDER_bluez4 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101-r5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7-r0 (value None) against ['bluez4', 'bluez5'] Bitbake is faced with the question "what should provide libasound-module-bluez?" which is a runtime name. It needs to try and find a PREFERRED_PROVIDER entry which matches this but those use *build time* naming. So it converts "libasound-module-bluez" into the canonical ${PN} of bluez4 and bluez5 and then tries to look those up. What it actually should do is go one step further of mapping bluez4/bluez5 into the virtual/bluez but that does not happen. Bug opened on this issue: YB5044 https://bugzilla.yoctoproject.org/show_bug.cgi?id=5044 [YOCTO #5030] (From OE-Core rev: 6f07d066074b1e01ff3c16408812e6b6d5e531ac) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Drop darwin8/darwin9 usageRichard Purdie2013-08-231-4/+0
| | | | | | | | | | | There were darwin8/darwin9 overrides spinkled in the code from times gone by. Lets settle on the darwin override and remove the others since its pointless duplication. We always inject darwin into OVERRIDES if needed in the darwin8/9 cases. (From OE-Core rev: 8d5e6eed7802a6056f9eaa50a85e3eee00fe2742) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Work around dev symlink problems on darwinRichard Purdie2013-08-231-6/+9
| | | | | | | | | | | | | | | | | | | | | | On darwin, we have: libxxx.dylib -> libxxx.Y.dylib compared to Linux which has: libxxx.so -> libxxx.so.Y Our ordering of PACKAGES with -dev first and then ${PN} makes it impossible to match the files correctly using simple globbing. This makes darwin targets completely broken since both the libs and the dev symlinks end up in ${PN}-dev. Whilst this commit is a hack, it at least puts the files into ${PN} and allows the builds to be used. Symlinks don't take up much space so this isn't the end of the world. I'm open to better solutions to this. (From OE-Core rev: 51c3dbe2df45096bbd7866adabb08e114952ff13) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/classes/gcc: Don't hardcode -nativesdkRichard Purdie2013-08-231-1/+2
| | | | | | | | | | | | | Hardcoding -nativesdk as the sdk package architecture is inflexible. We may have multiple different target OS and we need a way to be able to separate them. Turning this into a configurable value allows the flexibility we need to build different SDKMACHINEs with different OS targets. The commit should have no behaviour change, just makes things more configurable. (From OE-Core rev: a2110e86b98d646e136de9ec6b8e668079b0d4f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gettext: Improve USE_NLS handling for nativesdk/crosssdk/cross-canadianRichard Purdie2013-08-231-0/+1
| | | | | | | | | | | | | | | | The gettext handling of USE_NLS has become a bit tricky to understand, or alter from the SDK context. This patch introduces a SDKUSE_NLS which can be set to configure a given SDK/ADT to use NLS or not. This is independent of the target system NLS usage. The code in gettext.bbclass is therefore simplified and the classes themselves now set USE_NLS to appropriate values. No NLS is used for native, cross and crosssdk since it is never used there and would just increase build time. (From OE-Core rev: fe634d47449899f7424adb77ff5bc7ddf8a07a47) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_rpm.bbclass: NO_RECOMMENDATIONS supportMark Hatle2013-08-222-0/+4
| | | | | | | | | | | | | | | | | | Add NO_RECOMMENDATIONS support. A way to disable all recommended packages from being installed. This will help shrink the size of the resulting filesystem. Add documentation on NO_RECOMMENDATIONS and BAD_RECOMMENDATIONS. Note, using NO_RECOMMENDATIONS has side effects such that kernel-modules may not have been installed. A user will need to manually add to their image any kernel-modules required to be on the image for functionality. (From OE-Core rev: 0341bfa886ea851f5a394051545b4e624d8003dd) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@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-11-15 00:35:30 +0000