| commit | 03af686b17b03308e493e8bce41a3756b0c8173e | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Thu Oct 05 11:23:53 2023 -0700 |
| committer | Jagpal Singh Gill <paligill@gmail.com> | Tue Nov 28 14:11:49 2023 -0800 |
| tree | 3f537f881db3bf2f96979eadaf0b4f1e7363f3fb | |
| parent | a60ff8459393e8a043d203c02ee658c14c967ff0 [diff] |
phosphor-health-monitor: add D-Bus paths - Add the D-Bus paths for BMC metrics. - The code for these paths will be autogenerated in the common.hpp Change-Id: I3d0273d83136659d67b0907006fb050db948a732 Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir