commit | 7f516a02b02d44e799a29e2d2d8f579dce31fb1f | [log] [tgz] |
---|---|---|
author | Andrew Jeffery <andrew@codeconstruct.com.au> | Thu Jun 27 19:42:19 2024 +0930 |
committer | Andrew Jeffery <andrew@codeconstruct.com.au> | Thu Jun 27 20:36:05 2024 +0930 |
tree | a540ab888467e1eed0adad9c7b10bfdb652fc8c3 | |
parent | 62dd15e88a15ff0bfed635b3cd68a27ff19c7002 [diff] |
meson: Request pdbg via dependency() pdbg provides a pkgconfig file, use the usual approach for discovering the dependency. Change-Id: I20993c3c79cddd882c5d4747b7c2d5e2114ba9a3 Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
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