| commit | 3cfcc9c0eb86954846daacb7a05e3293b9864659 | [log] [tgz] |
|---|---|---|
| author | Adriana Kobylak <anoo@us.ibm.com> | Tue Mar 26 09:06:13 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Apr 03 03:11:02 2024 +0000 |
| tree | f0118bb64b6fa172055e7399060997d4cc95f17a | |
| parent | ab761c09bec3d1a62d7d543966a6eaccf2bb1103 [diff] |
software: README: Add Minimum Version Add the description of a new MinimumVersion interface that would hold the information set by the user when choosing to compile the phosphor-bmc-code-mgmt repo with the minimum ship level check option. Change-Id: Icd94700d0f684df92245641b324a0f227c59fb3f Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
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