| commit | 219368bedb6a8607a50ec9ad9129478e45cdd68f | [log] [tgz] |
|---|---|---|
| author | William A. Kennington III <wak@google.com> | Wed Oct 26 14:47:20 2022 -0700 |
| committer | William A. Kennington III <wak@google.com> | Thu Nov 10 23:44:53 2022 +0000 |
| tree | 96e879d33da475d00387df7456806d8490599bac | |
| parent | e7c10bd5cdab6cd898e5cad0daab8c1128adc0c8 [diff] |
Network/VLAN: Remove InterfaceName Having the interface name is redundant with EthernetInterface and nothing currently relies on this version of the value. Change-Id: I53e700dae937059c2fd415bf7d546a8c887b68d4 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++.
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