| commit | f18b21e0e16a2ac5fe1600bcc35b8c89a7e51caf | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Sep 09 06:57:37 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Sep 09 06:57:40 2021 -0500 |
| tree | 882787aafe108f46f3ac7f432e3c12e48be89b1f | |
| parent | d81cff3c7a1b4b8f4a4442c26dcac3773e457ad2 [diff] |
various: fix error metadata for systemd rules systemd-journald requires that log statements are "KEYWORD=%printf" and any spaces would cause the journal metadata to be dropped. Fix a few of them I see in the repo. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I8c7f84bed0a919d5042e083bf3bd87001b10aaf9
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