| commit | a74e44f6ef7db43d38eb600fbfee152b31b30514 | [log] [tgz] |
|---|---|---|
| author | Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> | Fri Jul 23 15:02:20 2021 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Wed Aug 04 14:52:46 2021 +0000 |
| tree | 103c33cc2cfa03c698d7462a779680166bdada9f | |
| parent | 3a617023eacf8a7fcc49e15d5767b35f47c7c089 [diff] |
Extending meson build system to support fast compilation during development stage Tested compilation against 3 build configurations - with lto for src and tests/src (for release sw): all: ~3 min; change in cpp file: ~2 min - with lto for src and no_lto for tests/src (for release sw): all: ~2 min; change in cpp file:~ 40 sec - after using scripts/configure_fast_compilation.sh (for development only): all: ~1.75 min; change in cpp file: ~20 sec Signed-off-by: Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> Change-Id: Idf435d8455260d2d988cb7286d71401f21fd03e2
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].