commit | 8018391d05873634c1771ebfffca398b30d7ca90 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Dec 21 11:52:25 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Dec 21 11:56:22 2021 -0600 |
tree | 312b030178f2470f32df7e603935ea84bbd6fc62 | |
parent | 15527a43fe309d3599d146d5a48607b14b426a37 [diff] |
create fallback gtest subproject dependency Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I6b0ce32242a0a74b56f4a163cfb3a1e15fe8a7ee
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