commit | 2bcb4b4f008ea70645ef6d755cc5967bd2bccfae | [log] [tgz] |
---|---|---|
author | SunnySrivastava1984 <sunnsr25@in.ibm.com> | Tue Dec 01 21:56:34 2020 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Mon Dec 14 14:47:23 2020 +0000 |
tree | 2941d811a59bd06ebb713e604d201a3b4b71661e | |
parent | 41490f2da59124728b36b6a209f5984d7cba6ea8 [diff] |
Addition of Location code interface. This commit adds an interface yaml to publish location code of an inventory item. It will furnish data to the property ServiceLabel, under Location->PartLocation on bmcweb, which will be used to publish location code of any item. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: I9eaf6b539fe97d1df6d8d992980b96668b88d800
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