commit | 02f196d40802ee0b4d0b37f8781edb7c481b1300 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Mon Dec 14 14:09:37 2020 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Mon Dec 14 14:09:47 2020 -0600 |
tree | abac096525cf22babb9a99f401f8df0bb2f90b4b | |
parent | 6be85da9193d5c529b49fbf9345507e0be2b9477 [diff] |
Location: fix generated meson files When LocationCode interface was added, the checked in generated meson files were missing one change. Re-run generator and check in. Fixes 2bcb4b4f008ea70645ef6d755cc5967bd2bccfae. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic348773be3c21c7fe51784a7211bb8150e1a7ac9
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
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir