| commit | d2620704f721c60f730404c47c15b5f061b29d4c | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Mon Jun 28 12:06:15 2021 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Jul 16 11:34:24 2021 +0200 |
| tree | 0d8474110b45f047f0e2b7aa534563f58e55dec2 | |
| parent | 4ab1d496d8a50d0466afb7f49668c40758bfe6a9 [diff] |
Add meson generated files to .gitignore Meson is now generating subproject dependencies .wrap files inside 'subprojects' directory. As this directory contains non-generated .wrap files, .gitignore could no longer specify * rule for them. Tested: - Git is not detecting new files after clean local build. Change-Id: Ifb8d72aae2c19671b331ddaaf3960384a8700431 Signed-off-by: Szymon Dompke <szymon.dompke@intel.com>
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].