summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/meta
Commit message (Collapse)AuthorAgeFilesLines
* populate_sdk: install UTF-8 locales in SDKsRoss Burton2018-04-051-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | As glibc 2.27 can't read older locale-archives, SDKs using glibc 2.27 on hosts using glibc earlier than 2.27 won't be able to find any locales, so bitbake won't start and Python can't use UTF-8. So by default install all locales into the SDK. Special-case Extensible SDKs by installing no locales as they ship glibc in a buildtools, and that will have the locales. Locale installation requires cross-localedef, so add that to DEPENDS. Also remove the explicit en_US addition in buildtools-tarball as it is now redundant. (From OE-Core rev: 96896568d197cd06302713c24c0f7d91bfaea6c1) (From OE-Core rev: 385dd115d00aabbcd970ef6b62353480d87a5a55) (From OE-Core rev: 065ddf01b914805298fb1ddf83ae32b5018856b3) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: add symlinks and unfsd to support Eclipse pluginPaul Eggleton2016-10-071-1/+1
| | | | | | | | | | | | | | The Yocto Project Eclipse plugin requires that runqemu and unfsd are accessible within the SDK, and indeed the standard SDK has these. This turns out to be fairly easy to do - we just need to add unfsd and symlink it, runqemu and a few other scripts into the SDK's bin directory. Fixes [YOCTO #10214]. (From OE-Core rev: 9007e0e3fce7e09b043fead54b17f69c1661d162) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: ensure corret TOOLCHAIN_CONFIGSITE_NOCACHE valueChen Qi2016-09-261-0/+2
| | | | | | | | | | | | | Expand TOOLCHAIN_CONFIGSITE_NOCACHE value immediately before inheriting cross-canadian to avoid HOST_ARCH being changed from TARGET_ARCH to SDK_ARCH, thus ensuring its correct value. [YOCTO #10255] (From OE-Core rev: 1e13d1fd22186af5544e7248dc12635cd2f2e08b) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools/uninative-tarball: Fix deployment overlap issuesuninative-1.4Richard Purdie2016-09-232-4/+4
| | | | | | | | | | | | | | | | | | We still have problems where deploying SDKMACHINE=i686 can cause removal of SDKMACHINE=x86_64 artefacts. The reason is that x86_64 is a BUILD_ARCH as well as an SDK_ARCH and the manifest namespaces overlap. To fix this, set PACKAGE_ARCH and the stamp-extra-into to include SDK_OS. SDK_OS may not be entirely correct but it is what sstate.bbclass uses for nativesdk and fixing that is a separate issue. This is confirmed to resolve artefact problems on the AB which have been delaying a new uninative release. (From OE-Core rev: 1dbc6ec4ca061570d2482c9abebcf720298db9b7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: improve stamp independenceJoshua Lock2016-09-231-2/+13
| | | | | | | | | | | | | | buildtools-tarball shouldn't be regenerated when MACHINE changes, nor should variants for other SDKMACHINE be removed from the deploy directory when SDKMACHINE changes. Remove target architecture dependencies so that deploy artefacts can overlap. (From OE-Core rev: b7d1a310f6b880e92b124a78af3c948abaab4236) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: Make stamp independentRichard Purdie2016-09-221-0/+6
| | | | | | | | | | | | | | | | The uninative tarball only contains nativesdk compoents. It should not get regenerated when MACHINE changes for example. Currently its sstate arch is also incorrect so changing SDKMACHINE results in other variants being removed from the deploy directory. This patch removes the target architecture dependencies so that deploy artefacts can overlap and it doesn't continually rebuild. This also fixes various autobuilder/release artefact issues we're having as a result of these issues. (From OE-Core rev: 6edd0b8dccc6e1e21f2ef87013e2e0a40d19b0d6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: add SDKMACHINE to stamps-extra-infoJoshua Lock2016-09-211-1/+1
| | | | | | | | | | Otherwise the stamps for x86-64 and i686 uninative tarballs match and we can't deploy both to the DEPLOYDIR. (From OE-Core rev: fee426ae0c2b27925b05b856ada676958ee10869) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: add SDKMACHINE to stamps-extra-infoJoshua Lock2016-09-211-1/+1
| | | | | | | | | | Otherwise the stamps for x86-64 and i686 uninative tarballs match and we can't deploy both to the DEPLOYDIR. (From OE-Core rev: 2a9603759fe87d6326c145f6213ffffeb6afc6ae) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball/uninative-tarball: Fix for working with populate_sdk ↵Richard Purdie2016-09-042-2/+11
| | | | | | | | | | | | | | | | under sstate control Firstly, these recipes are not target (MACHINE) specific so they should by SDK_ARCH based, not PACKAGE_ARCH. Also fix use of SDK_DEPLOY -> SDKDEPOLYDIR after other recent changes. Together these fixes avoid various build failures and ensure the tarballs only get built once rather than multiple times. (From OE-Core rev: 894c9b6ded702897ae4084ef75959cdc8cc6f7a3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-ide-support: inherit nopackagesJackie Huang2016-09-031-1/+1
| | | | | | | | | | | The recipe is to generate an environment script in do_populate_ide_support for using an IDE and it doesn't generate packages at all, so inherit nopackages (From OE-Core rev: 68e06f1782253d1b9c8d8c4d818bc4915b93d257) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: allow including toolchain in eSDK on installPaul Eggleton2016-07-261-0/+15
| | | | | | | | | | | | | | | | | | | | | If we're to completely replace the standard SDK with the extensible SDK, we need to be able to provide the standard toolchain on install without doing anything other than installing it, so that you can install the SDK and then point your IDE at it. This is particularly applicable to the minimal SDK which normally installs nothing by default. NOTE: enabling this option currently adds ~280MB to the size of the minimal eSDK installer. If we need to reduce this further we would have to look at adjusting the dependencies and/or the sstate_depvalid() function in sstate.bbclass which eliminates dependencies, or look at reducing the size of the artifacts themselves. Implements [YOCTO #9751]. (From OE-Core rev: ed0d8ed72370df694f720cc13897493478dc1de9) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-extsdk-toolchain: add meta-recipe to install toolchain into eSDKPaul Eggleton2016-07-261-0/+13
| | | | | | | | | | | | | | | | | | Add a meta-recipe to bring the toolchain into the extensible SDK. This was modelled on meta-ide-support but some adjustments were needed to the dependency validation function in sstate.bbclass to ensure that all of the toolchain gets installed into the sysroot. With this, after installing a minimal eSDK you only need to run the following after sourcing the environment setup script to get the toolchain: devtool sdk-install meta-extsdk-toolchain Addresses [YOCTO #9257]. (From OE-Core rev: 8110806b1b5534ae830a4fdd1a5293c86a712d0b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testexport-tarball: Add default value for TEST_EXPORT_SDK_PACKAGESRichard Purdie2016-06-151-0/+2
| | | | | | | | | | | | | | Otherwise we see parsing failures in the default configuration: ''' Nothing RPROVIDES '${TEST_EXPORT_SDK_PACKAGES}' (but /media/build1/poky/meta/recipes-core/meta/testexport-tarball.bb RDEPENDS on or otherwise requires it) ''' (From OE-Core rev: 79aa2d34590660c788e0a6c56ef1bb1a5dda5119) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testexport-tarball.bb: Add recipeMariano Lopez2016-06-071-0/+56
| | | | | | | | | | | | | | | | | | This new recipe is used when exporting runtime test outside packages that won't be installed in the testing system but are required for the runtime testing. This new recipe is almost identical to buildtools-tarball, but is able to define the SDK packages in local.conf. [YOCTO #7850] (From OE-Core rev: fbcd1f9ed6144a76ff6a556d23af30f04c39bfa0) (From OE-Core rev: d787cd34da1cba52f5ecf68b7f55aa5550ed5e71) Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/lib: Update xrange -> range for python3Richard Purdie2016-06-021-1/+1
| | | | | | | | xrange() no longer exists in python 3, use range() (From OE-Core rev: d022b4335100612d6596cc4c4956cb98ed5873cc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* signing-keys: set SUMMARY instead of DESCRIPTIONPaul Eggleton2016-05-301-1/+1
| | | | | | | | | | | Short descriptions should go into SUMMARY (DESCRIPTION will get the same value if not set. (From OE-Core rev: 8fe0b683800b352f17c6ff0465c6eaa5bb8196b9) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: add nativesdk-locale-base-en-usRobert Yang2016-05-191-0/+1
| | | | | | | | | It is required by python3's bitbake. (From OE-Core rev: 342701f25db0943fb1038ac3741a1feaab8458fd) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: replace nativesdk-python with nativesdk-python3Robert Yang2016-05-191-5/+5
| | | | | | | (From OE-Core rev: 97b5b150b3d3e82a5a42c1ea4351eed60aba7906) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: remove nativesdk-python-pexpectRobert Yang2016-05-191-1/+0
| | | | | | | | | | | | | | | | It was added for testing, and not needed any more after: 4a8a74c62836a20610daf029d4cec0b3087758b2 Author: Robert Yang <liezhi.yang@windriver.com> Date: Mon Mar 21 02:25:50 2016 -0700 gpg_sign.py: get rid of pexpect So remove it. (From OE-Core rev: 8ae1a5328e7ca820611fc1911195ebce6dc92237) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* signing-keys: Use SYSROOT_DIRS to add dirs to stage in sysrootPeter Kjellerstedt2016-05-131-4/+2
| | | | | | (From OE-Core rev: 4a37960e504d6c0bbd0f4c088bef8f3a99beab6a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Drop unneeded LIC_FILES_CHKSUM valuesPaul Eggleton2016-05-111-1/+0
| | | | | | | | | | With the changes to insane.bbclass we don't need LIC_FILES_CHKSUM to be set for recipes that don't actually pull in any source. (From OE-Core rev: fc14e794c53f94158a5e6d6a8644656875639d0c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-world-pkgdata: add LIC_FILES_CHKSUMRobert Yang2016-05-061-0/+2
| | | | | | | | | | Fixed: ERROR: meta-world-pkgdata-1.0-r0 do_populate_lic: QA Issue: meta-world-pkgdata: Recipe file does not have license file information (LIC_FILES_CHKSUM) [license-checksum] (From OE-Core rev: 6e0ce5ada01da34ad619b2a918097b543b089437) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: set INHIBIT_DEFAULT_DEPSRobert Yang2016-04-191-0/+3
| | | | | | | | | | The recipe doesn't need any default deps. (From OE-Core rev: 25f904b4f0f5a049ffabc7b3613d5902099d4ae0) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: fix perl being included when building with ipkPaul Eggleton2016-04-182-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to some logic within opkg, a package with the name matching a dependency will always win over a package with that name in RPROVIDES - even if there is an RCONFLICTS (which is silently ignored), higher feed priority and version. The end result is that buildtools gets perl installed instead of the nativesdk-buildtools-perl-dummy package and that perl (with missing dependencies) gets used in preference to the host one, which is precisely what we were trying to avoid. This is almost certainly a bug in opkg, especially as the other package's dependencies aren't properly installed under these circumstances either. However, specifying RREPLACES works around this, and with no apparent side-effects is probably the safest solution for now. At the same time I noticed that in prepending to SDK_PACKAGE_ARCHS we were actually ending up with a low priority for the dummy package feed rather than a high one, so change to append it instead. This has no effect on the packages that get installed at the moment, but should be done in case the package manager behaviour changes to factor in the feed priority in future. Fixes [YOCTO #9469]. (From OE-Core rev: b18134ddaf949b4f001a1613ab876aed6324040a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball.bb: fix unexpected operatorRobert Yang2016-04-181-1/+1
| | | | | | | | | | | | | Fixed: run.create_sdk_files.45747: 131: [: =: unexpected operator The SDKMACHINE is not set by default. (From OE-Core rev: 528388c3cef027d436fc794c73d57a247521c238) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball.bb: set TOOLCHAIN_NEED_CONFIGSITE_CACHE to nullRobert Yang2016-04-141-0/+3
| | | | | | | | | | | | buildtools-tarball doesn't need config site, set TOOLCHAIN_NEED_CONFIGSITE_CACHE to null so that no target recipes will be built when bitbake buildtools-tarball. (From OE-Core rev: 1c187fd7f722b01e0284e4d368f6f9366e9c2f0b) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add texinfo (for makeinfo)Richard Purdie2016-04-051-0/+1
| | | | | | | | | | | | | | | Initially I was reluctant to do this however makeinfo is a dependency of the buildsystem and only adds around 400kb to the buildtools-tarball so it likely makes sense to add it. This allows people to use the project on older environments. Need to enable nativesdk-texinfo but this seems straightforward. [YOCTO #8990] (From OE-Core rev: 5e290201e13a685818ff03ad9cd6679977e560d1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* signing-keys: create ipk packageIoan-Adrian Ratiu2016-03-111-1/+14
| | | | | | | | | | Store the ascii armored pubkey generated using gpg_sign.export_pubkey() in its own package. (From OE-Core rev: 9dab5725dace0c54f4c5ed892d18e2d41cca71b5) Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: Add glibc-gconv-iso8859-1 for guileRichard Purdie2016-03-071-0/+3
| | | | | | (From OE-Core rev: a8181c2d3a9e51569d77ab2ad9950b27a1113294) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: respect SDKMACHINE when buildingRoss Burton2016-02-281-4/+6
| | | | | | | | | | | | | So that a single machine can build multiple architectures for the uninative-tarball respect SDK_ARCH instead of BUILD_ARCH. This means a x86-64 host can build a i686 uninative-tarball by setting SDKMACHINE=i686. (From OE-Core rev: 11b0e7e1cb29fd1fbe06bdb5606a55b92ecdcc89) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adt-installer: Drop since its replaced by the extensible SDKRichard Purdie2016-02-281-1/+1
| | | | | | | | | | | | | | The extensible SDK replaces adt-installer so this can be removed now, all future effort in this direction will be placed onto that. This includes a layer version change so the autobuilder knows when to stop building adt-installer. [YOCTO #6404] (From OE-Core rev: c413164c03bdce38f41e63ad2a27dc6108521b9a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* signing-keys: Make signing keys the only publisher of keysRandy Witt2016-02-261-18/+43
| | | | | | | | | | | | | Previously the keys were put into the os-release package. The package indexing code was also deploying the keys rather than only using the keys. This change makes signing-keys.bb the only publisher of the keys and also uses standard tasks that already have sstate. (From OE-Core rev: 1e38068ac38dfd067655dfd41464e28439179306) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sign_rpm.bbclass: do not store key details in signer instanceMarkus Lehtonen2016-02-191-10/+6
| | | | | | | | | | | | | Refactor the LocalSigner class. Do not store keyid or passphrase file in the signer object as they are only needed for some of the methods. For example, the newly added verify() method does not need any key parameters and export_pubkey only uses keyid. (From OE-Core rev: e2412294b6b1d3a80ee97a0706613349edc51d33) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy.bb: Fix variable expansion in python codeAníbal Limón2016-02-111-2/+2
| | | | | | | | | | | | | Since python expansion of bb data variables is disable in order to provide a standard interface usage for expand variables this variables aren't expanded now so change to call d.expand('${VAR}'). This API expansion change was causing to install perl in nativesdk. (From OE-Core rev: cb7a3f997d7278eb6e31ea79ad933a7ab1717977) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/lib: new module for handling GPG signingMarkus Lehtonen2016-01-261-14/+12
| | | | | | | | | | | | | | | | | Add a new Python module (oe.gpg_sign) for handling GPG signing operations, i.e. currently package and package feed signing. The purpose is to be able to more easily support various signing backends and to be able to centralise signing functionality into one place (e.g. package signing and sstate signing). Currently, only local signing with gpg is implemented. [YOCTO #8755] (From OE-Core rev: 9b3dc1bd4b8336423a3f8f7db0ab5fa6fa0e7257) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: add option to bring in pkgdata for worldPaul Eggleton2016-01-241-0/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a variable SDK_INCLUDE_PKGDATA which you can set to "1" to include pkgdata for all recipes in the world target. There are a couple of uses for this: 1) If you use "devtool add" to add a recipe that builds something which depends on anything in world, the dependency can then be correctly mapped to the recipe providing it and that recipe can be added to DEPENDS, since we have the pkg-config and shared library dependency data within pkgdata. 2) You'll be able to search for these recipes and any files they package for the target with "devtool search" since that also uses pkgdata This of course assumes you've tailored world through EXCLUDE_FROM_WORLD to only include recipes you'd want built in your distro, but I think that's a reasonable assumption; failing that there is a WORLD_PKGDATA_EXCLUDE variable that you can set to exclude any recipes you don't want. Note that this patch relies on functionality implemented in a recent BitBake patch and will not work without it. Implements [YOCTO #8600]. (From OE-Core rev: 67149ea097d6fab7496b43e85a40853f40bd527e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy: Bump PRRichard Purdie2015-12-181-0/+2
| | | | | | | | | | Recent changes to this recipe caused automated PR increments to break, regressing package feeds. The only way to recover is to bump PR, so do this centrally to fix anyone affected. (From OE-Core rev: dacdb499d31cb2e80cca33cba9d599c8ee983dc4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball.bb: 32bit tools need pseudo 32bit libraryJuro Bystricky2015-12-121-0/+6
| | | | | | | | | | | | | | | | | | "pseudo" does not build 32 bit library by default on 64 bit host, but the 32 bit library is needed when using 32 bit development tools (buildtools-tarball) running on a 64 bit host. Building of the library can be forced if the environment variable NO32LIBS is set to "0". Hence for 32 bit buildtools we export the environment variable NO32LIBS="0" and NO32LIBS is also added into BB_ENV_EXTRAWHITE (if not already there). [YOCTO#8581] (From OE-Core rev: 1c20e66428df10000741c25dddb7a2b1fd55ba42) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy: properly set PACKAGE_ARCHPaul Eggleton2015-12-111-2/+0
| | | | | | | | | | | | | | | Turns out I did a silly thing in OE-Core revision 9b1831cf4a2940dca1d23f14dff460ff5a50a520 and forgot to remove the explicit setting of PACKAGE_ARCH outside of the anonymous python function; the original bug was apparently fixed but the functionality of allarch.bbclass was being disabled because it was able to see that PACKAGE_ARCH was not set to "all" - which was what I was trying to ensure. (From OE-Core rev: a25ab5449825315d4f51b31a634fe6cd8f908526) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy: fix rebuilding when SDKMACHINE changesPaul Eggleton2015-12-011-2/+9
| | | | | | | | | | | | | | | | | | | This recipe produces an empty dummy package (in order to satisfy dependencies on perl so we don't have perl within buildtools-tarball). Because we were inheriting nativesdk here the recipe was being rebuilt, but having forced PACKAGE_ARCH to a particular value the packages for each architecture were stepping on eachother. Since the packages are empty they can in fact be allarch (even though they won't actually go into the "all" package feed). It turns out that nheriting nativesdk wasn't actually necessary either, so drop that. Fixes [YOCTO #8509]. (From OE-Core rev: 9b1831cf4a2940dca1d23f14dff460ff5a50a520) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add 850 codepage to uninative-tarballRandy Witt2015-10-271-0/+1
| | | | | | | (From OE-Core rev: 6211c8060d408134dfa6c00b23b517c439e4c1e7) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package signing: automatically export public keysMarkus Lehtonen2015-10-271-0/+45
| | | | | | | | | | | | Automatically export public key(s) of the signing key(s) from the gpg keyring. Adds a new simple recipe that does the actual task of exporting the keys. This patch makes the RPM_GPG_PUBKEY and PACKAGE_FEED_GPG PUBKEY settings obsolete. (From OE-Core rev: 23b30c34581948e1ea02c25cbf7b9194d7e49fb8) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-ide-support: No need to mark as nostamp anymoreRichard Purdie2015-10-011-1/+0
| | | | | | | | | With the modern checksum infrastructure, this is no longer needed (much in the same way images no longer need this). (From OE-Core rev: 30e83bbc3f90b4cd4caf8ad7ca847267ae50cf7e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add inherit toolchain-scriptsRichard Purdie2015-07-121-0/+1
| | | | | | | | | The core class used to have this inherit but its being phased out, add the inherit directly where we need it instead. (From OE-Core rev: bdd546a8a492d386afdcc24e9540b0b88e9cd230) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: Ensure we append to the default ↵Richard Purdie2015-06-231-1/+1
| | | | | | | | | | | | TOOLCHAIN_NEED_CONFIGSITE_CACHE The toolchain-scripts class was changed to assign to the variable using ??= which allows users to override it. We therefore need to _append instead of += to have the change take effect as intended. (From OE-Core rev: d589777a4d423b1f0c9953900bd79772d15ee4af) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: delete the packagedata taskChen Qi2015-04-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This task is meaningless for uninative-tarball as the package task has been deleted. Besides, sometimes it would cause problems. To reproduce, use the following command. bitbake uninative-tarball -c cleansstate && bitbake uninative-tarball && bitbake uninative-tarball -c clean && bitbake uninative-tarball The error is something like below. File: 'sstate.bbclass', lineno: 33, function: sstate_installpkg 0029: bb.build.exec_func(f, d) 0030: 0031: for state in ss['dirs']: 0032: prepdir(state[1]) *** 0033: os.rename(sstateinst + state[0], state[1]) 0034: sstate_install(ss, d) 0035: 0036: for plain in ss['plaindirs']: 0037: workdir = d.getVar('WORKDIR', True) Exception: OSError: [Errno 2] No such file or directory [YOCTO #7597] (From OE-Core rev: 8f905077aaed3dbeeed04787add1cf725fa87bdc) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_base: Show title in SDK installerPaul Eggleton2015-04-241-0/+2
| | | | | | | | | | | | Show a friendly title when running the SDK installer, so the user knows what SDK they are installing. The title is controlled by the SDK_INSTALLER_TITLE variable and includes the distro name and SDK version by default. (From OE-Core rev: 0af913887f4c0a79c6b950bd5d57c06333520a14) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: fix dependency on patchelfTyler Hall2015-03-251-1/+2
| | | | | | | | | | | | | | | | | DEPENDS doesn't actually add the dependency on patchelf-native to the populate_sdk task. SDK_DEPENDS does this, but move the append to after inheriting the base class so it does not get overwritten. Without this, uninative-tarball fails to build in a clean workspace on a system without patchelf. [YOCTO #7467] (From OE-Core rev: 0631c2b52432ddf86292351d605b65941d2a8be2) Signed-off-by: Tyler Hall <tylerwhall@gmail.com> Acked-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-pexpect: Adds this module to buildtools, since it is needed by some ↵Alejandro Hernandez2015-03-221-0/+1
| | | | | | | | | | | of the automated runtime test code. [YOCTO 7279] (From OE-Core rev: 5c183f69b65478a98982e544728d00269efe3e22) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: add extensible SDKRandy Witt2015-02-241-0/+12
| | | | | | | | | | | | | | | | | | | | This bbclass will create an SDK with a copy of bitbake and the metadata and sstate for the target specified for the task. The idea is to let "system" developers both work on applications and then test adding them to an image without having to switch between workspaces or having to download separate items. Rather than running bitbake directly however, the primary way of running builds within the extensible SDK is to use the "devtool" command. The rest of the build system is fixed via locked shared state signatures, and thus only the recipes you have added get built. (From OE-Core rev: bf81d6bb7f6df5405b8f2148e2a22e0030c12757) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Chen Qi <Qi.Chen@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-13 11:22:57 +0000