| commit | bff28e0227cf62f61dedd8a47634f1eeec24f8b8 | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@inspur.com> | Wed Aug 16 09:52:50 2023 +0800 |
| committer | George Liu <liuxiwei@inspur.com> | Wed Aug 16 09:52:50 2023 +0800 |
| tree | c2a1e8bd8f9a0e90465db33e214d942247401fa3 | |
| parent | 402dc6a5beee58ee1e6514a425c542a0d879954c [diff] |
meson_options.txt: Support for reading options from meson.options Support has been added for reading options from meson.options instead of meson_options.txt[1]. These are equivalent, but not using the .txt extension for a build file has a few advantages, chief among them many tools and text editors expect a file with the .txt extension to be plain text files, not build scripts. [1] https://mesonbuild.com/Release-notes-for-1-1-0.html#support-for-reading-options-from-mesonoptions Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I42eecc9dec19ae68d6cf04c55be7d6a7f6acba7c
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