1. 25 Mar, 2014 1 commit
  2. 24 Jan, 2014 1 commit
  3. 20 Dec, 2013 1 commit
  4. 10 Dec, 2013 1 commit
  5. 09 Oct, 2013 1 commit
  6. 02 Oct, 2013 1 commit
  7. 01 Oct, 2013 1 commit
  8. 07 Jun, 2013 1 commit
  9. 28 May, 2013 1 commit
  10. 11 Apr, 2013 1 commit
  11. 03 Apr, 2013 2 commits
  12. 02 Apr, 2013 2 commits
  13. 29 Nov, 2012 1 commit
  14. 09 Oct, 2012 1 commit
  15. 25 Sep, 2012 1 commit
    • Daniel Molkentin's avatar
      Introduce $$QTC_PREFIX · 745cb4b7
      Daniel Molkentin authored
      'make install' now installs to $(INSTALL_ROOT)$$QTC_PREFIX/...
      This is used for giving the contents of the 7zips an additional prefix.
      (previously done by doing an additional copying step in bindistHelper).
      QTC_PREFIX can also be used to give Qt Creator a different install path
      at qmake time, and defaults to /usr/local on Linux.
      On Windows and Mac there is no default for QTC_PREFIX.
      Usage: qmake -r QTC_PREFIX=/qtcreator-2.6.0 && make &&
      INSTALL_ROOT=/tmp/creator-dist make install
      Change-Id: Id30781e14bfdde52531800f22b22e39f0459e806
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@digia.com>
  16. 11 Sep, 2012 1 commit
  17. 07 Sep, 2012 1 commit
  18. 05 Sep, 2012 1 commit
    • Daniel Molkentin's avatar
      Introduce $$QTC_PREFIX instead of abusing $(INSTALL_ROOT). · c29bf6f6
      Daniel Molkentin authored
      Reason: $INSTALL_ROOT is only meant to be used by packagers
      to temporarily put the contents into a different location,
      which is needed for fakeroot packaging.
      QTC_PREFIX is not a qmake variable, and defaults to
      /usr/local. On Windows the default prefix is "QtCreator",
      since "make install" is expected to be used in
      a packaging context only where either INSTALL_ROOT
      should be used or QTC_PREFIX should be set to the
      absolute destination path where e.g. an installer
      generator will pick it up.
      Change-Id: Ifa4950340e58e34726c53f5417adcc7b50828ce1
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@nokia.com>
  19. 21 Aug, 2012 1 commit
  20. 02 Mar, 2012 1 commit
  21. 22 Feb, 2012 1 commit
  22. 04 Jan, 2012 1 commit
  23. 09 Nov, 2011 1 commit
  24. 06 Oct, 2011 1 commit
  25. 05 Oct, 2011 1 commit
  26. 15 Mar, 2011 1 commit
  27. 18 Feb, 2011 1 commit
  28. 03 Nov, 2010 2 commits
  29. 01 Nov, 2010 2 commits
    • con's avatar
      Mac: Use rpath instead of executable_path. · 49b86e77
      con authored
      Because executable_path and loader_path are just too inflexible for some
      stuff. The rpath is supposed to be set to the Qt Creator app's Contents
      Compiling on 10.4 now requires to enter compatibility mode via
      QTC_TIGER_COMPAT env variable or TIGER_COMPAT_MODE qmake variable.
    • con's avatar
      Make tests compile on Mac. Use qtLibraryName instead of qtLibraryTarget. · 59c301a8
      con authored
      qtLibraryTarget is only defined if used with TEMPLATE=lib, which makes
      it fail in pri files that are used for app pro files. The tests still
      don't run because of run time linking issues.
  30. 13 Oct, 2010 1 commit
    • Denis Mingulov's avatar
      Add precompiled headers to Qt Creator sources, to any library and plugin · 69229287
      Denis Mingulov authored
      Precompiled headers are a performance feature supported by some
      compilers to reduce the (re-)compilation time substantially.
      Usage in Qt: http://doc.qt.nokia.com/4.7/qmake-precompiledheaders.html
      Due to the usage of precompiled headers Qt without demos/examples/webkit
      etc might be compiled even faster than Qt Creator on some systems.
      Despite of Qt, Qt Creator consist of mostly quite small subprojects
      (plugins and libraries) where the effect would not be so noticeable
      but still will be visible.
      This patch adds default precompiled headers to any plugin and library
      (i.e. by changes in src/qtcreatorplugin.pri and src/qtcreatorlibrary.pri
      respectively). Almost the same headers are included to general
      precompiled header (src/shared/qtcreator_pch.h) like used in QtCore,
      just QPointer/QScopedPointer etc and QDebug are added, it is used almost
      in any subproject. Also for plugins some QtGui related headers are added
      Default precompiled headers are enabled so:
      isEmpty(PRECOMPILED_HEADER):PRECOMPILED_HEADER = $$PWD/shared/header.h
      So it is possible to override this variable in any place in the project
      file in case if it will be needed.
      Such overriding is used for Botan (src/libs/3rdparty/botan) - it is
      not a Qt project, just a pure C++. Most usable headers were used to
      create special precompiled header for Botan. It is 3rd party component
      so also src/libs/3rdparty/precompiled_headers folder was created -
      to use for any future 3rd party components' precompiled headers.
      To enable a usage of precompiled headers feature in Qt projects
      'precompile_header' has to be added to CONFIG. It is done by default
      for limited platforms only (e.g. not for Linux now), so to enable it on
      any other platform - e.g. special qmake command has to be used:
      qmake "CONFIG *= precompile_header" -r ../../qt-creator/
      To disable a usage of precompiled headers (on platforms where it is
      pre-enabled - otherwise it will be used automatically):
      qmake "CONFIG -= precompile_header" -r ../../qt-creator/
      To see on which platforms precompiled headers feature is enabled
      by default - qt/mkspecs folder has to be checked.
      Precompiled headers require an additional space on the disk, it looks
      like for Qt Creator full size of the shadow build folder grows up to
      2 times (e.g. 1.5 GB to 3 GB).
      Test results:
      Linux x64, gcc 4.4, T7500, 3 GB RAM: About 22.5 minutes are reduced
      to about 14 minutes (almost 80% faster).
      Windows x86, vs2008, P8400, 2 GB RAM: About 70 minutes are reduced
      to about 20 minutes (amazing 250% faster).
      Merge-request: 2182
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@nokia.com>
  31. 08 Sep, 2010 1 commit
  32. 25 Sep, 2009 1 commit
  33. 15 Sep, 2009 1 commit
  34. 03 Jun, 2009 1 commit
  35. 08 May, 2009 1 commit
  36. 06 May, 2009 1 commit
    • Oswald Buddenhagen's avatar
      beautify installation of pluginspecs · c1dc4394
      Oswald Buddenhagen authored
      use the data copying custom compiler approach here, too.
      this leaves more work to qmake, which is good.
      on the upside, pluginspecs will be installed when they change without
      having force a re-link of the plugin itself.
      on the downside, installation of a pluginspec will force a re-link of
      the plugin. oh, well - you can't have it all (with qmake) ...