commit | 52f37113f231b6e4235677b3ad375e075e921892 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 01 09:47:21 2021 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 01 09:48:17 2021 -0600 |
tree | f04b6341b685198c1605ef9efe5d22d57152a908 | |
parent | e0764cf41d16b823a519e9d4f508b588e3e84aba [diff] |
software: remove old TODO The software design had a reference to a "TODO" pertaining to the old REST API, which has been present for years and unresolved. Since the REsT API is deprecated anyhow and issues should be tracked elsewhere, remove this TODO. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I554da4dcfee32a1196e3c42c17bbba6c73cd1653
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