| commit | 4aec8027acae734a1dbc6334d53fd66ab854b81c | [log] [tgz] |
|---|---|---|
| author | Willy Tu <wltu@google.com> | Thu May 20 23:57:16 2021 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 22 21:56:52 2021 +0000 |
| tree | e5f4096a3f909ef7af7afbbaf0613965f45dcf05 | |
| parent | 0170a765942a3432976e06e975c07f22ed3bb8a7 [diff] |
Software: Settings: add setting to Software interface Added the xyz.openbmc_project.Software.Settings interface to provide the user with some control over the Software it manages. Currently, it only has `WriteProtected` that indicate if the software is writeable or not. The settings are enforced by the service that manage the property. Change-Id: I726c247428b4e1c8b1fe9cf66554ef272bbcd231 Signed-off-by: Willy Tu <wltu@google.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 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