| commit | 90116920633cdd49e68508d8009d2fec24237539 | [log] [tgz] |
|---|---|---|
| author | Jonathan Doman <jonathan.doman@intel.com> | Mon Nov 01 17:26:07 2021 -0700 |
| committer | Jonathan Doman <jonathan.doman@intel.com> | Mon Nov 01 18:14:53 2021 -0700 |
| tree | 94fb88cbecc956ed89d313249baa7850762b9ab3 | |
| parent | 4a3bfcaf4a5ac066cc6b3a63a9fae7143f8d7b7d [diff] |
Fix install_subdir setup error meson 0.60 gives the following error when attempting to setup: meson.build:100:0: ERROR: install_subdir keyword argument "exclude_files" cannot be absolute It's due to an internal change in string path construction. See https://github.com/mesonbuild/meson/issues/9450 for a related bug report. Technically this behavior should go away with the next meson release, but we can harden our own meson.build rather than rely on undocumented behavior regarding whether or not the trailing slash will be removed. Tested: `meson setup` is successful with meson 0.60 Change-Id: I34a919586975dffb4cfe71e77dcca31e5902af36 Signed-off-by: Jonathan Doman <jonathan.doman@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 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