Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 7619ab783e9dddf4d8602022889e2ae8641f23db
commit7619ab783e9dddf4d8602022889e2ae8641f23db[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Wed Nov 29 06:44:58 2023 -0600
committerZane Shelley <zshelle@us.ibm.com>Thu Nov 30 20:17:38 2023 +0000
treee81ce36c1821806b8d96925e6385ced14b1250b1
parent3907c7a739710aa94749431a9de8451d7b56e186 [diff]
build: use allowed over enabled

Meson feature options are typically in a tri-state of enabled, disabled,
or auto.  The enabled and disabled functions on an option (from
`get_option`) no longer return true for auto features.  Instead, the
expectation is to use `allowed()` which is true for both enabled and auto.

Switch all uses of `enabled` to `allowed`.

Change-Id: I2253ebff36b49c4b79b803175dd76668f8ac2ba8
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
4 files changed
tree: e81ce36c1821806b8d96925e6385ced14b1250b1
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .eslintignore
  8. .gitignore
  9. .prettierignore
  10. .prettierrc.yaml
  11. buildinfo.hpp.in
  12. cli.cpp
  13. cli.hpp
  14. config.h.in
  15. LICENSE
  16. listener.cpp
  17. listener.hpp
  18. main.cpp
  19. main_nl.cpp
  20. meson.build
  21. meson.options
  22. OWNERS
  23. 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