summaryrefslogtreecommitdiff
path: root/meta-mellanox
diff options
context:
space:
mode:
authorBrad Bishop <bradleyb@fuzziesquirrel.com>2019-05-23 02:21:40 +0300
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2019-05-29 01:36:40 +0300
commitbd44fa88f1ac55161f9c26b8091f69e4229cc00c (patch)
treec07d4828c6eed6967f87f65c39f7c1dcec8d539f /meta-mellanox
parent5e2c8c7e4178ac45d3b44ce2bc541e9a1e0d8a76 (diff)
downloadopenbmc-bd44fa88f1ac55161f9c26b8091f69e4229cc00c.tar.xz
meta-phosphor: inventory: enable non-native recipes
There exists a number native class recipes throughout meta-phosphor that simply provide a data (often YAML) file as input to building another application. Having these data file recipes implemented as native class recipes prevents the use of machine overrides because bitbake (rightfully so) discards machine qualifiers from native recipes. Further, data files aren't really any different than library header files and those are consumed by recipes as target class recipes that are DEPENDed on. Do the same thing for data file recipes. (From meta-phosphor rev: 1675a60bc9648cb5c7ec224df3791dbe89f09134) Change-Id: I7fa23c7914abc5018f6534a8daa0462c6ee9daa3 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-mellanox')
0 files changed, 0 insertions, 0 deletions