| commit | 5364764e2e76ff3533254cfa2ddc466ccb2f8b31 | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Jun 25 11:45:38 2020 +0200 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 18 16:05:07 2020 +0000 |
| tree | 1220532ed73abc085b41be8313ad8ef24046d1f7 | |
| parent | d37091affcd933b7bc7cfd0ac393e2dd539f0235 [diff] |
Create Report and ReportManager interfaces Both interfaces are created based on Telemetry design described in openbmc/docs/designs/telemetry.md. Both will be implemented in Telemetry service in openbmc/telemetry repository. Ref: https://github.com/openbmc/docs/blob/master/designs/telemetry.md Tested: - Successful build and verified changes in server.hpp and server.cpp. Change-Id: Id6578ce1d349ee07b8a07b2d597471ba7433a6c0 Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Signed-off-by: Wludzik, Jozef <jozef.wludzik@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 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