summaryrefslogtreecommitdiffstats
path: root/meta/conf/layer.conf
Commit message (Collapse)AuthorAgeFilesLines
* layer.conf: Extend recipes not to install without explict dependenciesRichard Purdie2021-10-111-1/+11
| | | | | | | | | | | | | | | | There are several dependencies which recipes have which are not needed at runtime, only at build time. Extend the list of these from bison to include quilt, patch, meson, autoconf, automake and ninja which should reduce the amount of data being included in native sysroots. This speeds up and reduces the sstate needed for image builds for example. If this change breaks recipes, it probably means they're missing an explicit DEPENDS on something in this list which is a bug in the recipe. (From OE-Core rev: 8e26252b45b7660c7c67c702411bdec187a76ffc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Override changes mean we're only compatible with honisterRichard Purdie2021-08-021-1/+1
| | | | | | | | | Due to the override changes, we only allow compatibility with honister and not hardknott. (From OE-Core rev: 72c04cb3ca78208a135275d6dd43ad500b663cb5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to add post 3.3 release honister seriesRichard Purdie2021-04-181-2/+2
| | | | | | (From OE-Core rev: c0f43f19fecfd16f973c2d2f8227106c46b451bb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Drop gatesgarth from the layer series namesRichard Purdie2021-03-201-1/+1
| | | | | | | | | The time has come to encourage people to update actively maintained layers to use the new series name. (From OE-Core rev: 737e3e608e64fc9ba67facc3dd2dd30497266f1e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Add gatesgarth back for now to allow for transitionRichard Purdie2021-03-151-1/+1
| | | | | | (From OE-Core rev: 60bb29725473497f57396ef32c6dc13b89b8a45d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update for hardknott release seriesRichard Purdie2021-03-151-2/+2
| | | | | | (From OE-Core rev: d430bf39f2f2ecdf989b33f7405751844d783fc5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: fix syntax error in PATH settingMatt Madison2020-11-131-1/+1
| | | | | | | | | | | | | | | | Commit 05a87be51b44608ce4f77ac332df90a3cd2445ef introduced a Python conditional expression when updating PATH that generates syntax warnings in bitbake-cookerdaemon.log: Var <PATH[:=]>:1: SyntaxWarning: "is not" with a literal. Did you mean "!="? Fix this by using the more appropriate '!=' comparison operator. (From OE-Core rev: 2e753a12cf6bb98f9e0940e5ed6255ce8c538eed) Signed-off-by: Matt Madison <matt@madison.systems> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: fix sanity error for PATH variable in extensible SDK workflowSourabh Banerjee2020-10-171-1/+3
| | | | | | | | | | | | | | | | Sanity checker reports following error for the PATH variable, when bitbake -e <recipe> command is run in an extensible SDK workspace. PATH contains '.', './' or '' (empty element), which will break the build In case of extensible SDK, PATH variable is formed with two consecutive ':' as bb.utils.which(d.getVar('PATH'),'bitbake') call returns an empty string. This change adds ':' if BITBAKEPATH is a non empty string. (From OE-Core rev: 05a87be51b44608ce4f77ac332df90a3cd2445ef) Signed-off-by: Sourabh Banerjee <sbanerje@codeaurora.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Switch to gatesgarth only in preparation for releaseRichard Purdie2020-10-171-1/+1
| | | | | | | | Update the core layer release series to gatesgarth in readiness for release. (From OE-Core rev: d2e0d82f3e34a6c49066e39775572c5b8cd3c392) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: Drop gcc-cross-initial, gcc-crosssdk-initial referencesDouglas Royds2020-09-141-1/+1
| | | | | | | | | | | Further to 5b2fd1c724 Also a few remaining references in comments and in distro_alias.inc (From OE-Core rev: 35d4dd42477f316b6af889a0aec16439693e0849) Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* allarch: Add missing allarch ttf-bitstream-veraDaniel Gomez2020-08-061-0/+1
| | | | | | | | | | allarch is missing in ttf-bitstream-vera recipe. Add it and include the recipe in the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS list. (From OE-Core rev: 31c02477a4fb91f19f8c3ef3f8bc9a20e416c859) Signed-off-by: Daniel Gomez <daniel@qtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: fix adwaita-icon-theme signature change problemChangqing Li2020-07-271-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | allarch package adwaita-icon-theme inherit both allarch and gtk-icon-cache, since commit 31e3d34c8a9c3e8481aa837aa0bf52adf095fe62 [gtk-icon-cache.bbclass: add runtime dependency], it start depend on non-allarch packages gdk-pixbuf and gtk+3, which make it's signature changes when machine changed. like for task do_prepare_recipe_sysroot: "Hash for dependent task gdk-pixbuf/gdk-pixbuf_2.40.0.bb:do_populate_sysroot changed from a72aba8432699c8ce4ca1f71833ef14a89ffde0ea4063e37b9d819fdb1e407f4 to 1ad4e1bd76921b71482657f3b017184e9ade8e2a0b9f43ad64ed2dda83b1520f" the only way to fix this is remove the task dependency. SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS not work in class, so add it in layer.conf. Maybe we have other recipes under other layers have similar problem, we can only add one by one to its layer.conf, seems not a good idea. but add *->pixbuf will influence other packages (From OE-Core rev: ec0888d73d7e7f811961f50f334c72fbc6b1d401) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Bump OE-Core layer versionJoshua Watt2020-06-031-1/+1
| | | | | | | | | | | | | The commits 910ffaf5be ("pyelftools: Import from meta-python") and a96f815c53 ("pycryptodome: Import from meta-python") moved recipes from meta-python to oe-core. In order for this to be communicated with users, bump the LAYERVERSION so that meta-python can key of it in its LAYERDEPENDS. (From OE-Core rev: 2d503b27e7c88cee9a37c79c4605c77b11f230b6) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Move to gatesgarth namingRichard Purdie2020-05-181-2/+2
| | | | | | | | | We're still compatible with dunfell from the core perspective so that is left for compatibility (probably for the next week or two). (From OE-Core rev: 1e79324f8290b820fee034b0d4a8c353027879da) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Drop zeus compatibility for dunfell releaseRichard Purdie2020-03-291-2/+2
| | | | | | (From OE-Core rev: 8930cd153084f58c2c1c8950dc0ddce786db548b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Allow compatibility with zeus for nowRichard Purdie2020-03-151-1/+1
| | | | | | (From OE-Core rev: 1970c5f7838ff10cd6243e1624553bdc46e89fad) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to LAYERSERIES_CORENAME to dunfellRichard Purdie2020-03-151-2/+2
| | | | | | | | Update the layer core name to the new release name. (From OE-Core rev: 090bb3b44ba0cc01c29942c00d43e910d1ff735e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Consider shared-mime-info and desktop-file-utils siggen safeKhem Raj2020-02-281-0/+2
| | | | | | | | | | | | | | These are added as dependencies by mime class, which could be inherited along with allarch and dependencies silently go into target specific recipes and which then can result in sstate hash signature mismatches when the allarch recipes are reused for another arch [YOCTO #13805] (From OE-Core rev: 510015ac81df969f690d6c8661b00bebe73b7fca) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update for zeus seriesRichard Purdie2019-10-081-2/+2
| | | | | | (From OE-Core rev: a5c9709b8da6e7ad62167b5036e7f454a62aa83e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Remove weston-conf from SIGGEN_EXCLUDE_SAFE_RECIPE_DEPSKhem Raj2019-09-191-1/+0
| | | | | | | | | This recipe is gone (From OE-Core rev: 3a8e60bb36631ba2b32213c234ec7b4e1e2544d5) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston-init: Add possibility to run weston as non-root userKhem Raj2019-09-191-0/+1
| | | | | | | | | | | | | | | | | | | These changes are from meta-96boards primarily Launch the session via a udev rule based on what kind of display device is available delete weston-conf and move the fuctionality into weston-init other layers are doing same weston-init installs machine specific weston.ini therefore mark is machine specific now (From OE-Core rev: aa3bced2e1de2f4ba507aa014835b06edccc138a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Whitelist lttng-tools->lttng-modules dependencyRichard Purdie2019-05-271-0/+1
| | | | | | | | | | | The API between lttng-tools and lttng-modules is safe, whitelist it as the dependency fixes tools failures. This needs a hack in the multilib class as right now there is no way to know if a given recipe is a kernel module or not. This needs to be revisited. (From OE-Core rev: 584e713bf7f6885a13c440cd45c0f469feb3a694) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: add PACKAGECONFIG for nfc, fix MACHINE_ARCH signature when l2tp is ↵Martin Jansa2019-04-231-0/+1
| | | | | | | | | | | | | | | | | enabled * import 2 fixes from LuneOS * with l2tp PACKAGECONFIG enabled connman depends on MACHINE_ARCH xl2tpd: === Comparing signatures for task do_package_write_ipk.sigdata between hammerhead and mako === ERROR: connman different signature for task do_package_write_ipk.sigdata between hammerhead and mako NOTE: Starting bitbake server... Hash for dependent task xl2tpd/xl2tpd_git.bb.do_packagedata changed from 6312d5711b5c2c1a85ee235d09bf37a8ec00f7ad9e7248c087bb83ef1d5bd078 to c0d3ef52b37bda945d8b2a015980ddb8fe7b4b3dca3d82d71a84176cc5125142 Unable to find matching sigdata for /OE/build/luneos-master/webos-ports/meta-openembedded/meta-networking/recipes-protocols/xl2tpd/xl2tpd_git.bb.do_packagedata with hashes 6312d5711b5c2c1a85ee235d09bf37a8ec00f7ad9e7248c087bb83ef1d5bd078 or c0d3ef52b37bda945d8b2a015980ddb8fe7b4b3dca3d82d71a84176cc5125142 (From OE-Core rev: ba89fea0e443e1492000b7114f32edf15819a151) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to warrior release name seriesRichard Purdie2019-04-021-2/+2
| | | | | | (From OE-Core rev: 13e45fffb66c7cb7ba0d07bed063c0c5ce57004b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache.bbclass: Refactor it to make it more reliableRobert Yang2019-01-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous ccache.bbclass has the following problems: - It uses host's ccache for native recipes, but this may not work on some hosts, for example, it nerver works on my Ubuntu 14.04.4, there are always build failures (m4-native failed at do_configure, and others will also be failed if I disable CCACHE for m4-native) - native/nativesdk/cross/crosssdk recipes use host's ccache, but target uses ccache-native, this may confuse user. - The target recipes may use both host's ccache and ccache-native, this may cause unexpected problems and be hard to debug. This is because ccache-native is in SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS, so ccache-native may not be present when rebuild target recipes, and then it would use hosttools/ccache, but the previous ccache files were generated by ccache-native. - Target recipes can't use ccache when no ccache is installed on the host: CCACHE = "${@bb.utils.which(d.getVar('PATH'), 'ccache') and 'ccache '}" After refactored: All types recipes (native, target and others) will use ccache-native except ccache-native itself, host's cache won't be used any more. It is more reliable now, which will work everywhere when ccache-native can be built. And now we need use "CCACHE_DISABLE = '1'" to disable ccache for the recipe rather than "CCACHE = ''" since we set CCACHE in anonymous function, and d.getVar('CCACHE') works after "CCACHE ??=" which is set in bitbake.conf, so we can't check whether CCACHE is set or not in anonymous function since it is always set. Use CCACHE_DISABLE to disable it would be more clear. (From OE-Core rev: b25271b65262f70d849a4861da216c9be6c54d53) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Drop virtual/libc-for-gccRichard Purdie2018-12-261-1/+0
| | | | | | | | | We no longer have special "libc" for gcc so we can rely on plain virtual/libc and reduce the complexity in the dependencies. (From OE-Core rev: 122217b421f749b5fef52bea44ad6e04bc8f8d3a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: Split out machine specific configurationMark Hatle2018-10-281-0/+1
| | | | | | | | | | | | | | | Weston needs to be configured to load the fbdev driver when run on a QEMU system. Other MACHINEs may want to also provider their own configuration as well.. Adding a new RRECOMMEND configuration package will allow this, but avoid installing empty packages/files in the majority case where it is not needed. Add maintainer entry as well. (From OE-Core rev: 0f43ea8510ae6148a49eb25accac407b6b301b43) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Remove items that made this machine (qemu) specificMark Hatle2018-10-211-0/+1
| | | | | | | | | | | | | | | | Create a new systemd-conf recipe to contain the specific system/machine configuration items. This new package is now machine specific. Without doing this trying to create a single system with multiple BSPs, one of which was qemu based, would result in the systemd -and- everything that dependend upon systemd to have their hash changed. The hash changing means lots of rebuilds, but worse if it's a package based system each different machine ends with a new PR value and a newly generated package. (From OE-Core rev: d3395418758ed414eee3e95e13d2d8bc5dca88cc) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Drop sumo from LAYERSERIES_CORENAMESRichard Purdie2018-10-011-1/+1
| | | | | | | | | | | Prepare for release and drop sumo for the compatible list of layer names. This will mean other layers need updating to continue to indicate compatibility with master but that is intentional at this part of the release cycle, we want layers to indicate compatibility and show they're up to date. (From OE-Core rev: 9ec5a8a0f86510f7aae572dfb79e8bda73d4e0fc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Add thud to LAYERSERIES_CORENAMESRichard Purdie2018-09-241-2/+2
| | | | | | | | | | | With the release approaching, add thud to LAYERSERIES_CORENAMES and update oe-core to use this release series. "sumo" will be removed during M4 in the next couple of weeks so people need to start updating their master layers in preperation for release. (From OE-Core rev: 986792481fa005fe136fd4b4e388042492b1ad8a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Avoid indirect autoconf-archive-native dependenciesChangqing Li2018-08-211-0/+3
| | | | | | | | | | | remove the indirect dependcy of autoconf-archive-native via SSTATE_EXCLUDEDEPS_SYSROOT to avoid not needed .m4 installed into sysroot, which may cause compile problem. (From OE-Core rev: d23156460e2b8f6684bd3005d7fa09b2c73e522e) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Avoid indirect bison-native dependencies (via ↵André Draszik2018-08-161-0/+6
| | | | | | | | | | | | | | | | | | SSTATE_EXCLUDEDEPS_SYSROOT) Avoid adding bison-native to the sysroot without a specific dependency in the recipe. This means indirect dependencies (e.g. X -> Y -> binutils-cross -> bison-native) no longer meet the dependency incidentally. This improves determinism and avoids build failures when people switch to external toolchains. Based on an idea by Richard Purdie: http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146324.html (From OE-Core rev: b7edc20cc2dd82989bd9561f860cb25478a40f69) Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping ↵André Draszik2018-08-161-0/+2
| | | | | | | | | | | | base-passwd|shadow-sysroot recipes Use the newly introduced SSTATE_EXCLUDEDEPS_SYSROOT for specifying the base-passwd|shadow-sysroot recipes to be excluded from a recipe sysroot. (From OE-Core rev: 68e502e9063a88532fe0154f152ba408f0091900) Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping *-initial recipesAndré Draszik2018-08-161-0/+5
| | | | | | | | | | Use the newly introduced SSTATE_EXCLUDEDEPS_SYSROOT for specifying the *-initial recipes to be excluded from a recipe sysroot. (From OE-Core rev: 6706bad52f9311ea79c534ee90014c3216992999) Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update LAYERSERIES rocko -> sumoRichard Purdie2018-04-061-2/+3
| | | | | | | | Also set LAYERSERIES_COMPAT for core (we're compatible with ourself). (From OE-Core rev: 4aa43cd844781a07a2dbf17f21ed35c6a0100d02) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: add -bootconf recipes to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPSCalifornia Sullivan2018-03-061-0/+2
| | | | | | | | | | The bootloaders depend on these to be functional in the non-deploy case, but changes in them don't require rebuilding of the packages. (From OE-Core rev: e102f771dee8d07320ffaf8f39288c5a73626364) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: add busybox-inittab to SIGGEN_EXCLUDERECIPES_ABISAFEDenys Dmytriyenko2018-03-041-0/+1
| | | | | | | | | Similar to sysvinit-inittab (From OE-Core rev: a673d5bbf7e4db6de9a5151df041e6c5db7e413e) Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: Move hardcoded native toolsJoshua Watt2018-03-011-0/+5
| | | | | | | | | | Now that SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS supports the wildcard syntax, these exclusions no longer need to be hardcoded (From OE-Core rev: 891ca3c891f2ed5476442442bd9784ba10b9a94d) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: add install moduleCalifornia Sullivan2017-11-301-0/+4
| | | | | | | | | | | | | | The non-EFI counterpart for installation was previously missing for initramfs-framework. This simply puts the normal install script in the correct location for initramfs-framework to make use of it. Partial fix for [YOCTO #12346]. (From OE-Core rev: f9d7cf30b12cbc5f642a11c0511dc1dc3ccf1aa5) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: remove the recipeAlexander Kanavin2017-11-091-1/+0
| | | | | | | | | | Perf is the preferred solution, and oprofile is difficult to maintain against musl. (From OE-Core rev: 5f470aed944c941b339652961a13266389288739) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/conf/layers.conf: Add ca-certificates as ABISAFEMark Hatle2017-09-131-0/+1
| | | | | | | | | | | | | | | | | meta-oe was doing this before, but it was triggering a yocto-compat-script failure during the signature checking. The ca-certificates changing is ABISAFE, as the certificates themselves do not modify the compiles behavior of the applications. This should permit easier upgrades without as much rebuilding. The original value was set in meta-oe by commit ff7a4b13c4efeffc5853a93c6ff7265fa3d6c143. (From OE-Core rev: 583dca290c230fbc981c41fe91e8abeff616e633) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: bump PR and fix install-efi and setup-live modulesCalifornia Sullivan2017-09-121-4/+4
| | | | | | | | | | | | | | | | | | | | Bump initramfs-framework PR, as it was missed in the previous initramfs-framework patch. These modules are shell scripts so they can be allarch. Fix the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS in layer.conf, as these dependencies moved from the main recipe to these modules. Finally, set the PR to 4 in the new module recipes to avoid breaking package feeds. Fixes [YOCTO #12024]. (From OE-Core rev: d8af496dde699fadb2b21ff45cd20cf31e8abaf7) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: Change recipe to be allarchOtavio Salvador2017-08-311-1/+5
| | | | | | | | | | | | | | | There is no COMPATIBLE_HOST in the recipe neither it makes sense for this to be machine specific. Possibly, initramfs-framework's based modules may be machine specific but if there is the case they can just RDEPENDS on initramfs-framework-base and provide the specific module as another recipe. (From OE-Core rev: 9a661bca9d9dd03627a5efaea0f9247394f05b0e) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/conf/layer.conf: bump layer version for LSB changesRoss Burton2017-06-281-1/+1
| | | | | | | | | | | As oe-core has just dropped a number of recipes that were for LSB conformance, bump the layer version so we can also remove meta-qt4 from the autobuilder. (From OE-Core rev: 179b7ae2511974173ae4aa72dfb49384ff69c2e5) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.confRichard Purdie2017-06-121-0/+2
| | | | | | | | | | | This means mismatched layers are more clearly identified to the user in cases where compatibility has not been tested. This is perhaps not as needed for the core repository (other than CORENAMES) but lets lead by example. (From OE-Core rev: cde66d5eac8e5c2821ba225dc4be4af4e0581652) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add HOSTTOOLS_DIR for ${TMPDIR}/hosttoolsPeter Kjellerstedt2017-05-011-1/+1
| | | | | | | | | | | The path to where to install and find the tools copied from the host environment is already used in a couple of places. This warrants it to get its own variable. (From OE-Core rev: 8164c466943ffedff399009bf5547dba4f06d6c8) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base/bitbake.conf: Filter contents of PATH to only allow whitelisted toolsRichard Purdie2017-03-111-0/+2
| | | | | | | | | | | | | | | | | | | | | | We currently have a determinism problem in that the host tools present in PATH can influence the build. In particular, the presence of pkg-config on the build host can mask missing pkgconfig class dependencies. This adds in a new HOSTTOOLS variable and then uses it to set up a directory of symlinks to the whitelisted host tools. This directory is placed as PATH instead of the usual /usr/bin:/bin and so on. This should improve determinism of builds and avoid the issues which have been particularly obvious since the introduction of recipe specific sysroots. If users find there is a tool missing, they can extend HOSTTOOLS from a global class or global conf file. Right now the settings should be enough to build everything in OE-Core. (From OE-Core rev: fa764a403da34bb0ca9fa3767a9e9dba8d685965) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: bump version for change in eSDK selftest behaviourJoshua Lock2017-02-191-1/+1
| | | | | | | | | | | | | Since 59a99cd8 "oeqa/sdk: Updates sanity tests for minimal eSDK" we can now run oe-selftests against a minimal eSDK. We need to increase the layer version so that we can detect this change in behaviour in our automated testing. (From OE-Core rev: def3800c7e58d9d1b54ea1df27b190a0f6d1d544) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: remove pointercalMaxin B. John2016-08-251-1/+0
| | | | | | | | | | remove pointercal reference from layer.conf file since we moved the pointercal recipe from oe-core. (From OE-Core rev: 7a0f93956f43a5d000e845eeb429e9e37d48ae2e) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: bump version for uclibc removal and LSB updateRoss Burton2016-07-261-1/+1
| | | | | | | | | | As of oe-core layer version 9, uclibc has been removed and LSB approximates version 5 (which means that Qt 3 isn't required for LSB conformance). (From OE-Core rev: e2900a30cc36ced67d157814b0f6afbd8f1ff8ed) Signed-off-by: Ross Burton <ross.burton@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 19:36:53 +0000