| commit | 208b4e423f6686d6fd54bedd93ad80f95639bd98 | [log] [tgz] |
|---|---|---|
| author | Vijay Lobo <vijaylobo@gmail.com> | Thu May 06 14:56:35 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jun 29 19:42:12 2021 +0000 |
| tree | 25bfe8f43f3ccbadcd71702e042effac63806b09 | |
| parent | 08e8099ef3210afdf0f076c075d096a88ca6e128 [diff] |
Entry: Add ServiceProviderNotify property Add a ServiceProviderNotify property that can be used to indicate that this event log should be notified to the service provider, if that is implemented on the system. Signed-off-by: Vijay Lobo <vijaylobo@gmail.com> Change-Id: I65029020aed35c069d10058159792a75ba188048
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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir