commit | 61465db5edd8eca02da92eb43cbbff5e0a129216 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Oct 30 14:53:11 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Oct 30 16:21:25 2020 -0500 |
tree | 374dc1137b406e0a0982b7aa9a71b5f9e78e6820 | |
parent | 6e36587a1f6838d594c7df8382636b71a6044032 [diff] |
meson library and dependency cleanup Change-Id: I09e3c514dfc67b701bf09a6e079ad3a5d9344fca Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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