| commit | 90cfce16584253a5f524c718ce5a6ae7c33f7b8c | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 27 14:32:07 2024 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 27 14:32:09 2024 -0400 |
| tree | 0ccb9ec09a5f0395f29c9fdd27bd60a5ebbcff92 | |
| parent | 5133c7bfa8127e8a4ea339c439675ad018911363 [diff] |
Logging.Create: return result path from create call When a daemon creates an event or error entry it is sometimes helpful to be able to look up that entry later, for example to mark it as resolved. Add a return to the method call for this. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ia010e53fda55cef8b9cfc948482e133f20040320
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