| commit | cfc8707515c42a25fec386127e374163d3c9ffe7 | [log] [tgz] |
|---|---|---|
| author | Brad Bishop <bradbish@qti.qualcomm.com> | Tue Jul 29 17:21:46 2025 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Aug 11 15:23:09 2025 +0000 |
| tree | 4adb8ccd5620436c59d2cc7acbcb5e328c0341e0 | |
| parent | ac40045f3b6c68a1dfd68b053d434d5bf0bd4ac8 [diff] |
meson: subproject as system dependency When phosphor-dbus-interfaces is a subproject, use -isystem for phosphor-dbus-interfaces headers. This is a signal to, for example static analysis tools, that the phosphor-dbus-interfaces headers are to be treated as if they were installed in the compilers default search path (e.g. /usr/include). Change-Id: Iaa94b339c689cb47abcaed49a397bc60518f48c3 Signed-off-by: Brad Bishop <bradbish@qti.qualcomm.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