| commit | 3dc7bc882e2597db9a0ddeb78fc1c91581192955 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@codeconstruct.com.au> | Thu Jun 27 19:52:38 2024 +0930 |
| committer | Andrew Jeffery <andrew@codeconstruct.com.au> | Thu Jun 27 21:09:10 2024 +0930 |
| tree | 00d7508c95d35d3acfeef79c195b2f56af54fdf3 | |
| parent | 7f516a02b02d44e799a29e2d2d8f579dce31fb1f [diff] |
subprojects: Add valijson wrap
Addresses the following meson warning:
```
Has header "valijson/validator.hpp" : NO
Cloning into 'valijson'...
remote: Enumerating objects: 4827, done.
remote: Counting objects: 100% (1766/1766), done.
remote: Compressing objects: 100% (893/893), done.
remote: Total 4827 (delta 875), reused 1685 (delta 832), pack-reused 3061
Receiving objects: 100% (4827/4827), 4.80 MiB | 3.60 MiB/s, done.
Resolving deltas: 100% (2637/2637), done.
HEAD is now at 9183462118f5 Fix return type on getMinLength
Subproject exists but has no meson.build file.
Subproject valijson is buildable: NO (disabling)
meson.build:87: WARNING: include_directories sandbox violation!
The project is trying to access the directory 'subprojects/valijson/include' which belongs to a different
subproject. This is a problem as it hardcodes the relative paths of these two projects.
This makes it impossible to compile the project in any other directory layout and also
prevents the subproject from changing its own directory layout.
Instead of poking directly at the internals the subproject should be executed and
it should set a variable that the caller can then use. Something like:
some_dep = declare_dependency(include_directories: include_directories('include'))
[provide]
some = some_dep
some_dep = dependency('some')
executable(..., dependencies: [some_dep])
This warning will become a hard error in a future Meson release.
```
Change-Id: I26b4ced45285943b6cae1c1feeace2f853931b0d
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