commit | 47409124aaf297a8bc0b883e55f2ced50cd15cb8 | [log] [tgz] |
---|---|---|
author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Wed Jan 13 07:39:25 2021 -0600 |
committer | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Fri Jan 15 07:54:11 2021 -0600 |
tree | 7ac1da27a385766a5510853580c4893d110f26be | |
parent | 962f955868979f588c32a9cfe927ef66ad0b361c [diff] |
Add NotAllowed error to dump create and initiateOffload. Certain dump creation may not be allowed during all the time so adding a new error "xyz.openbmc_project.Common.Error.NotAllowed" to the list of errors, similarly dump offload also cannot be done always so adding that error to initiateOffload too. Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> Change-Id: I079f3a0977ebce99d7ec3d4974b569040615e908
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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir