commit | cfe12d262822fe7cdde8e744842a22b24513e6d3 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Mon Jan 25 15:22:18 2021 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Sun Feb 21 13:40:41 2021 +0000 |
tree | bde7ab60a9e0440d33f71282790a39f1457076bd | |
parent | 257c17da484244ae81b98d4bb12a052187d2c57e [diff] |
new unsupported request common error A common use case is where an interface or property does not support all of the possible options to it. Create a common error for these scenarios. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I36b09f73adfed9244976ce21c70d02bae61bba01
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir