| commit | c096cf78fe626923f81067a5b97283aa856d8b74 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Apr 21 11:15:51 2023 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Apr 21 11:15:51 2023 -0500 |
| tree | 04acc7ac58e2bb0b6c1cf496482eec3dc68bd15f | |
| parent | a1b26a4bdf606df141695561a92a4f060cdd0156 [diff] |
regenerate-meson: re-run with latest from sdbusplus The sdbus++-gen-meson has a new version, which requires regenerating all the meson in this repository. Re-run the `regenerate-meson` script. Change-Id: Ic72fe80376052d5749ba007bb87be25c83a46279 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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