diff options
author | Khem Raj <raj.khem@gmail.com> | 2019-02-03 16:01:44 -0800 |
---|---|---|
committer | Martin Jansa <Martin.Jansa@gmail.com> | 2019-02-14 17:40:27 +0000 |
commit | cb1b47212659a21514553cb0a0102861a6e2299b (patch) | |
tree | b8438df62790860dee4978bbca3a51359d8ef9d7 /recipes-qt/qt5/qtwebengine/chromium/0019-chromium-fix-build-with-clang.patch | |
parent | 6d919b0bf1ede1d585a6a198257d9e01cf01bd94 (diff) | |
download | meta-qt5-cb1b47212659a21514553cb0a0102861a6e2299b.tar.gz |
qtbase: Export host compiler and linker
Certain portions of qtwebengine build involves building native tools
using host compiler/linker, this however currently uses gcc and when we
build with clang to compile the target pieces, chromium configures for
clang and rightly so, but then does not have a way to define flags for
host and target separately, and it ends up supplying same flags for both
host and target builds, the trouble is that the options between clang
and gcc are not always same in some cases, they dont understand each
others options. So build starts to fail due to these errors about
unknown cmdline options.
This makes sure we inject CC_host, CXX_host, LD_host into qmake.conf so
they can be used in such packages
We use clang to do host builds when TOOLCHAIN = "clang" is used
otherwise default to gcc as it was the case
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'recipes-qt/qt5/qtwebengine/chromium/0019-chromium-fix-build-with-clang.patch')
0 files changed, 0 insertions, 0 deletions