commit | d37091affcd933b7bc7cfd0ac393e2dd539f0235 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 11 14:24:21 2020 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 11 14:24:23 2020 -0600 |
tree | 22317ba8151931f22292d0ff26bcbccbc0412319 | |
parent | 2c33a8992449471f566fdfdaa629fae27ac572f8 [diff] |
object-mapper: document error returns on methods The ObjectMapper can return errors in cases where a query results in no services and/or object paths: Common.ResourceNotFound. Add this to the interface definition as documentation. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I09f82afc07f2a3281787b0adf7f6841be23621e9
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