summaryrefslogtreecommitdiffstats
path: root/meta/conf/layer.conf
AgeCommit message (Collapse)Author
2021-03-20layer.conf: Drop gatesgarth from the layer series namesRichard Purdie
The time has come to encourage people to update actively maintained layers to use the new series name. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-03-15layer.conf: Add gatesgarth back for now to allow for transitionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-03-15layer.conf: Update for hardknott release seriesRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-11-13layer.conf: fix syntax error in PATH settingMatt Madison
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. Signed-off-by: Matt Madison <matt@madison.systems> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-10-17layer.conf: fix sanity error for PATH variable in extensible SDK workflowSourabh Banerjee
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. Signed-off-by: Sourabh Banerjee <sbanerje@codeaurora.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-10-17layer.conf: Switch to gatesgarth only in preparation for releaseRichard Purdie
Update the core layer release series to gatesgarth in readiness for release. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-09-14tcmode-default: Drop gcc-cross-initial, gcc-crosssdk-initial referencesDouglas Royds
Further to 5b2fd1c724 Also a few remaining references in comments and in distro_alias.inc Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-08-06allarch: Add missing allarch ttf-bitstream-veraDaniel Gomez
allarch is missing in ttf-bitstream-vera recipe. Add it and include the recipe in the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS list. Signed-off-by: Daniel Gomez <daniel@qtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-07-27layer.conf: fix adwaita-icon-theme signature change problemChangqing Li
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 Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-06-03layer.conf: Bump OE-Core layer versionJoshua Watt
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. Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-05-18layer.conf: Move to gatesgarth namingRichard Purdie
We're still compatible with dunfell from the core perspective so that is left for compatibility (probably for the next week or two). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-29layer.conf: Drop zeus compatibility for dunfell releaseRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-15layer.conf: Allow compatibility with zeus for nowRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-15layer.conf: Update to LAYERSERIES_CORENAME to dunfellRichard Purdie
Update the layer core name to the new release name. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-02-28layer.conf: Consider shared-mime-info and desktop-file-utils siggen safeKhem Raj
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] Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-08layer.conf: Update for zeus seriesRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-19layer.conf: Remove weston-conf from SIGGEN_EXCLUDE_SAFE_RECIPE_DEPSKhem Raj
This recipe is gone Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-19weston-init: Add possibility to run weston as non-root userKhem Raj
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 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>
2019-05-27layer.conf: Whitelist lttng-tools->lttng-modules dependencyRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-04-23connman: add PACKAGECONFIG for nfc, fix MACHINE_ARCH signature when l2tp is ↵Martin Jansa
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 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-04-02layer.conf: Update to warrior release name seriesRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-01-14ccache.bbclass: Refactor it to make it more reliableRobert Yang
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. Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2018-12-26recipes: Drop virtual/libc-for-gccRichard Purdie
We no longer have special "libc" for gcc so we can rely on plain virtual/libc and reduce the complexity in the dependencies. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-10-28weston: Split out machine specific configurationMark Hatle
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. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-10-20systemd: Remove items that made this machine (qemu) specificMark Hatle
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. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-09-27layer.conf: Drop sumo from LAYERSERIES_CORENAMESRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-09-24layer.conf: Add thud to LAYERSERIES_CORENAMESRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-08-21sstate: Avoid indirect autoconf-archive-native dependenciesChangqing Li
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. Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-08-16sstate: Avoid indirect bison-native dependencies (via ↵André Draszik
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 Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-08-15sstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping ↵André Draszik
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. Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-08-15sstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping *-initial recipesAndré Draszik
Use the newly introduced SSTATE_EXCLUDEDEPS_SYSROOT for specifying the *-initial recipes to be excluded from a recipe sysroot. Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-06layer.conf: Update LAYERSERIES rocko -> sumoRichard Purdie
Also set LAYERSERIES_COMPAT for core (we're compatible with ourself). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-06layer.conf: add -bootconf recipes to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPSCalifornia Sullivan
The bootloaders depend on these to be functional in the non-deploy case, but changes in them don't require rebuilding of the packages. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-04layer.conf: add busybox-inittab to SIGGEN_EXCLUDERECIPES_ABISAFEDenys Dmytriyenko
Similar to sysvinit-inittab Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-01sstatesig: Move hardcoded native toolsJoshua Watt
Now that SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS supports the wildcard syntax, these exclusions no longer need to be hardcoded Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-11-29initramfs-framework: add install moduleCalifornia Sullivan
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]. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-11-09oprofile: remove the recipeAlexander Kanavin
Perf is the preferred solution, and oprofile is difficult to maintain against musl. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-09-13meta/conf/layers.conf: Add ca-certificates as ABISAFEMark Hatle
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. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-12initramfs-framework: bump PR and fix install-efi and setup-live modulesCalifornia Sullivan
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]. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-30initramfs-framework: Change recipe to be allarchOtavio Salvador
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. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-28meta/conf/layer.conf: bump layer version for LSB changesRoss Burton
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. Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-06-09meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.confRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-05-01bitbake.conf: Add HOSTTOOLS_DIR for ${TMPDIR}/hosttoolsPeter Kjellerstedt
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. Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-11base/bitbake.conf: Filter contents of PATH to only allow whitelisted toolsRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-02-19layer.conf: bump version for change in eSDK selftest behaviourJoshua Lock
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. Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-08-25layer.conf: remove pointercalMaxin B. John
remove pointercal reference from layer.conf file since we moved the pointercal recipe from oe-core. Signed-off-by: Maxin B. John <maxin.john@intel.com>
2016-07-25layer.conf: bump version for uclibc removal and LSB updateRoss Burton
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). Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-05-30layer.conf: Whitelist ca-certificate dependency on opensslRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-02layer.conf: Update after replacement of udev with eudevRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-02layer.conf: Whitelist cantarell-fonts fontconfig dependencyRichard Purdie
fontconfig is a stable API dependency and allarch fonts are desirable. This matches the other fonts. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-13 09:42:11 +0000