| commit | 93064d8fcef2c6fde1f61c0cedacb46b21eab039 | [log] [tgz] |
|---|---|---|
| author | Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> | Thu Sep 09 13:35:50 2021 +0200 |
| committer | Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> | Thu Sep 09 13:51:01 2021 +0200 |
| tree | 776a9a360ff52c67b2160cfd43276ba489466ad7 | |
| parent | 8069771c0db62887b72aa2b8c51cd64eb5f99b2d [diff] |
Updated subprojects revisions to fix build issues Revisions of subprojects had to be modified to eliminate errors during compilation of OpenBMC Telemetry project via meson build + ninja Tested: - Built Telemetry and ran its unit tests, all passed Signed-off-by: Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> Change-Id: I9e20550a625f24d0e5135dcde78994007c0dfc47
This component implements middleware for sensors and metrics aggregation.
This application is implementation of Telemetry proposed in OpenBMC design docs [1].
It's responsible for:
[2],[3] updates.[4]There are two way to build telemetry service:
To build it using bitbake follow the guide from OpenBMC docs[5]. To build it using meson follow the quick guide to install meson[6] and then run below commands
meson build cd build ninja
After successful build you should be able to run telemetry binary or start unit tests
./tests/telemetry-ut ./telemetry
In case if system is missing boost dependency, it is possible to build it locally and set BOOST_ROOT environment variable to location of built files for meson. After this change meson should be able to detect boost dependency. See [7] for more details.
More information can be found in OpenBMC docs repository [8].