| commit | 6db06f5b8024f6a7cd9b69930c2a02402b501ec9 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Jun 13 17:08:38 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Jun 13 17:09:53 2024 -0500 |
| tree | dc172cd9bec2c3a5c00fc1fad772f9e721078272 | |
| parent | a8f47e7f1dfc43b6b9775bee7ee9e529a21fd7a5 [diff] |
software.version: add namespace path The software design specifies that all Version objects should be under the `/xyz/openbmc_project/software` namespace path. Add it to the YAML so it can be used in clients. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I5ba88e109daac416206fa7d65df926bf2a928ac2
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