Skip to content
GitLab
Select Git revision
  1. 03 May, 2016 - 1 commit
  3. 19 Apr, 2016 - 1 commit
    • James McDonnell's avatar
      Add the ability to change precompiled header use · cc1a28d0
      James McDonnell authored 
      
Give the Windows configureapp the same -pch/-no-pch arguments found in
the Linux configure script.  Using command line arguments to
enable/disable precompiled header use is preferable to mkspec changes.

Make -pch the default for all toolchains.  In particular, this makes
-pch the default for QNX on Windows.  Previously, QNX on Windows had
an implied default of -no-pch.  Precompiled headers are the default
for QNX on Linux; they should also be the default for QNX on Windows.
A 'dictionary["PCH"] = "no"' will need to be added in
Configure::applySpecSpecifics for any toolchain that should default to
-no-pch (none known at this time).

-no-pch is implemented by putting a "CONFIG -= precompile_header"
in qmodule.pri.  This ensures that Qt is built without precompiled
headers (as requested) even if allowing precompiled header use is the
default for the toolchain.

Task-number: QTBUG-52578
Task-number: QTBUG-11545
Change-Id: I1b59bc2d416c5ba169161c5b3cc13accd76eeac8
Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
      cc1a28d0
  5. 22 Mar, 2016 - 1 commit
    • Andreas Holzammer's avatar
      qmake: Fix wince dll deployment in Visual Studio · f8d790f0
      Andreas Holzammer authored 
      
This fix repairs the mechanism to deploy Qt dlls as well as C++ runtime
to a wince target in Visual Studio.

Do this by adding a deploy section in the Visual Studio solution and
adding the C++ runtime from the mkspec to the files deployed to the target.
Deploy target path is set to what the wizard of Visual Studio defaults to.
Before, the c++ runtime was only deployed for executables which were built
as part of Qt.

Task-number: QTBUG-50924
Change-Id: I478010dc16e35c68578281895aa3ae14b5c96bb4
Reviewed-by: default avatarMaurice Kalinowski <maurice.kalinowski@theqtcompany.com>
      f8d790f0
  7. 21 Mar, 2016 - 2 commits
  9. 10 Mar, 2016 - 1 commit
  11. 07 Mar, 2016 - 1 commit
  13. 28 Jan, 2016 - 1 commit
  15. 10 Dec, 2015 - 3 commits
  17. 08 Dec, 2015 - 1 commit
  19. 04 Dec, 2015 - 1 commit
  21. 02 Dec, 2015 - 1 commit
  23. 17 Nov, 2015 - 1 commit
  25. 03 Nov, 2015 - 1 commit
  27. 26 Oct, 2015 - 1 commit
  29. 23 Oct, 2015 - 1 commit
  31. 20 Oct, 2015 - 1 commit
  33. 18 Oct, 2015 - 1 commit
  35. 14 Oct, 2015 - 1 commit
  37. 02 Oct, 2015 - 1 commit
  39. 01 Oct, 2015 - 3 commits
  41. 22 Sep, 2015 - 1 commit
    • Thiago Macieira's avatar
      Auto-detect whether 64-bit std::atomic really works · 3d7586b7
      Thiago Macieira authored 
      The C++ standard says it must, but some badly-configured toolchains seem
to be lacking support.

In particular, for some 32-bit platforms without native support for
them, GCC implements 64-bit atomics via out-of-line functions in
libatomic. If that library is missing... well, then std::atomic 64-bit
doesn't work and we mustn't try to use it.

This was found when trying to compile Qt 5.6 for MIPS 32-bit:

Linking library libQt5Core.so.5.6.0
.obj/qsimd.o: In function `std::__atomic_base<unsigned long long>::load(std::memory_order) const':
/opt/poky/1.7/sysroots/mips32r2-poky-linux/usr/include/c++/4.9.1/bits/atomic_base.h:500: undefined reference to `__atomic_load_8'
.obj/qsimd.o: In function `std::__atomic_base<unsigned long long>::store(unsigned long long, std::memory_order)':
/opt/poky/1.7/sysroots/mips32r2-poky-linux/usr/include/c++/4.9.1/bits/atomic_base.h:478: undefined reference to `__atomic_store_8'

Yocto bug report: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8274



Change-Id: I42e7ef1a481840699a8dffff140224d6614e5c36
Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
Reviewed-by: default avatarLars Knoll <lars.knoll@theqtcompany.com>
Reviewed-by: default avatarThiago Macieira <thiago.macieira@intel.com>
      3d7586b7
  43. 14 Sep, 2015 - 1 commit
  45. 05 Sep, 2015 - 1 commit
    • Thiago Macieira's avatar
      Add detection of C++14 and C++1z compiler features · 4684c1af
      Thiago Macieira authored 
      
[ChangeLog][General Improvements] Qt's buildsystem now detects whether
the compiler supports C++14 and experimental support for C++1z. If the
compiler supports it, then Qt is automatically compiled using that
support.
\
This does not apply to user applications built using qmake: those are
still built with C++11 support only. To enable support for C++14 in your
application, add to your .pro file: CONFIG += c++14 (similarly for
C++1z).

Change-Id: Ib056b47dde3341ef9a52ffff13ef1f5d01c42596
Reviewed-by: default avatarLars Knoll <lars.knoll@theqtcompany.com>
      4684c1af
  47. 25 Aug, 2015 - 1 commit
  49. 21 Jul, 2015 - 1 commit
  51. 06 Jul, 2015 - 1 commit
  53. 16 Jun, 2015 - 1 commit
  55. 01 Jun, 2015 - 1 commit
  57. 27 May, 2015 - 4 commits
  59. 20 May, 2015 - 1 commit
  61. 12 May, 2015 - 1 commit
    • Oswald Buddenhagen's avatar
      remove $INCLUDE/$LIB hack for mingw · 03ae6ad8
      Oswald Buddenhagen authored 
      
mingw is not msvc, and nobody in their right mind would expect it to
behave like it.

[ChangeLog][Important Behavior Changes][qmake] Qt configure and qmake
used with a MinGW spec will no longer emulate MSVC by picking up the
INCLUDE and LIB environment variables. Use the -I/-L configure options
to pass additional paths, as you would under Unix.

Change-Id: I533bb97de34d14dcbd45e0416283a79f44096c67
Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@theqtcompany.com>
      03ae6ad8
  63. 07 May, 2015 - 1 commit