Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / d9573f489eae420fc73709ed62eabb68dad444ff
commitd9573f489eae420fc73709ed62eabb68dad444ff[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Wed Dec 02 15:52:06 2020 -0600
committerZane Shelley <zshelle@us.ibm.com>Wed Dec 02 15:52:06 2020 -0600
tree9ac379626e5be7fdeb6a4ae0c4007c0e8c9eb32e
parentc252894d1fe965a331d7625394ed9d82fd0a8ac2 [diff]
Clean up meson.build for reabability

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: Ibcf5898075661fee6be1bba402abc2c005061892
1 file changed
tree: 9ac379626e5be7fdeb6a4ae0c4007c0e8c9eb32e
  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