Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-dbus-interfaces / 0e6cea83df69d4047037d5ee7ccd4b04a1e79bca
commit0e6cea83df69d4047037d5ee7ccd4b04a1e79bca[log] [tgz]
authorWilliam A. Kennington III <wak@google.com>Thu Jun 17 22:35:57 2021 -0700
committerWilliam A. Kennington III <wak@google.com>Fri Jun 18 00:46:30 2021 -0700
tree167ddc8fdca4ef0df8b70f0bf46f655ff071170c
parent08baf48ad5f15774d393fbbf4e9479a0ef3e82d0 [diff]
build: Don't depend on sdbusplus.found()

We can't depend on this for determining if we are using sdbusplus from a
subproject or not. If the project including phosphor-dbus-interfaces
finds the sdbusplus dependency first, this will show as found and use
the wrong routine for finding the tools.

Change-Id: Id1870ecc5a330cc26ea242657255ebfe13fd0448
Signed-off-by: William A. Kennington III <wak@google.com>
1 file changed
tree: 167ddc8fdca4ef0df8b70f0bf46f655ff071170c
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .shellcheck
  6. LICENSE
  7. MAINTAINERS
  8. meson.build
  9. meson_options.txt
  10. 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