| commit | 6050b6559bfa80e3372e6bb4145a14c7ebf6a27c | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Fri Dec 20 11:43:06 2024 +0100 |
| committer | Michal Orzel <michalx.orzel@intel.com> | Fri Dec 20 11:43:06 2024 +0100 |
| tree | f534131b3853333f0ee95220b2c606c7ec0dd1f4 | |
| parent | b47b7db48c4f883eb191077848d55d96bd884607 [diff] |
Fix CI compilation issue Resolves maybe-uninitialized error for std::function object, which shows when compiling with optimizations. Tested: CI build passed. Change-Id: Ia6f07a23715f0bf34d19e100bca94fc29cd0aa9f Signed-off-by: Michal Orzel <michalx.orzel@intel.com>
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].