| commit | b28afc99e4444e16357b45366a99f151cb70b17e | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@inspur.com> | Wed Aug 16 09:47:32 2023 +0800 |
| committer | George Liu <liuxiwei@inspur.com> | Wed Aug 16 09:47:32 2023 +0800 |
| tree | 774a7ac9f3828e089c2ebbc7622435b88b7ef034 | |
| parent | 7c80e52bdce3b96fd59c5a0e5d6de5119d5831a4 [diff] |
meson_options.txt: Support for reading options from meson.options Support has been added for reading options from meson.options instead of meson_options.txt[1]. These are equivalent, but not using the .txt extension for a build file has a few advantages, chief among them many tools and text editors expect a file with the .txt extension to be plain text files, not build scripts. [1] https://mesonbuild.com/Release-notes-for-1-1-0.html#support-for-reading-options-from-mesonoptions Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I3cf46c18541cefee7cc0db7a5bb63d1e27890147
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