| commit | ed45963ef0a5b30fd6e54ea8ee4937833ff6032e | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 18 07:18:34 2020 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 18 07:18:36 2020 -0600 |
| tree | a250c91853cc464792c37558187522f35a055709 | |
| parent | 29f59a60dcf9701e01f950424d712150b41c3df8 [diff] |
build: regenerate meson for stable-sort There was a small tweak to the sdbusplus script so that the sort becomes stable. Regenerate meson from that. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I15a4645efdad781d28496f30e787c411a62073b0
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