| commit | b1b4d2617e80de24563fad86d0dddece81410def | [log] [tgz] |
|---|---|---|
| author | William A. Kennington III <wak@google.com> | Sat Jun 05 12:22:23 2021 -0700 |
| committer | William A. Kennington III <wak@google.com> | Mon Jun 07 23:24:40 2021 -0700 |
| tree | 3fd3716ac8e3734aaf2fe99bfebd50dc4eb15e2a | |
| parent | 71892004aa707899ec6928c7cd00957113e99c55 [diff] |
treewide: Create yaml directory This allows the propagated yamldir paramter to work correctly in subproject style builds. We don't want other files in the project conflicting with tools that scan the yamldir. Change-Id: Ie2759c7f3baf399392cdda0e507055ceb262d2e1 Signed-off-by: William A. Kennington III <wak@google.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir