| commit | c6883fc4f6d0f4da3b05f3274ac0a654dff96969 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Tue Feb 27 16:19:04 2024 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Feb 27 22:49:40 2024 +0000 |
| tree | 362fa89295b0d5793a3f64a76a1bff36a6bb09eb | |
| parent | 097188ac4f10033e2ae407e4e264c446eaf79006 [diff] |
State.Host: use set for AllowedHostTransitions The intended use of this is as a set of allowed elements. Express intent with `set` instead of `array`, even though these end up on dbus in the same data type. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I0c2f55daa704f578ed1bb45a93ad81b4c57b90fc
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