commit | b2bbac7e2986decf1ed5d102e79f1872ddd84881 | [log] [tgz] |
---|---|---|
author | Wludzik, Jozef <jozef.wludzik@intel.com> | Thu Jan 21 12:52:01 2021 +0100 |
committer | Wludzik, Jozef <jozef.wludzik@intel.com> | Thu Feb 11 12:24:30 2021 +0100 |
tree | 849e53ad889fa118c55d143f075d897a4b7c313a | |
parent | 4461e14097547ca2b85945e371c260c40a5d6d86 [diff] |
Add Trigger and TriggerManager interfaces Trigger and TriggerManager interfaces design are based on Telemetry design. Interfaces be implemented in openbmc/telemetry repository. Ref.: https://github.com/openbmc/docs/blob/master/designs/telemetry.md Signed-off-by: Wludzik, Jozef <jozef.wludzik@intel.com> Change-Id: I41c31aa2ae091d3283ddb4ec422885483f4d0429
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir