| commit | 484f6c45b0fb7d4c3de460200e187f19635c1d0f | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Tue Nov 01 21:07:54 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Nov 01 21:07:56 2022 -0500 |
| tree | 5bb4b90a8b24f5fffa58ecd90658c52bbf7ce430 | |
| parent | fc5546ea66377480bcddc5208eefc291ca5b0e99 [diff] |
Item: remove documentation for non-conforming association The association for CPU/Slot does not conform to the documented association rules, so remove it from the readme so as to not mislead others. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I00fd61d13c9d75609221698118225f6dab5fe56f
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