commit | 0894943fe046af9bc318af85a50f32306eb5f10d | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Tue Jun 09 10:22:12 2020 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Sat Sep 05 16:49:05 2020 +0000 |
tree | bdbc726d58bf943f5a21f6064c40a5ab9991c9a6 | |
parent | 446ce846777fada726953b3196948b7399331587 [diff] |
build: enable meson build Add meson build support. Autotools support will be removed in the future once the consuming meta-phosphor recipes are updated. This should be feature complete relative to the previous autotools support. Additionally, support is added for using sdbusplus as a subproject in the event that users do not have sdbusplus installed. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic2c0129bda11cf10aaa557c2fd6403e2ed2cd8dd
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