| commit | 037a43e50495133744e151338f74c9a06986da44 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Jan 15 16:03:05 2024 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Jan 15 16:03:54 2024 -0600 |
| tree | 936dc19da9f0982f5fc150c9c42bbb7ff57836fa | |
| parent | 6f96e056d9cde20f07b8f38bd6f0b6111c967fa0 [diff] |
ObjectMapper: Add default paths The ObjectMapper service is expected to be at a specific location per the description. Document this with code constants as well. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I6623d56ae5cfd01a55ffe628bd68c5fcfd3da1dc
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