| commit | 3c5b76491afb8401627fc343077fe420f8a5e7f9 | [log] [tgz] |
|---|---|---|
| author | Chu Lin <linchuyuan@google.com> | Tue Jul 20 20:38:09 2021 +0000 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Thu Sep 30 13:37:48 2021 -0400 |
| tree | 4dc12ef0d9833a1c134f8c42ccd7052dc2411558 | |
| parent | 7e624b6a4ab51bf72cb7c6a2d17afedc0be08b4a [diff] |
Add the cable interface The cable interface is used to represent a cable instance in ipmi inventory Design Doc: https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/45395 Signed-off-by: Chu Lin <linchuyuan@google.com> Fixed minor whitespace issue and added meson.build. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: Ia917288efd343dd77cdb57ee0c863ec4dfac096e
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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir