| commit | 5d54b3d19c3b98d395a818693acb2fb0ca22a32d | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Wed Oct 18 10:34:08 2023 -0500 |
| committer | Matt Spinler <spinler@us.ibm.com> | Mon Oct 23 21:04:34 2023 +0000 |
| tree | b690edc0b57fbf312dc858641976c8535831108f | |
| parent | 8a2674b8b6afe66759fd878b40512eff6b6f6396 [diff] |
Add myself as owner to com/ibm Adding myself to be an owner for just the IBM D-Bus interfaces. Change-Id: Ic88f649f9b21e9e71d75db584ce6dfed46479f93 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