| commit | 45b095d5d02ccf4039f87d8273e3194f0c42da03 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 12 11:15:07 2023 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 12 11:15:07 2023 -0500 |
| tree | fa620ef5d2063741f8387afb6b1cf0e0029dcab6 | |
| parent | 88902e67bcd86b2122b4c1f3b1eaa550b329b08a [diff] |
build: upgrade to C++23 Meson 1.1.1 and GCC-13 both support C++23 and a sufficient portion of the standard has been implemented. Upgrade the build to leverage it. Change-Id: I7bb2188a9627a7390574e8d930bec671c15205f1 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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