commit | a7a6db3f770f5a1a5fd660ba3f6a611c435db616 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 03 08:38:37 2020 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 03 08:38:45 2020 -0600 |
tree | 923c4ee6f6d7d3db26fac7c2cbc8e712ff012c6e | |
parent | f7b0e07121a5ff287c7d8ffac411b732e592ae05 [diff] |
VR: add meson files New interface was added without a corresponding meson update. fixes f7b0e07121a5ff287c7d8ffac411b732e592ae05 Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I02c88ddb5a5ffdde1865655393154771649b35f7
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