| commit | 855b46f32ad385b9e26cf3a2c1e3a547e0eb8632 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Jan 15 16:21:40 2024 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jan 17 13:30:40 2024 -0600 |
| tree | 6234d445b64ef22bfae8ed7756c1d1d37b778021 | |
| parent | 037a43e50495133744e151338f74c9a06986da44 [diff] |
State: add default paths for BMC,Host,Chassis Add namespace and path constants matching those in the README for programmatic use. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ice4e14716b2de6477f3dd7c15e53cc7bdb68270f
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