| commit | 2c872b3c4bb9adde1e1bebc748da8e221a1f90a2 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Jan 22 09:51:52 2024 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Jan 22 09:52:25 2024 -0600 |
| tree | 016a10c92b79b9a8760574ae227e3c4a88da0f86 | |
| parent | 1bb696106f955527b5db0f9cb334b135f14da171 [diff] |
Inventory.Item: add namespace path constant Add path constant that allow code to avoid hard-coding strings, matching the requirements outlined in the description section of the YAML. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I9d79f0301cd7132c3c879330a71147c3fc8f620e
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