diff options
| author | Gyorgy Sarvari <skandigraun@gmail.com> | 2025-02-25 14:33:35 +0100 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2025-02-25 09:46:52 -0800 |
| commit | e3c5b2dd0c5758da6396514c6c6ec413056b6fe0 (patch) | |
| tree | e097b47aad3235d421e13fc69632ec6232a0d029 /meta-python/recipes-devtools/python/python3-django.inc | |
| parent | 996dfcbdd7bfd2933e053780f1761c06b4043e7f (diff) | |
| download | meta-openembedded-e3c5b2dd0c5758da6396514c6c6ec413056b6fe0.tar.gz | |
capnproto: only export binaries for native build
The base problem this is trying to solve: capnproto has two main
components: libraries that can be linked against, and binary files
that can generate c++ code from capnproto definitions. When cross-compiling
one needs to use the cross-compiled libraries, but with the native
definition-compilers.
When linking against capnproto from another recipe, cross-compilation
fails, because the cmake files generated by capnproto verify the
existence of binary files in $bindir. When using a cross-compiled
version of capnproto, these binary files do not exist in RECIPE_SYSROOT, so
the compilation fails.
The previous patch: the previous solution patched the CMakeLists.txt
file in a way that it didn't export nor install the generated binary files.
Accidentally this also happened with native build (and happened knowingly with
target builds).
The new patch: instead of not installing and not exporting the binaries,
just install them without exporting, when creating a target build.
During compilation check is CMAKE_CROSSCOMPILING is set (coming from
cmake.bbclass) - if it is set, only install the binaries, without
exporting. When it is not set, resort to the original behavior.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-django.inc')
0 files changed, 0 insertions, 0 deletions
