| commit | 937eaaf8c00f88f71be86f5e1b7a1b31364b0b2b | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 03 10:17:59 2021 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 03 10:18:01 2021 -0600 |
| tree | 9e7353c9ebdeb5d9f6e1f07320dd6a14d6855dab | |
| parent | bdf8719fe803bee219b9a4cef7e8cbcc653a641a [diff] |
meson: fix phosphor-logging dependency
When using the phosphor-logging dependency from the subproject, the
repository fails to build with a number of missing header errors:
../src/report.cpp:6:10: fatal error: phosphor-logging/log.hpp: No such file or directory
6 | #include <phosphor-logging/log.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
Phosphor-logging itself now uses meson, so it can be picked up as a
proper subproject dependency rather than attempting to find the header
files inside the subproject repository. Switch the meson dependency
invocation to fallback to the subproject appropriately.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9d90e245169366ff1046c30c516af871b5c64eb3
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].