| commit | 36b527af49cf87d0bc7097ea6faba4904fbf8878 | [log] [tgz] |
|---|---|---|
| author | Benjamin Fair <benjaminfair@google.com> | Wed Nov 02 20:41:21 2022 +0000 |
| committer | Benjamin Fair <benjaminfair@google.com> | Mon Nov 07 23:00:15 2022 +0000 |
| tree | 809a5ff382e33142e3baa0a8b5e84b810a8cdeef | |
| parent | 484f6c45b0fb7d4c3de460200e187f19635c1d0f [diff] |
Inventory: Add "containing" Association for Item This Association indicates that an Item (usually a Chassis or Board object) physically contains other objects. Also remove the duplicate definition from Cpu and CpuCore since it's now covered by Item. Signed-off-by: Benjamin Fair <benjaminfair@google.com> Change-Id: I6df06b1dddfd9408ff39e8917d269a2cba22668d
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