| commit | 1ac4d547845d70f987a7bf43bb65405be92727d8 | [log] [tgz] |
|---|---|---|
| author | Wludzik, Jozef <jozef.wludzik@intel.com> | Wed Jan 27 13:15:27 2021 +0100 |
| committer | Wludzik, Jozef <jozef.wludzik@intel.com> | Mon Feb 01 09:43:24 2021 +0100 |
| tree | be74dd4548fc0df508f8e06af880c6c5027e9064 | |
| parent | 596a994519927be24988c658a1ead44cef11cc7a [diff] |
Update README.md file Added how to build section to README file. Updated references. Signed-off-by: Wludzik, Jozef <jozef.wludzik@intel.com> Change-Id: I8a9070d776119206e7c63fc61bc6975ea4f7d184
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].