summaryrefslogtreecommitdiff
path: root/meta-phosphor/classes/phosphor-logging-yaml-provider.bbclass
AgeCommit message (Collapse)AuthorFilesLines
2020-06-16phosphor-base.inc: add var for automatic YAML subdirsPatrick Williams1-1/+1
Some packages have directory trees of YAML files arranged based on canonical organization names. See phosphor-logging-yaml-providers.bbclass as an example. Add a variable that can be appended to by a layer to limit the number of 'bbappends' that are necessary in a layer to add their layer-specific organizations to all the YAML processing recipes. (From meta-phosphor rev: 2f31e7a7a37f841c1b2586e92258a7759b36306f) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ie4754ba96a4542ce813869a1384b44ab88000be0 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-16phosphor-logging: create bbclass for non-native YAMLPatrick Williams1-0/+22
The current working model for many packages that supply YAML is that they have both a native and a non-native package where the native package doesn't build anything but supplies YAML and the non-native package does the real building. In the case of phosphor-logging this is due to a cyclic dependency: package-yaml -> logging header -> package To hopefully reduce the complexity on package makefiles to this dual-build structure, I have created a non-native bbclass that can be used to create simple packages for the logging YAML. I have also created a sample for phosphor-led. (From meta-phosphor rev: bb79d7c980ba03f45ba5c3cb1783f59ee5cdc4bd) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I38e096c36180b2b6e68a336bb204727a2f96c1a1 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>