commit | 991b2b8bdbc950f2a85aebfc29d1b34ea3264686 | [log] [tgz] |
---|---|---|
author | Vernon Mauery <vernon.mauery@linux.intel.com> | Mon Sep 26 16:16:45 2022 -0700 |
committer | Vernon Mauery <vernon.mauery@linux.intel.com> | Mon Sep 26 16:21:23 2022 -0700 |
tree | 2ce9e9d4964b8b6e8ba71191a1dd8e693e4eaeb6 | |
parent | a1a46a94405db4fc29d9ad695dee44e2214e4262 [diff] |
Port in intel-dbus-interfaces content This takes the com.intel.Control.* content from the intel-dbus-interfaces repo and puts it into the yaml/com/intel subdir. Tested: meson build -Ddata_com_intel=true && ninja -C build Configures and builds, creating a library with the com.intel.Control.* interfaces in it (inspected using nm) Change-Id: I42b07b734483a4a2c9ba89e1bcadbc08d5b074b5 Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.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