| commit | 73c931fb942daa714bfff17e950b9d5622a25842 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Oct 03 11:00:29 2024 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Oct 07 11:01:21 2024 -0400 |
| tree | 73ffcdf05ca60900884f1f7978509bd1a81da461 | |
| parent | 9d46e5bb0fcad6c4a775dcef781c0ce4b9de1ff5 [diff] |
Logging: add event for clearing The phosphor-logging had an internal event reported for when the event log is cleared. Create an equivalent event here for better documentation (and using the new event format). Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ia8e0e329c5a2818376f0fb313531a1040af23dd6
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