commit | 05cf69547eb8fd820b2362a7d49a55171070f3f6 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Feb 17 09:01:55 2022 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Feb 17 10:35:38 2022 -0600 |
tree | dafc8cd348baa59f36feb3df7c559b81b1175182 | |
parent | 4f40f2f3cc6f26eef528c728df87d9ecd554ac85 [diff] |
run-ci: ensure old generated content is removed Remove the old generated directories before re-running the generate script in order to detect if spurious files are left in place. See I9dcc51fd23f2dac56b7b8efca57ca789e3075309 as an example of spurious files previously being identified. Tested: Pushed this change to Gerrit in front of I9dcc51f and confirmed the CI failure that is fixed by that commit. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ia27fbe11f8ef6399da05bbeb741e818e77d859cf
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