Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 13683089432cbfb152ff9fdffb978cb1fdbe7a54
commit13683089432cbfb152ff9fdffb978cb1fdbe7a54[log] [tgz]
authorBen Tyner <ben.tyner@ibm.com>Thu Jun 25 12:49:47 2020 -0500
committerben.tyner <ben.tyner@ibm.com>Thu Jun 25 18:01:45 2020 +0000
tree60148cf0ae73f210597dceaa7d2ed0217d530154
parent792f32f7073a47e2feb340514aea32c1875ad0dc [diff]
Allow building locally without phosphor-logging

Check for phosphor-logging available. It is only available when building
via CI, SDK or if phosphor-logging and associated dbus support has been
installed locally. If phosphor-logging is not available then compile in
minimal logging code. This allows for local testing of changes that are
not affected by or depend on phosphor-logging.

Change-Id: I1b4d54c36b181596beff465307c16ca33f2f91d8
Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
3 files changed
tree: 60148cf0ae73f210597dceaa7d2ed0217d530154
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .gitignore
  8. cli.cpp
  9. cli.hpp
  10. LICENSE
  11. listener.cpp
  12. listener.hpp
  13. main.cpp
  14. main_nl.cpp
  15. MAINTAINERS
  16. meson.build
  17. meson_options.txt
  18. README.md
README.md

Hardware Diagnostics for POWER Systems

In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.

Aditional details TBD.

Building

For a standard OpenBMC release build, you want something like:

meson -Dtests=disabled <build_dir>
ninja -C <build_dir>
ninja -C <build_dir> install

For a test / debug build, a typical configuration is:

meson -Dtests=enabled <build_dir>
ninja -C <build_dir> test