Age | Commit message (Collapse) | Author | Files | Lines |
|
Most repositories now put their dbus and phosphor-logging YAML into
a `yaml` subdirectory. Enhance the bbclass to support either in the
root or in the `yaml` subdirectory.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I30a104088d4ac9696e9072b33ec8e91c4a718f10
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
|
|
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>
|
|
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>
|