commit | 4f9c09144b60edc015291d2c120fc5b33aa0bec2 | [log] [tgz] |
---|---|---|
author | Michal Orzel <michalx.orzel@intel.com> | Mon Aug 01 10:20:46 2022 +0200 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 09 11:10:31 2022 +0000 |
tree | d0c9ee03c30786bc98ed921bd667f9e05d251301 | |
parent | 9f2fee821a19da9382a4aee09d8b5079bd03b8e3 [diff] |
Update Telemetry service interfaces This change updates description of interfaces utilized by Telemetry service, so that its contents mirror the desired implementation. Change-Id: I7207c4889912e848a058279b9d89f643a7e0b6b8 Signed-off-by: Michal Orzel <michalx.orzel@intel.com>
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 and org/freedesktop 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