| commit | 097188ac4f10033e2ae407e4e264c446eaf79006 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Tue Feb 27 16:15:37 2024 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Feb 27 22:26:14 2024 +0000 |
| tree | 5878b584a5a42b7a54ef2d444e2e9bf78ad9b9ad | |
| parent | 871f75569898fedfc48a8f56b146866e8bf4ef95 [diff] |
Inventory.Item.MemoryBuffer: remove unused interface There are no uses of this interface in the whole organization so, remove it. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I9b91cd6e4b287dcbf1884d1c586ecf44a56de2e4
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