summaryrefslogtreecommitdiff
path: root/meta-google/conf/layer.conf
AgeCommit message (Collapse)AuthorFilesLines
2021-11-18meta-google: Depend on phosphor-layerWilliam A. Kennington III1-0/+1
This makes our override ordering explicit with respect to layers we append to. Change-Id: If6048bcbd0199e730dc5a9bb52667a94887578cd Signed-off-by: William A. Kennington III <wak@google.com>
2021-08-24treewide: remove gategarth from layer-supportPatrick Williams1-1/+1
We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current and the upcoming. Remove 'gatesgarth' is it is now 2 releases back. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
2021-08-09meta-google: layer.conf: Revert 45725 and add honister as Yocto releaseWilly Tu1-3/+3
Reverting the changes in https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/45725 and adding `honister` to LAYERSERIES_COMPAT for the next Yocto release. Change-Id: I32c138127dc3508d6925c990643b9efce2bda0b6 Signed-off-by: Willy Tu <wltu@google.com>
2021-08-07meta-google: layer.conf: Cleanup for Yocto override syntax changeWilly Tu1-3/+3
Update `_google-layer` to `:google-layer`. Change-Id: I3443c265aa3ff3bb711f65c016942bfd53ecf153 Signed-off-by: Willy Tu <wltu@google.com>
2021-04-06hardknott: yocto releaseAndrew Geissler1-1/+1
Latest upstream yocto has moved on to the 3.3 hardknott release Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
2021-03-10meta-google: linux: Add configurationsWilliam A. Kennington III1-0/+7
Upstream: 3c2cdab65317061f819ca0f48448821ea4ab79cf Change-Id: I7c519c5d1b4d404727aee909ea7582165c9f4dd4 Signed-off-by: William A. Kennington III <wak@google.com>
2020-11-05meta-google: update Yocto compat for gatesgarthPatrick Williams1-1/+1
The next release of Yocto is soon and most of the upstream layers have switched support strings for it. Support layer compat for gatesgarth (current) and dunsfell (previous). (From meta-google rev: 98b0607cb298193ee7a8033e0c333224a10d0477) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ie038d9ad9f7f785fd8b3091cb19d6b593924eace Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-05-01meta-google: dunfell: add support for new layerAndrew Geissler1-1/+1
(From meta-google rev: 74821b8be2d4fdeec6d6663147b0016175dae469) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ibf35a67b59b869b3a4d5fb46665a9797119de580 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-09-20meta-google: layer.conf: add zeus compatibilityPatrick Venture1-1/+1
OE-core master will be dropping warrior soon; zeus is the next release. (From meta-google rev: 3bc085b11bb53063d63b043a9d678cfd4359eacd) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ia05fbd051ec17edd30849480fbeb94c263f96935 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-09meta-google: layer.conf: set BBFILE_PATTERNPatrick Venture1-1/+1
Bitbake uses this regex to associate recipes and bbappends from BBFILES (which contains recipes and bbappends from -all- layers listed in bblayers.conf) to this layer. The association is then used to map the BBFILE_PRIORITY value for this layer onto the recipes provided by this layer. BBFILE_PRIORITY is used to determine which recipe to use when the same recipe appears in multiple layers. Without BBFILE_PATTERN set, recipes in this layer will get a default priority and not the priority specified in BBFILE_PRIORITY. This layer doesn't set a priority anyway, so functionally this patch is a noop but it is an improvement from a correctness standpoint, and it makes a warning go away Removes warning: WARNING: No bb files matched BBFILE_PATTERN_google-layer '' (From meta-google rev: 006860684ec5b429b386a474c799a8ded05a6179) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I0e13c50b59a38fff89c4e737b27b20df56db1b67 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-06meta-google: layer.conf: Add warrior compatibilityPatrick Venture1-1/+1
oe-core branched in preparation for the upcoming 2.7 Yocto release and as of 13e45ff requires core layer compatibility to "warrior" instead of "thud". We'll retain compatibility for both until we do our own branch or stop testing thud. (From meta-google rev: 2282c02ed2b9021205840e6bd9b3fdcf70870f87) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I9396d0ec3ea4fbbb9a8ba5aaa685196f7a087dd3 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-10meta-google: prepare for yocto 2.6Patrick Venture1-1/+1
Set compatibility to thud. (From meta-google rev: 0d4ca78901c79cbef8401df0aa2261569fad6854) Change-Id: I337d9dfc4c8bce18bd7b7cff3f4ca3e4e8ff7b00 Signed-off-by: Patrick Venture <venture@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-17meta-google: Add initial configuration layerPatrick Venture1-0/+10
meta-google: provides a set of recipes for Google daemons shared with OpenBMC as well as any recipe modifications Google needs for working with OpenBMC. (From meta-google rev: 320c29c7579f74fff6c13244e8d471521b6844bf) Change-Id: I76275485a574b02e92333aff4f95e209eb3f4ede Signed-off-by: Patrick Venture <venture@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-07-01 03:56:07 +0300