commit | a9825f2ff27a6a941179a1634dfefbf9cee4ca74 | [log] [tgz] |
---|---|---|
author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Sun Nov 22 21:07:57 2020 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jan 12 15:25:12 2021 +0000 |
tree | 1dda5b0c4fc8b34dd18ce33ce1be3b41d0457b01 | |
parent | 8f40d35bdd83a032987c5dbbbd6fced8fe3a866e [diff] |
Update Notify method to remove unused DumpType DumpType is no more valid since there is there will be one unique dump manager per dump type. So the implementation need to call the right dump manager based on the path. so removing the redundant option of passing dump type. Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> Change-Id: Ib8ddacad04954599c6247487e25f460bc8df9b80
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