| commit | 3e2cc9d4978cf8f8bab4384dfd2b4996d95040fe | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Tue Dec 14 12:00:52 2021 +0100 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Tue Dec 14 16:03:00 2021 +0100 |
| tree | 6b4935ba4ca050a28d014ebf16c45372ba62b986 | |
| parent | b8cc78ddf9cc87c83176c7bda575ceef2678d00f [diff] |
Update subprojects versions Local meson + ninja build was failing, because phosphor-logging was set to old version without meson.build file. Sdbusplus was also updated, and setters have been updated to reflect its latest changes. Testing done: - local build is working properly. - UTs are passing. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I71d5a4bbf7aae4573dcfa014fc46a9f7862ecec8
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].