| commit | 359b7664358d82032465650529a553d27634a809 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 12 11:15:49 2023 -0500 |
| committer | Adrian Ambrożewicz <adrian.ambrozewicz@linux.intel.com> | Wed Dec 27 11:25:25 2023 +0000 |
| tree | 5b222d99f2427a8437bd21990337d0a2e4d3e82d | |
| parent | c7935fa17008a5822567c7b702289bb10fe223a3 [diff] |
build: upgrade to C++23 Meson 1.1.1 and GCC-13 both support C++23 and a sufficient portion of the standard has been implemented. Upgrade the build to leverage it. Change-Id: If193a9f16c90ba8ac423aec7e5660bea524ce891 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].