meson: adjust nlohmann-json dependency

Simplify the dependency directive and align with the usage in other
repositories.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I6b140e3a26314de110902bb4dceb1e8c57d80c3c
2 files changed
tree: 249107dd424bed43dffc0da7b7febbceeca85261
  1. subprojects/
  2. test/
  3. .clang-format
  4. .editorconfig
  5. .gitignore
  6. .prettierrc.yaml
  7. dbusSensor.cpp
  8. dbusSensor.hpp
  9. dbusUtils.cpp
  10. dbusUtils.hpp
  11. exprtkTools.hpp
  12. LICENSE
  13. meson.build
  14. meson.options
  15. OWNERS
  16. phosphor-virtual-sensor.service.in
  17. README.md
  18. thresholds.hpp
  19. virtual_sensor_config.json
  20. virtualSensor.cpp
  21. virtualSensor.hpp
README.md

phosphor-virtual-sensor

phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json from one of three locations:

  1. The current directory.
  2. /var/lib/phosphor-virtual-sensor
  3. /usr/share/phosphor-virtual-sensor

By default the repository will install a sample config into (3).

There are two types of data in this file.

virtual sensor configuration information

See virtual_sensor_config.json in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.

information to get a virtual sensor configuraton from D-Bus

For example:

{
  "Desc": {
    "Config": "D-Bus",
    "Type": "ModifiedMedian"
  }
}

Sensors added this way can only use a set of restricted calculations. Currently the only type supported is modifiedMedian.

The virtual sensor configuration information needs to be added into the relevant hardware configuration file in entity-manager. This method of adding a virtual sensor allows a recipe that builds for different hardware configurations to have different virtual sensors for each configuration.

The virtual sensor configuration in entity manager follows a different format to the JSON in virtual_sensor_config.json (specified in entity-manager/schemas/VirtualSensor.json).