commit | 29f59a60dcf9701e01f950424d712150b41c3df8 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Mon Dec 14 15:03:45 2020 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 17 16:12:28 2020 -0600 |
tree | c88452327f7deecc440f5dbbfc3a304b66bb1f37 | |
parent | 0601b2eb778eb48bb30744f23231ede6f8b95d1c [diff] |
regenerate-meson: improve search for sdbus++ tool Improve search for sdbus++-gen-meson so that this works both within SDK (where sdbus++-gen-meson is in the path) and from submodule. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ifea44b67a8e8563c2f2612981bbb5605e7ed2e53
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