| commit | 588ca2b8cdecd8b28ae840cbd9a2ed7a0bdabdd2 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Jan 30 17:48:11 2025 -0500 |
| committer | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 03 14:25:59 2025 -0600 |
| tree | d9903f81440b58cc3cd01794f45dca908dec46ba | |
| parent | 85d42b14c2aa4f647146a0d1633f64e8c0dd1c81 [diff] |
build: use allowed over enabled or not-disabled 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`. Switch all uses of `not disabled` to `allowed`. Change-Id: I2f446393dfb207d1429ec4a3a0c6b66f23e30ec7 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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.
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