| commit | bfcb5d0c39571cd5f0215d22e9f7fee0c23dfd59 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Nov 22 11:05:16 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 11 19:34:56 2024 +0000 |
| tree | 10a4352dd2346fa7a5cea207c8d7444cc322467d | |
| parent | 530ca6173befe2b88a8e71acb62d5eee79805951 [diff] |
Logging.Entry: Add 'AdditionalData2' as a dict of metadata In order to ease transition from vector to dict, add a new property for the time being. Existing code can transition to using the dict and then we can rename the property once everyone has moved to the dict format. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I4c918cb25021fd5434f6a50da7bbe3e0b2c2a4fb
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