| commit | 25b1bcba49c71ffa0ca70a32ae696e25795843a0 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 11 14:38:45 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 11 14:38:47 2024 -0500 |
| tree | 15272ac6f5e58a76aa909017b8034bb8aab3f676 | |
| parent | bfcb5d0c39571cd5f0215d22e9f7fee0c23dfd59 [diff] |
Logging.Entry: switch 'AdditionalData' to dict of metadata All client users of AdditionalData have moved to AdditionalData2, which is already a dict. Switch AdditionalData to be a dict as the next part of the migration. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic18c8f9eb9804a1221482a96dd682817816d76d9
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