commit | a39c66ae86c5e5bdfdeb88da3f79e31407c45581 | [log] [tgz] |
---|---|---|
author | Asmitha Karunanithi <asmitk01@in.ibm.com> | Tue Sep 21 11:05:50 2021 -0500 |
committer | Asmitha Karunanithi <asmitk01@in.ibm.com> | Mon Jul 11 04:45:20 2022 -0500 |
tree | 82d0e2da512afe4142d7d74cd5a6cdcb17430204 | |
parent | dac7f6c39a5e627a9856723e40819f06bca11b61 [diff] |
Add a new interface "OriginatedBy" This interface can be implemented by the dbus objects of any application/service that has a requirement to store the identity of the "originator" that has caused the activity. This unique id is stored in the "OriginatorId" property and "OriginatorType" helps identify the type of originator. Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com> Change-Id: Ia96592bbe4a7b0057fe66f8e1f09d73837978c30
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 and org/freedesktop 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