| commit | c35b70189ddf99f23498acedf9601c312b02a42c | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Tue Mar 04 11:38:29 2025 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Mar 05 21:06:19 2025 +0000 |
| tree | b949e30a4515f562a6ad2c954c48f06434bf42f5 | |
| parent | 90d5f80a72270ea6eff9adbc5bd5049cf7ea877d [diff] |
registry: add registry_target to the external dependency When PDI is used as a subproject, we need some dependency that indicates the registry is populated. Add the internal build rule to the primary external dependency so any dependency on PDI satisfies the registry population. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Id16b4c272a82f5451e58b271e02a622b108ffaa3
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