| commit | 6f7ee6335a79e2583c39efd7958cbe0474798be4 | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Tue Jun 11 09:51:39 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jun 11 16:12:29 2024 +0000 |
| tree | 72ff676d9b932fdd87f03430afac5325cd24940e | |
| parent | 9b664e95f79a66b515e360bf3cdce13e42d818ef [diff] |
Dump.Create: Add system dump path Update paths to include SYSTEM segment too, which is needed for xyz.openbmc_project.Dump.Entry.System interface Change-Id: I7ca769871c9cdc5ce7c4d4b80187f447bb169cb6 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
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