| commit | 844e332c6a85c37e3feda0e092e09cd3bee53366 | [log] [tgz] |
|---|---|---|
| author | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed Oct 12 09:21:16 2022 -0400 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed Oct 12 09:21:16 2022 -0400 |
| tree | 454fb1db959317082c9697db38e060409810a6e0 | |
| parent | bed657a128eac2b6e56417ee6545bfd3d6bc10d8 [diff] |
OWNERS: update It's been quite some time since I've helped maintain the DBus interfaces in any meaningful way, so it is time to drop my name from the list. Thanks to Patrick for stepping in and filling that void. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: I922bbb119549d855e2eb4a4c2aec33960e1de2bd
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