commit | 41a7b450d537f51da4bf1fcaa51f25ca02eb5edf | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Apr 15 13:49:06 2021 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Apr 15 13:50:39 2021 -0500 |
tree | 175d198d8f118a5ce623e0029978de50288aca1a | |
parent | 16599e2dc0ca8e41f71706f55d139e8f0af61ad7 [diff] |
build: add dependency for subproject use When phosphor-dbus-interfaces is used as a subproject, it needs to expose a 'dependency' which can be used by the consuming project to get at the libphosphor_dbus. Add it using the 'declare_dependency' call. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: If8984d86704d2109b826e3c10512d01e90fd6bbc
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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
.
Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir