commit | 47f32d12c1ef5d4311a8b8c5779a6c67616cb7e8 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Jun 24 16:13:38 2020 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Sat Sep 05 16:49:05 2020 +0000 |
tree | 92acd90c97347d1386879de498953f65d15bd380 | |
parent | d9632146a8c7c36c52a7ecdbbd649988caffb831 [diff] |
build: use generated meson.build files Make changes to the root meson.build to utilize the generated meson.build files found in the `gen` sub-directory. Update the README to indicate how these can be regenerated. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ibe45637faf572e0a5a88719adf5f41f877895927
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