1. 07 Jan, 2016 1 commit
    • hjk's avatar
      Analyzer: Slim down AnalyzerStartParameters · 8150209f
      hjk authored
      * SysRoot can always be determined from kit.
      * Pass around RunMode as extra parameter
        not as part of AnalyzerStartParameters.
        That's closer to the pattern used elsewhere.
      * Environment was always initialized from the runconfig's
        EnvironmentAspect. The tools can do that directly.
      * Provide setter for display name for cases where
        it is not equal to RunConfiguration::displayName
      Change-Id: I811a0d7cdeb55cc37a16a593b3942abb567a2150
      Reviewed-by: default avatarBogDan Vatra <bogdan@kdab.com>
      Reviewed-by: default avatarUlf Hermann <ulf.hermann@theqtcompany.com>
  2. 19 Nov, 2015 1 commit
  3. 19 Aug, 2015 1 commit
  4. 17 Aug, 2015 1 commit
    • Ulf Hermann's avatar
      Tell the QML debug server exactly what services we expect · 5f90990c
      Ulf Hermann authored
      The services need to be loaded before the first QML engine is created.
      The first QML engine may be created before a client connects. When the
      JavaScript debug service is loaded the engine is put into interpreter
      mode as we don't support debugging in JIT mode. Profiling, however
      should be done in JIT mode, whenever possible.
      Thus, in order to avoid the loading of unnecessary plugins and to get
      better results from the QML profiler we tell the debug server which
      services we expect, even before the client connects. Qt 5.6 will support
      additional command line arguments to specify the services and this
      change uses them.
      Change-Id: I6dcee016c39995e9adada6eaf0e39d8299c9b7e7
      Reviewed-by: default avatarChristian Kandeler <christian.kandeler@theqtcompany.com>
      Reviewed-by: default avatarhjk <hjk@theqtcompany.com>
  5. 30 Jun, 2015 1 commit
  6. 17 Jun, 2015 1 commit
  7. 23 Apr, 2015 1 commit
  8. 30 Jan, 2015 1 commit
  9. 16 Jan, 2015 1 commit
  10. 09 Oct, 2014 1 commit
  11. 10 Apr, 2014 1 commit
  12. 19 Mar, 2014 1 commit
    • Ulf Hermann's avatar
      Android: notify qml profiler when app is stopped · 1111c06a
      Ulf Hermann authored
      As we cannot determine reliably what happened to the app we drop the
      "success" parameter to notifyRemoteFinished(). It was almost always
      true before and where it wasn't it didn't do anything useful. The
      transition from AppRunning to AppKilled without AppDying in between
      was invalid and would have triggered an assertion when it happened.
      Task-number: QTCREATORBUG-11760
      Change-Id: Iebf4ca9bddbcc7b152131f9574bc5f2c0a8ba44f
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
  13. 08 Jan, 2014 1 commit
  14. 05 Nov, 2013 1 commit
  15. 22 Oct, 2013 1 commit
  16. 19 Aug, 2013 1 commit
    • Christian Kandeler's avatar
      Introduce the concept of a "device process". · 22599094
      Christian Kandeler authored
      Provide a QProcess-like abstraction that can be used
      to implement processes running locally or on a remote
      device. Objects of a concrete class implementing the functionality
      are created by IDevice objects.
      Current implementations are:
           - Local execution (QProcess-based), provided via the DesktopDevice.
           - Remote execution via SSH.
           - A specialized case of the former for remote Linux systems (provided by
      The latter is already being used in a number of places. As a result, lots of
      code dealing with details such as setting the remote environment could be
      moved to a central location. These things are no longer the concern of whoever
      is wishing to run a remote process.
      Change-Id: I919260ee6e77a020ca47226a4a534e7b8398106f
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
  17. 05 Aug, 2013 1 commit
  18. 01 Aug, 2013 1 commit
  19. 23 Jul, 2013 3 commits
  20. 19 Jul, 2013 1 commit
  21. 07 May, 2013 2 commits