meson: pldmtool: fix subproject build
pldmtool uses headers from phosphor-logging for lg2 support, but
was missing the phosphor-logging dependency. Add the dependency
back in, which fixes subproject-based builds.
Without this change the following failure is observed:
```
In file included from ../pldmtool/pldm_cmd_helper.hpp:4,
from ../pldmtool/pldm_cmd_helper.cpp:1:
../common/utils.hpp:15:10: fatal error: phosphor-logging/lg2.hpp: No such file or directory
15 | #include <phosphor-logging/lg2.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
```
With the change, the build is successful.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id4ca9e7a01e3dfb8b93cbb8da4094264923c3e4d
PLDM (Platform Level Data Model) is a key component of the OpenBMC project, providing a standardized data model and message formats for various platform management functionalities. It defines a method to manage, monitor, and control the firmware and hardware of a system.
The OpenBMC PLDM project aims to implement the specifications defined by the Distributed Management Task Force (DMTF), allowing for interoperable management interfaces across different hardware and firmware components.
To build and run PLDM, you need the following dependencies:
MesonNinjaAlternatively, source an OpenBMC ARM/x86 SDK.
To build the PLDM project, follow these steps:
meson setup build && meson compile -C build
The simplest way of running the tests is as described by the meson man page:
meson test -C build
Alternatively, tests can be run in the OpenBMC CI docker container using these steps.
pldm daemon accepts a command line argument --verbose or --v or -v to enable the daemon to run in verbose mode. It can be done via adding this option to the environment file that pldm service consumes.
echo 'PLDMD_ARGS="--verbose"' > /etc/default/pldmd systemctl restart pldmd
rm /etc/default/pldmd systemctl restart pldmd
For complete documentation on the functionality and usage of this repository, please refer to the docs folder.