| commit | 0c07b1352dff2f53861f5513c44eca8766e0cc21 | [log] [tgz] |
|---|---|---|
| author | Alexander Hansen <alexander.hansen@9elements.com> | Thu Sep 04 11:32:17 2025 +0200 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 05 15:01:48 2025 +0000 |
| tree | 5dcb53342cfc64a30eb4d205ab67f82e51b75c08 | |
| parent | 5b6deab0ed505aba429fd468ec11c17e5ae35c32 [diff] |
OWNERS: Add myself as reviewer Only subscribing to a few folders here since it looks like there are lots of changes coming in lately. I'm interested in changes to Inventory, Sensors and Software interfaces. Might drop out of here if there's too many emails :) Change-Id: I8ff4440e82ace294359bf0e16c1a471cca4811de Signed-off-by: Alexander Hansen <alexander.hansen@9elements.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