1. 03 Nov, 2011 3 commits
  2. 13 Oct, 2011 1 commit
  3. 06 Oct, 2011 1 commit
  4. 05 Oct, 2011 1 commit
  5. 04 Oct, 2011 1 commit
  6. 29 Sep, 2011 1 commit
  7. 27 Sep, 2011 1 commit
  8. 26 Sep, 2011 1 commit
  9. 21 Sep, 2011 3 commits
  10. 12 Sep, 2011 2 commits
  11. 01 Sep, 2011 1 commit
  12. 26 Aug, 2011 1 commit
  13. 25 Aug, 2011 1 commit
  14. 22 Aug, 2011 1 commit
  15. 16 Aug, 2011 1 commit
  16. 02 Aug, 2011 1 commit
  17. 20 Jul, 2011 1 commit
  18. 12 Jul, 2011 1 commit
  19. 08 Jul, 2011 1 commit
  20. 06 Jul, 2011 1 commit
  21. 24 Jun, 2011 2 commits
  22. 23 Jun, 2011 1 commit
  23. 22 Jun, 2011 2 commits
  24. 08 Jun, 2011 1 commit
  25. 23 May, 2011 1 commit
  26. 12 May, 2011 1 commit
    • Thorbjørn Lindeijer's avatar
      Disable observer and jsdebugger services when they're already part of Qt · 2b0266d0
      Thorbjørn Lindeijer authored
      As of Qt 4.8 the observer and jsdebugger services are part of Qt. This
      means the following changes are necessary in Qt Creator:
      
      * Do not link to the QmlJSDebugger library.
      * Do not create JSDebuggerAgent and QDeclarativeViewObserver instances
        in the QmlApplicationViewer and use the new declarative_debug CONFIG
        option to enable those services in Qt. This is done automatically
        for debug builds.
      * Point out the QML Debugging Library and the QML Observer are "Not
        needed" in the Qt options page.
      * Change the label in qmake options from "Link QML debugging library" to
        "Enable QML debugging". It still remains as a way to enable this
        functionality in release builds or for QtQuick applications not based
        on Qt Creator's template.
      * Rely on qmlviewer for debugging QML UI projects rather than the
        observer, which is no longer necessary.
      
      Reviewed-by: Kai Koehne
      2b0266d0
  27. 02 May, 2011 1 commit
  28. 29 Apr, 2011 1 commit
  29. 17 Apr, 2011 1 commit
  30. 16 Apr, 2011 1 commit
  31. 13 Apr, 2011 2 commits
  32. 11 Apr, 2011 1 commit
    • Alessandro Portale's avatar
      Another fix for shadow build deployment with sh.exe in path · f1033737
      Alessandro Portale authored
      The "isEmpty(QMAKE_SH)" test is nonsense in the case of an msvc
      build, because for msvc, sh.exe is never executed (although QMAKE_SH
      is set.
      
      "isEqual(QMAKE_DIR_SEP, \\)" is now the ultimate test. QMAKE_DIR_SEP
      will only be "/" if sh.exe is in the path AND win32-g++ is used.
      
      Task-Number: QTCREATORBUG-4455
      f1033737