commit | c252894d1fe965a331d7625394ed9d82fd0a8ac2 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 02 15:42:42 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 02 15:42:42 2020 -0600 |
tree | 1c68ef5504a1985a099a969b5dce8a40ed9ff6d0 | |
parent | f80482a5017a898ee69fec57d15a6201a6fcbbd5 [diff] |
clean up libraries in meson.build files Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I6ca90bb9d02243413fc5e0b85001666e836a435c
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