| commit | e2c4105f2f416f1c3dbf4107f1204004dc194b56 | [log] [tgz] |
|---|---|---|
| author | Karol Niczyj <karol.niczyj@intel.com> | Wed May 19 10:14:10 2021 +0200 |
| committer | Karol Niczyj <karol.niczyj@intel.com> | Wed May 19 10:24:24 2021 +0200 |
| tree | d05b065ed44b342bf86c5d99b3fa059095815d48 | |
| parent | f763c9e3bbe0f86a4a41e7bb0dc70bffde0af9b2 [diff] |
Update buildsystem - sdbusplus HEAD use C++20. Therefore I changed revision to same commit as revision in yocto. - Updated Boost URL, because current one is not working. Test: Built telemetry and tested it with unit tests. Change-Id: I4c2cd10bfdc42a3deaf3b5a6aa9d7969721c45a8 Signed-off-by: Karol Niczyj <karol.niczyj@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].