| commit | d9632146a8c7c36c52a7ecdbbd649988caffb831 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Jun 24 16:12:44 2020 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Sat Sep 05 16:49:05 2020 +0000 |
| tree | dcdba94247e3eb3537406ade887a72a0b8be2450 | |
| parent | 0894943fe046af9bc318af85a50f32306eb5f10d [diff] |
build: add sdbus++-gen-meson generated files Use the tool to generate the meson.build files for the current tree of interfaces, but do not utilize them yet. Add a small helper tool to regenerate as needed. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ie1f68984e5b01dcab661863d2ac719d0e3cd45c1
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.
Due to the limited code generation methods available in meson today, changes to YAML files are not tracked by meson and do not automatically cause a new recompile. Subsequent runs when making YAML changes will require running ninja reconfigure in order to regenerate the code files from the YAML.
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