| commit | 37b87aa250bafd0e04a5fc5d6902222343c177e9 | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Wed Mar 13 02:30:05 2024 -0600 |
| committer | Gunnar Mills <gmills@us.ibm.com> | Wed Mar 13 03:27:42 2024 -0600 |
| tree | 71153a9b3d100ae8fc37b6ccffbad445ce7f0a7c | |
| parent | d993b640fa26d42389dee3a784cd7474068b5873 [diff] |
Fix misspelling in PCIeDevice d993b64 had default spelled wrong. Signed-off-by: Gunnar Mills <gmills@us.ibm.com> Change-Id: I5ff027eec51b9a10da4823de26650dbe490a265c
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