commit | abb61a0ff2d9ca0351292a48f8980ca7dd0127a7 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Thu May 25 12:47:56 2023 -0500 |
committer | Andrew Geissler <geissonator@yahoo.com> | Tue May 30 21:06:55 2023 +0000 |
tree | 3c53a27a199e86ba5da4324940350ae0353c43a0 | |
parent | f404c83b80d9227424c92fe66510024785adee41 [diff] |
bmc-ready: include new error codes in interfaces This will generate the appropriate bindings and ensure the error is passed back to the caller allowing them to properly handle this type of error. Change-Id: I63301d0371d27835417fcba503c32f854f1919bd Signed-off-by: Andrew Geissler <geissonator@yahoo.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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir