commit | 985388a8a5960e234182a0f3cb9cbaf7a8f3b91e | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 24 16:35:46 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 29 13:19:15 2022 -0500 |
tree | afa8d76fcb2fac95a5f35d3ee281b675e259027e | |
parent | edfcbc38ef12b8b9b8b52a2ead9e11bb70917cbb [diff] |
Create test-only version of util_lib Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ifd63af2772b936ec07ca4bbcf13c70429ffd5693
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