| commit | 7d24aa23641cb8894744800df25a5b95c61f3dc4 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Sat Feb 01 08:37:37 2025 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Sat Feb 01 08:37:37 2025 -0500 |
| tree | c5089aba40468118dedd2462ddce4360497b0c5b | |
| parent | 6c956488f7a1d796353cfd008787f9b6f7f64d29 [diff] |
meson: reformat with meson formatter Apply the `meson format` results. Change-Id: I0ff3dc51a6a4e8ea2edf03219e4578fcffe18748 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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].