commit | 0ae40524799fc0030418dbcf2899ca55246a6386 | [log] [tgz] |
---|---|---|
author | Vijay Lobo <vijaylobo@gmail.com> | Tue May 11 18:51:45 2021 -0500 |
committer | Vijay Lobo <vijaylobo@gmail.com> | Thu May 13 15:09:15 2021 -0500 |
tree | d56b3931b2f5759844dd120c60782514a83916d4 | |
parent | 33458d4432a8323616622881f314a73cf0b04d97 [diff] |
Entry: Add EventId property Add a EventId property unique to this event. This property is to support Redfish API version v1_1_0 for LogEntry. There are 2 properties to ID the event. 1. Id - a unique number to identify an event 2. EventId - an optional identifier which is associated with this event and its implementation defined Signed-off-by: Vijay Lobo <vijaylobo@gmail.com> Change-Id: Iae23f78ebac0ce55a3db54ac0c73cbf2e6c05be2
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true
-Ddata_org_open_power=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir