commit | 021f6d430938bd2ed18cacad66ee9573afab168e | [log] [tgz] |
---|---|---|
author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Wed Feb 08 09:00:12 2023 +0000 |
committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Tue Feb 28 14:32:51 2023 +0000 |
tree | 68db3d84a8997abae91c8e934a06163ccd93fab4 | |
parent | 3b861bb73a34b23d94083ca796085d44c2538dd6 [diff] |
updated telemetry service API Reverted addReport function to take multiple parameters instead of list of variants. Removed errors property from Report. Change-Id: Idd9ac31958142b7ce120fad676877b7226a32be7 Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
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