| commit | dc48725c1fe945ef92d4b0f8ad4a2c9572a1f7fb | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Tue Jul 07 16:15:07 2020 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Oct 08 13:45:31 2020 -0500 |
| tree | b64fd3a08fabe030ff88422ccafed97ea4c02861 | |
| parent | feeacfe06de6d32de43750500c9729f141ba6bac [diff] |
inventory.decorator: define CLEI interface Some products, especially in the telecom space, have an assigned CLEI number. See https://tools.ietf.org/html/rfc4152 . Define an interface to store the CLEI. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I8a3499a4e76b0605414ce702a76c01e126536dca
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