| commit | 453957cd164f46856b8f64a14a55c89dedb41011 | [log] [tgz] |
|---|---|---|
| author | Zhenwei Chen <zhenweichen0207@gmail.com> | Thu Mar 31 17:54:17 2022 -0700 |
| committer | Zhenwei Chen <zhenweichen0207@gmail.com> | Tue Apr 19 15:11:39 2022 +0000 |
| tree | 1cd82edeb3156db4b59b34a624eb236d8c339a82 | |
| parent | a12b0b3b37dd8e2b37b559410fe127d8a582affa [diff] |
Rename the reverse_name to reverse_names in associations.
It will allow two different associations with the same name and
different reverse_names.
For example:
associations:
- name: forward_name
reverse_names:
- reverse_name_A
- reverse_name_B
required_endpoint_interfaces:
- endpoint
Will have two associations:
- [forward_name, reverse_name_A, endpoint]
- [forward_name, reverse_name_B, endpoint]
Change-Id: Ia01ae59b7dba1556e7c7f8e56ccede47d623c1a1
Signed-off-by: Zhenwei Chen <zhenweichen0207@gmail.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 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