| commit | 2eefe98e65a244088c882c0250a86865b0f89ac5 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 11 12:26:29 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 11 12:27:18 2024 -0500 |
| tree | afba71b181b3433e6541f50676edf6b3c25d41f7 | |
| parent | 18b5dd4757b8c96e028e80efc5843d635ef095da [diff] |
OWNERS: allow yaml to also review gen If changes to YAML files also induce gen/* changes, the same owner should be able to review those. Adding Matt to be able to review gen. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iedbfc193df75cf7b70c282de3a14498e04070920
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