| commit | 0aadbe41aadd155d91e2bda1c471ac85a7dffee9 | [log] [tgz] |
|---|---|---|
| author | Ravi Teja <raviteja28031990@gmail.com> | Fri Jan 12 04:32:25 2024 -0600 |
| committer | Ravi Teja <raviteja28031990@gmail.com> | Fri Jan 12 04:36:52 2024 -0600 |
| tree | 23a8589a888c3a9b66bbffb3168dc6ce0cbc4a66 | |
| parent | 7da02bdee08f558b26e933a9dfba51362ada999b [diff] |
Add Hostname property errors Hostname does not allow special characters while setting hostname this commit adds InvalidArgument error to handle invalid hostnames Change-Id: I2ecc92637364baebe9e845bd22099fcb9744c2f4 Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
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