| commit | 08baf48ad5f15774d393fbbf4e9479a0ef3e82d0 | [log] [tgz] |
|---|---|---|
| author | William A. Kennington III <wak@google.com> | Sat Jun 05 12:27:15 2021 -0700 |
| committer | William A. Kennington III <wak@google.com> | Mon Jun 07 23:24:41 2021 -0700 |
| tree | b8d74735f6b3867b5c9a9799e1f6622b3a62b23d | |
| parent | b1b4d2617e80de24563fad86d0dddece81410def [diff] |
gen/run-ci: Only check files inside of gen We don't want to consider it a failure if files outside of the gen/ directory differ or are untracked in the build. They aren't supposed to be covered by this check. Change-Id: I7dcb85a289fd4270e3201dd92f024b59e64f8b9e 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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir