commit | e1693dabac7dbbf6424f982faa125f4e2e643ba3 | [log] [tgz] |
---|---|---|
author | Gunnar Mills <gmills@us.ibm.com> | Fri Nov 20 14:18:54 2020 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 11 17:44:27 2020 +0000 |
tree | cde08427c629cbf0d23d6352b69899938a1c1a11 | |
parent | d621780549da8a9b4f3161d3405dfff468faf63b [diff] |
Add Version AlreadyExists Error Heard from users it is hard to know why the image failed to upload in this case. Will use when the version is already on the device. Change-Id: Ibbbda073e16c2ca45700d5e22b368c07d440d412 Tested: Built with phosphor-bmc-code-mgmt and bmcweb changes and saw the error. Signed-off-by: Gunnar Mills <gmills@us.ibm.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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir