| commit | e6718c5e42ec886e4c1d3e4dd1a4be093721c548 | [log] [tgz] |
|---|---|---|
| author | Ivan Mikhaylov <fr0st61te@gmail.com> | Fri Jun 09 17:07:00 2023 +0300 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jun 21 20:04:29 2023 +0000 |
| tree | 0490cb8f11f0b198a10832a43c196afb8686a51c | |
| parent | 7720dd643bc7a6e59ba53ce218559b72189b9710 [diff] |
network/client: add TCP/UDP as Transport Protocol for Client Add TCP/UDP transport protocol for Client interface to make it use for different applications like rsyslog as example. Change-Id: I08511a1a70396e1c6fb979febfa8fb7343235e9d Signed-off-by: Ivan Mikhaylov <fr0st61te@gmail.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