| commit | f8ae65ca626e0328d6dfbc229f6fcf6dfed56812 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Mar 21 10:21:36 2022 -0500 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Wed Mar 23 13:29:22 2022 +0000 |
| tree | 4a907c56baabb8b382893a231224a3564734f45e | |
| parent | f670b0261ba539256a30d45177eec84f82749faa [diff] |
meson: simplify dependencies Leverage wrapfile `[provide]` directives to simplify the dependency searching in the meson.build. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I5bbde5732df9604b6ea45eaae519bdf64c27ee3c
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].