commit | db24111a017e1048923cfb9c1d387a21129014bd | [log] [tgz] |
---|---|---|
author | William A. Kennington III <wak@google.com> | Fri May 14 15:35:48 2021 -0700 |
committer | William A. Kennington III <wak@google.com> | Mon Jun 07 23:21:19 2021 -0700 |
tree | 0a1f76a1b19f7b6f918830eb5aa6de8c9ad98a13 | |
parent | d2180a95b5f8f3902f067dd94d4bd86b93ea9fde [diff] |
build: Don't use implicit includes Otherwise, our compiler gets littered with an include path for every single header. This creates a combinatorial explosion of paths and slows down compilation. Change-Id: Ief69e91f5e75e0c743918e473b5888e12ec5e068 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