| commit | 4444a13c9af8d581797bd43f378be51a614d60f5 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 08 06:35:17 2023 -0600 |
| committer | Adrian Ambrożewicz <adrian.ambrozewicz@linux.intel.com> | Wed Dec 27 11:26:47 2023 +0000 |
| tree | 4ea86e669450af57f5314ec32c58d2736f6bcddb | |
| parent | 8ca57c7da72c9e48c3a3af9acf26b5bc4f35911c [diff] |
meson: adjust nlohmann-json dependency - Simplify nlohmann-json dependency in meson.build. - Use consistent dependency variable names (based on Meson style). - Align wrap file name with meson wrapdb choice for the project. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I2e893fd8c300b36a16d704f2002bb966a6e52ce4
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].