commit | 6c25fd029fcb359ec5f0ab1f039f4ec3aaca7f5c | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Jan 17 11:52:54 2024 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jan 17 13:30:40 2024 -0600 |
tree | 8aada627f3b946d7b3dcf0aa09db78d7f60d940e | |
parent | 84591a23574b2810158694c6c1c92bd27328a0ac [diff] |
Logging: add default path and service names Add default paths and service names from the reference implementation in phosphor-logging. The service for logging is expected to be a singleton and the manager object resides at a fixed path. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ia8d4ec354dbbe234109562bd76f1f779922da4e0
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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir