commit | 8548f0373a3621a8e095bd7a4321be8d1974da09 | [log] [tgz] |
---|---|---|
author | William A. Kennington III <wak@google.com> | Fri May 14 15:34:01 2021 -0700 |
committer | William A. Kennington III <wak@google.com> | Sat Jun 05 12:20:52 2021 -0700 |
tree | 3e3e6acbaba29de033392f817e9d11d5584ce3a9 | |
parent | 2600affce017d5504ab3084fcd26de64f4229372 [diff] |
build: Tools should be native They should be pulled from the native path not the cross path. Change-Id: Iec5cd8cbef7fc74f7171a33eda50f3175d376414 Signed-off-by: William A. Kennington III <wak@google.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