| commit | 871f75569898fedfc48a8f56b146866e8bf4ef95 | [log] [tgz] |
|---|---|---|
| author | Jayanth Othayoth <ojayanth@gmail.com> | Tue Feb 27 00:16:55 2024 -0600 |
| committer | Jayanth Othayoth <ojayanth@gmail.com> | Tue Feb 27 00:57:23 2024 -0600 |
| tree | cda9321de5d9034386caa1eabace44b748605ffc | |
| parent | 3ae7aa84d385906c5c8ce44168129d991d60d1b8 [diff] |
Dump.Entry.FaultLog: interface restructure Moved Dump.Entry.FaultLog.FaultDataType enum definition to common folder. This to to use FaultDataType enums in different interfaces. Tested: Build verified. Change-Id: I1073ab5e558fc5444a4164492ebb36682dc51e8d Signed-off-by: Jayanth Othayoth <ojayanth@gmail.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