commit | 4e3faa232a0cb7aa222e84c21b4692dc9840603c | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Sep 17 10:04:40 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Sep 17 21:27:50 2021 +0000 |
tree | e73453561416d844186ba84c646f082329e44799 | |
parent | 7f6ce6ac79a57984a89fbc959d9772d5f9736c77 [diff] |
Meson project update to v50.0 There was a recent change in our meson files that requires a feature that was introduced in meson v50.0. Simply updating the project requirement to ensure that version is required to build. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ie837fb87bcbf56227945cbead781ec6be89fef0b
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