1. 04 Mar, 2015 1 commit
  2. 15 Sep, 2014 1 commit
  3. 02 Sep, 2014 2 commits
  4. 26 Aug, 2014 1 commit
  5. 08 May, 2014 1 commit
  6. 26 Mar, 2014 1 commit
  7. 25 Mar, 2014 1 commit
  8. 24 Jan, 2014 1 commit
  9. 20 Dec, 2013 1 commit
  10. 10 Dec, 2013 1 commit
  11. 09 Oct, 2013 1 commit
  12. 02 Oct, 2013 1 commit
  13. 01 Oct, 2013 1 commit
  14. 07 Jun, 2013 1 commit
  15. 28 May, 2013 1 commit
  16. 11 Apr, 2013 1 commit
  17. 03 Apr, 2013 2 commits
  18. 02 Apr, 2013 2 commits
  19. 29 Nov, 2012 1 commit
  20. 09 Oct, 2012 1 commit
  21. 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>
      745cb4b7
  22. 11 Sep, 2012 1 commit
  23. 07 Sep, 2012 1 commit
  24. 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>
      c29bf6f6
  25. 21 Aug, 2012 1 commit
  26. 02 Mar, 2012 1 commit
  27. 22 Feb, 2012 1 commit
  28. 04 Jan, 2012 1 commit
  29. 09 Nov, 2011 1 commit
  30. 06 Oct, 2011 1 commit
  31. 05 Oct, 2011 1 commit
  32. 15 Mar, 2011 1 commit
  33. 18 Feb, 2011 1 commit
  34. 03 Nov, 2010 2 commits
  35. 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
      folder.
      Compiling on 10.4 now requires to enter compatibility mode via
      QTC_TIGER_COMPAT env variable or TIGER_COMPAT_MODE qmake variable.
      49b86e77
    • 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.
      59c301a8