phosphor-logging: create bbclass for non-native YAML

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.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I3148f14c0502aebb55f083e39ac5c499e6276680
2 files changed
tree: 100ff9bcb57fcba1cf80ddbd86daccb04670ebd6
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.