| commit | 7f154004885f4e98bd8d0aa6f66259c117b95a4c | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Jan 03 10:12:23 2025 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Jan 10 19:57:38 2025 +0000 |
| tree | 56df10fead4fe8c7e0d7b75e80871d16d16d2759 | |
| parent | e2e4dde12e2fa9c8856e291dd6c7405a8fa4164f [diff] |
build: support registry generation sdbus++-gen-meson version 10 adds support for redfish registry generation and greatly simplifies the install directives. Regenerate the YAML meson files and modify the base meson.build as necessary. Also, format meson.build with `meson format`. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I77586fca7742d5468803913cb45276ca57271655
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