| commit | e5899eb58c62cd5ae6b1dee424691902de2ad52b | [log] [tgz] |
|---|---|---|
| author | Ramesh Iyyar <rameshi1@in.ibm.com> | Tue Jul 27 05:32:55 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jul 27 22:00:56 2021 +0000 |
| tree | 3b3fab79e97ce91dcfab10804fb4f4bfa6991f8d | |
| parent | 6ff65610dace799b4c60ac4d18b3417586e303da [diff] |
DeleteAll and Delete: Added additional errors The system or object may not be in a state to delete the object either "permanently" or "temporarily" so the added errors can be used accordingly by the object implementor. - xyz.openbmc_project.Common.Error.NotAllowed - If the object cannot be deleted permanently. - xyz.openbmc_project.Common.Error.Unavailable - If the object cannot be deleted temporarily. Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com> Change-Id: I1896dba4b936c263880244ee0f8b5248298ab5d1
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 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