| commit | 8e360784fc4edcc4de5b4b0f1fce5ffa7bf327fb | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Sat Sep 09 12:17:52 2023 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Sat Sep 09 12:18:08 2023 -0500 |
| tree | 51fc7ef1a5306acc3a03cf30634ac8288aeb6ddd | |
| parent | 4f6fbeab36c23cce3816f0f6de4c92b9b87774b7 [diff] |
Software.Image: add YAML from phosphor-bmc-code-mgmt Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Icc3a526d9cbc4e38b4336eca46d081e9c108022f
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
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 and org/freedesktop 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