| commit | 402dc6a5beee58ee1e6514a425c542a0d879954c | [log] [tgz] |
|---|---|---|
| author | Michal Orzel <michalx.orzel@intel.com> | Thu Jul 27 15:33:12 2023 +0200 |
| committer | Michal Orzel <michalx.orzel@intel.com> | Mon Aug 07 15:10:57 2023 +0200 |
| tree | 6c51c6195c9ea6f3bba109ba626c80bbaa923d7b | |
| parent | d1484a1499bc241316853934e6e8b735166deee2 [diff] |
Change authority D-Bus names Changing authority service references in code from 'ldap' to more generic name, to comply with change in phosphor-certificate-manager. Related change: https://gerrit.openbmc.org/c/openbmc/phosphor-certificate-manager/+/65458 Tested: Docs change, no way to test. Change-Id: I3b502f27b5f3dd1585238cdad24ab071cccc605f Signed-off-by: Michal Orzel <michalx.orzel@intel.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