| commit | 8b8f606fc7219d5cd7fbf94646a2bf44d8f98f31 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Aug 27 14:53:50 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Aug 27 14:56:47 2021 -0500 |
| tree | 855095504b6995279c55bdf3a54dc5bf6613dbd8 | |
| parent | 1889ebf11732ba5c01e650d6d3ca142dd0033619 [diff] |
build: use nlohmann-json dependency Many sources files want to use the 'json.hpp' file from nlohmann, but when this is installed as a subproject it isn't in the default search path, unless a dependency to it is explicitly added. In most cases this is pulled in via the 'Thresholds.hpp' file which is in-turn linked in by the thresholds static library. In meson, static libraries shouldn't be linked against directly but instead indirectly through a 'dependency' relationship, otherwise the implicit header file needs are not able to be communicated up to users of the library (such as Thresholds -> json.hpp here). Revamp the static library relationships to use 'dependencies' rather than 'link_with' so that the header file needs are properly expressed. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Id78aee6af03f10c555aa84edbe9ec44ac04ec342
dbus-sensors is a collection of sensor applications that provide the xyz.openbmc_project.Sensor collection of interfaces. They read sensor values from hwmon, d-bus, or direct driver access to provide readings. Some advance non-sensor features such as fan presence, pwm control, and automatic cpu detection (x86) are also supported.
runtime re-configurable from d-bus (entity-manager or the like)
isolated: each sensor type is isolated into its own daemon, so a bug in one sensor is unlikely to affect another, and single sensor modifications are possible
async single-threaded: uses sdbusplus/asio bindings
multiple data inputs: hwmon, d-bus, direct driver access