| commit | 8cca11f0c7d7f0dacec15b0c4272703862cbafba | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Wed May 10 09:07:55 2023 -0500 |
| committer | Matt Spinler <spinler@us.ibm.com> | Wed May 10 13:19:44 2023 -0500 |
| tree | 51d14ff6afb0a3a64f960e99e7d6c5e8e18916bf | |
| parent | 7193e55f600537eaeeb5c4deaf53f9a3f88415c6 [diff] |
Add association D-Bus example Show how the primary/secondary element and association terms map to D-Bus. Also add a link to the mapper association documentation. Change-Id: Ib7c64b4a1a02d0a902f8ab2fc2d67e2e4c59da45 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
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