| commit | 62dd15e88a15ff0bfed635b3cd68a27ff19c7002 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@codeconstruct.com.au> | Thu Jun 27 19:25:11 2024 +0930 |
| committer | Andrew Jeffery <andrew@codeconstruct.com.au> | Thu Jun 27 20:36:05 2024 +0930 |
| tree | 0ea048e2c000a7475de5b9233a6e48a4d8317ad4 | |
| parent | a001020f1e03110d29ae7c914f622336700d717d [diff] |
subprojects: Add phosphor-logging wrap Addresses the following error: ``` $ meson setup build ... Dependency hei from subproject subprojects/libhei found: YES 0.1 Run-time dependency phosphor-logging found: NO (tried pkgconfig and cmake) Looking for a fallback subproject for the dependency phosphor-logging meson.build:62:23: ERROR: Neither a subproject directory nor a phosphor-logging.wrap file was found. ``` Change-Id: I8b933009a4a282a7c0defcd672986aeeff0bdf2a 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