meson: Add dependency override for phosphor-dbus-interfaces

Resolves e.g. the following when phosphor-dbus-interfaces is specified
as a subproject:

```
$ meson setup build
...
phosphor-logging| WARNING: Subproject 'phosphor-dbus-interfaces' did not override 'phosphor-dbus-interfaces' dependency and no variable name specified
phosphor-logging| Dependency phosphor-dbus-interfaces from subproject subprojects/phosphor-dbus-interfaces found: NO

subprojects/phosphor-logging/meson.build:26:0: ERROR: Dependency 'phosphor-dbus-interfaces' is required but not found.
...
```

Change-Id: Ie549c377e71297e9748322be2f2e0c0153c104f7
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
1 file changed
tree: ec621150c75564ba6117bc361ab7879836800dfb
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .markdownlint.yaml
  6. .prettierrc.yaml
  7. .shellcheck
  8. LICENSE
  9. meson.build
  10. meson_options.txt
  11. OWNERS
  12. README.md
  13. requirements.md
README.md

phosphor-dbus-interfaces

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.

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 and org/freedesktop 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