commit | b797b3e1852f5fb59d65b9ebe787aabbbd2b8462 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Jun 29 10:12:05 2020 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Mon Jun 29 10:12:05 2020 -0500 |
tree | 4ce6eed17d6e5482467c49c733fef58eebc73cfb | |
parent | 13683089432cbfb152ff9fdffb978cb1fdbe7a54 [diff] |
Normalize includes relative to source root For unit test cases it is cleaner to have include file paths relative to source root (e.g. #include attn/attn_handler.hpp). Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Id718e57e9ba8da4c2ff3bb11b1c7a61537da538a
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