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.

Change-Id: I42aca4bd4a290b5ff05c1926ac6d81f03f8f3b76
Signed-off-by: Willy Tu <wltu@google.com>
3 files changed
tree: 5144e9d3667120083196753e0074d266d8758d7a
  1. com/
  2. gen/
  3. org/
  4. subprojects/
  5. xyz/
  6. .gitignore
  7. .shellcheck
  8. LICENSE
  9. MAINTAINERS
  10. meson.build
  11. meson_options.txt
  12. README.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.

Building

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.

Configuration

Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References