summaryrefslogtreecommitdiffstats
path: root/meta-boot2qt-distro/recipes-qt/qt5/qtbase/0002-Disable-ltcg-for-host_build.patch
diff options
context:
space:
mode:
Diffstat (limited to 'meta-boot2qt-distro/recipes-qt/qt5/qtbase/0002-Disable-ltcg-for-host_build.patch')
-rw-r--r--meta-boot2qt-distro/recipes-qt/qt5/qtbase/0002-Disable-ltcg-for-host_build.patch33
1 files changed, 33 insertions, 0 deletions
diff --git a/meta-boot2qt-distro/recipes-qt/qt5/qtbase/0002-Disable-ltcg-for-host_build.patch b/meta-boot2qt-distro/recipes-qt/qt5/qtbase/0002-Disable-ltcg-for-host_build.patch
new file mode 100644
index 0000000..b1a755f
--- /dev/null
+++ b/meta-boot2qt-distro/recipes-qt/qt5/qtbase/0002-Disable-ltcg-for-host_build.patch
@@ -0,0 +1,33 @@
1From 4de366eeb48038da4140c3dcb3e96070e7d56429 Mon Sep 17 00:00:00 2001
2From: Samuli Piippo <samuli.piippo@qt.io>
3Date: Tue, 23 Oct 2018 09:54:57 +0300
4Subject: [PATCH] Disable ltcg for host_build
5
6debug-prefix-map does not work correctly for static libraries
7when using ltcg, and since host_build compilations link agaist
8the libQt5Bootstrap.a library, it breaks source file packaging
9into debug packages.
10
11Also disable ltcg when compiling on Windows host platform,
12as GCC7 does not support lto with mingw.
13
14Disable also for static builds since those libraries can be linked
15on Windows host, where the lto built binaries won't work.
16
17Task-number: QTBUG-71230
18Change-Id: I5bea76ea03bf1943b0cfaf03d46a4840bd99a28b
19Upstream-Status: Inappropriate [embedded specific]
20---
21 mkspecs/features/ltcg.prf | 2 +-
22 1 file changed, 1 insertion(+), 1 deletion(-)
23
24diff --git a/mkspecs/features/ltcg.prf b/mkspecs/features/ltcg.prf
25index 482e5b5..de00842 100644
26--- a/mkspecs/features/ltcg.prf
27+++ b/mkspecs/features/ltcg.prf
28@@ -1,4 +1,4 @@
29-CONFIG(release, debug|release):!host_build {
30+CONFIG(release, debug|release):!host_build:!equals(QMAKE_HOST.os, Windows):!staticlib {
31 # We need fat object files when creating static libraries on some platforms
32 # so the linker will know to load a particular object from the library
33 # in the first place. On others, we have special ar and nm to create the symbol