| commit | 531c90e34497bbc571c18c50fe078c0d86e61d91 | [log] [tgz] |
|---|---|---|
| author | Willy Tu <wltu@google.com> | Wed Jun 30 18:24:28 2021 -0700 |
| committer | Willy Tu <wltu@google.com> | Wed Jun 30 18:25:01 2021 -0700 |
| tree | 685276bd0429b75026b05d4886ba56cc2d1c38b3 | |
| parent | 1f971f2d647b6d301208c4e39b3bbfb94eb1d029 [diff] |
Drive: rename Interface to interface Drive.Interface.yaml is not being processed and no server.hpp is created. Renamed to Drive.interface.yaml instead. Fixes openbmc/phosphor-dbus-interfaces#11. Same change as in https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-dbus-interfaces/+/43632 but that change was removed due to https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-dbus-interfaces/+/43821 Change-Id: I3e1a7dbd84aeb92689eeedf9c613595f4e16ada3 Signed-off-by: Willy Tu <wltu@google.com>
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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir