commit | 6a0b5030509d7b3ec24918ea247395f56bbb71c3 | [log] [tgz] |
---|---|---|
author | William A. Kennington III <wak@google.com> | Thu Aug 25 14:39:56 2022 -0700 |
committer | William A. Kennington III <wak@google.com> | Thu Sep 01 12:50:08 2022 -0700 |
tree | 9f2600ae61067e05c75bcae25c6debf21f4362f5 | |
parent | d67b2627fd1d16ad96866c6288d54bcf63a992e3 [diff] |
Network: Set const properties where desired We currently throw our own exceptions in these cases when we should just be leveraging the generator and properly exposing our intention. Change-Id: Ib16f95f1f04f7da8313c68245475ea87fec29e0b Signed-off-by: William A. Kennington III <wak@google.com>
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