| commit | 8ca57c7da72c9e48c3a3af9acf26b5bc4f35911c | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@inspur.com> | Wed Aug 16 10:35:44 2023 +0800 |
| committer | Adrian Ambrożewicz <adrian.ambrozewicz@linux.intel.com> | Wed Dec 27 11:25:50 2023 +0000 |
| tree | 840e0fb3966162238e4b8f6aac0d5699520014a7 | |
| parent | 359b7664358d82032465650529a553d27634a809 [diff] |
meson_options.txt: Support for reading options from meson.options Support has been added for reading options from meson.options instead of meson_options.txt[1]. These are equivalent, but not using the .txt extension for a build file has a few advantages, chief among them many tools and text editors expect a file with the .txt extension to be plain text files, not build scripts. [1] https://mesonbuild.com/Release-notes-for-1-1-0.html#support-for-reading-options-from-mesonoptions Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I90cc30833435f641223fe8e7f88458ae7fe1db95
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].