| commit | 2faed8a3c3d8cb05a026c3bb7516b4824471f338 | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <ed@tanous.net> | Wed Nov 27 10:59:57 2024 -0800 |
| committer | Ed Tanous <ed@tanous.net> | Fri Jan 24 16:28:39 2025 +0000 |
| tree | d5110ee0e065695ff496a41aeb27f61c4cd3eb0b | |
| parent | d25367bd9726a479eddbec85c51722d62043c724 [diff] |
Break apart trigger interface Having this large type creates confusion for translation. Splitting this parameter into two fields allows us to remove the variant property altogether, and allows splitting the rules for each type into their own description. The only users of this are bmcweb and telemetry, both of which have patches up to effect this change under the same topic. Testing in those patches. Change-Id: I51a1dd3fe0619aa7a75f92764875552feda01a92 Signed-off-by: Ed Tanous <ed@tanous.net>
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