Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-dbus-interfaces / 6f70d9ffd412bddd16fda82398c519f0528e0963
commit6f70d9ffd412bddd16fda82398c519f0528e0963[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Thu Apr 15 19:07:19 2021 -0500
committerPatrick Williams <patrick@stwcx.xyz>Thu Apr 15 19:09:36 2021 -0500
tree2f1d11e4fb0e0eeac2508e41b7d54acd543dd6d9
parent41a7b450d537f51da4bf1fcaa51f25ca02eb5edf [diff]
build: create pkgconfig var for yaml output

Some packages that depend on phosphor-dbus-interfaces try to
re-process the YAML for their own purposes.  Add variables to
pkgconfig and subproject-dependency so that those users can
determine where the YAML is at.  For pkgconfig it is in the
install path and for subproject's it is at the source-root.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I222b4394a22b45fe493ac13b9d50538dc0349bbb
1 file changed
tree: 2f1d11e4fb0e0eeac2508e41b7d54acd543dd6d9
  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