| commit | 1b03c8d66b6265ba2c40029e13078db5f09a88b7 | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Thu Oct 13 18:06:17 2022 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Oct 14 08:29:32 2022 +0000 |
| tree | e7a1a3d5f9e33a3261e438c5fffeaed5ff691b4c | |
| parent | daeddc7c5587933729a7a1e981b054c4c8be8069 [diff] |
Update meson and subprojects Few changes related to meson: - GTest and boost were updated. - Boost is now built locally in case it is not installed on system. - Minor meson.build refactor. Testing done: - local build is working fine, when subprojects are not installed on the system, - local build is working fine, when subprojects are installed on the system, - yocto build is working fine. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: Ib62092946d6ffafb1884d1ba3eab97bed243dd12
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].