commit | 297845b994ebcfb68a114a096385088ef4d636ad | [log] [tgz] |
---|---|---|
author | Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com> | Thu Oct 15 07:17:58 2020 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Oct 15 12:27:31 2020 +0000 |
tree | 85d123a74efcc50019c65c153d55c6b1a6acefd7 | |
parent | 6212ea6b396a35425568448cd693142fd185dea7 [diff] |
README: Add an example for using option -D Change-Id: I1a4e43944e89ee160ca703a4976db90554f35402 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
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