Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-dbus-interfaces / 71892004aa707899ec6928c7cd00957113e99c55
commit71892004aa707899ec6928c7cd00957113e99c55[log] [tgz]
authorWilliam A. Kennington III <wak@google.com>Fri May 14 16:09:53 2021 -0700
committerWilliam A. Kennington III <wak@google.com>Mon Jun 07 23:21:19 2021 -0700
tree5de750a074134439a2083f808e8185e0833d075c
parent795b437d39c5f044a865c6a957a963ee73c88ec8 [diff]
build: Don't generate markdown for subprojects

Change-Id: Ib4351fc4601b00d54470d4069a78a2b23efb54aa
Signed-off-by: William A. Kennington III <wak@google.com>
2 files changed
tree: 5de750a074134439a2083f808e8185e0833d075c
  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