commit | a1347418307d31a94bd21f22897aa508df938dcf | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Tue Dec 06 10:56:22 2022 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Dec 06 11:11:59 2022 -0600 |
tree | dfcb36f177db4f34b8b3f2be3ff718b3648ef755 | |
parent | 3c7b858a13aa5fde934d6d789c9a6027490f78dc [diff] |
reformat with latest settings Reformat with the latest settings from openbmc-build-scripts (and copy latest config files where appropriate). Fix a few minor markdownlint issues. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I55205817c29dc3f182a165ddf9cd5d4e07b90063
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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir