1. 31 Oct, 2013 2 commits
  2. 15 Oct, 2013 1 commit
  3. 11 Oct, 2013 1 commit
  4. 09 Oct, 2013 1 commit
  5. 01 Oct, 2013 1 commit
  6. 27 Sep, 2013 2 commits
    • Tobias Hunger's avatar
      TargetSetupPage: Generalize the page · 921f86df
      Tobias Hunger authored
      Generalize the target setup page and move it into projectexplorer
      Move the qmake specific code into a projectimporter class with
      a specialization for qmake projects in the qt4projectmanager.
      This change depends heavily on the BuildConfigurationFactory cleanups
      done earlier and completes that change in such a way that generic
      build configuration factories are now in theory possible. The
      remaining problem is how to select the best factory of several that
      claim to be able to handle a kit and that is left for the next patch.
      Change-Id: I47134cb1938c52adebcdc1ddfe8dbf26abbbbeee
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
    • Orgad Shaneh's avatar
      Fix qbs warnings · 666bdaa9
      Orgad Shaneh authored
      Duplicate dependencies
      Change-Id: I23e931cd6e75494a8ec7e099b0f2549764e5924b
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@digia.com>
  7. 20 Sep, 2013 1 commit
  8. 19 Sep, 2013 2 commits
  9. 17 Sep, 2013 2 commits
    • Tobias Hunger's avatar
      BuildConfigurationFactory: Refactor code · d2adc303
      Tobias Hunger authored
      Refactor the code of the build configuration factories. The idea is to
      generalize the code so much that we can allow plugins to install
      custom build configuration factories for the platforms they support.
      To support this use case the following changes where done here:
       * BuildInfo class was introduced to describe one build configuration that
         can be created by a factory.
       * Factories report a list of BuildInfo to describe what they can produce.
         This fixes the need for factories to implicitly create one buildconfiguration
         and then create another one 'officially' to support debug and release build
         configurations to be set up for projects.
       * Do no longer work around factories to create build configurations.
      Change-Id: Ic372e4a9b5c582633b467d130538948472b89d91
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
    • Christian Kandeler's avatar
      Fix qbs build. · 3ae8d6b3
      Christian Kandeler authored
      Commit cf56178d
       introduced an impressive amount of syntax errors.
      Change-Id: Ibaf8b8384b06ee92b658b71f08ac8d14e92c19b0
      Reviewed-by: default avatarThomas Hartmann <Thomas.Hartmann@digia.com>
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@digia.com>
  10. 16 Sep, 2013 1 commit
  11. 12 Sep, 2013 1 commit
  12. 09 Sep, 2013 1 commit
  13. 02 Sep, 2013 1 commit
    • Christian Kandeler's avatar
      Remove superfluous include paths from project files. · 72d17382
      Christian Kandeler authored
      A lot of our build system files specify unneeded include
      paths. These roughly fall into the following categories:
          a) Paths that are already set in more general files
             such as qtcreator.pri.
          b) Paths that serve no purpose at all, possibly
             left over from earlier versions of the project.
          c) Paths that act as workarounds for wrong include
             statements of the form '#include "xyz.h"', where
             xyz.h is not in the same directory as the including
      This patch removes such path specifications and fixes the offending
      include statements from case c).
      Tested on Linux, Windows and OSX with qmake and qbs.
      Change-Id: I039a8449f8a65df0d616b4c08081145c18ae4b15
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@digia.com>
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@digia.com>
  14. 30 Aug, 2013 1 commit
  15. 23 Aug, 2013 1 commit
  16. 21 Aug, 2013 1 commit
  17. 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>
  18. 08 Aug, 2013 1 commit
    • Andre Hartmann's avatar
      Custom Error Parser · 4bc61eca
      Andre Hartmann authored
      Allow setting the following items from outside:
      * capture regular expression,
      * file name, line number and message capture position and
      * whether to parse stdout, stderr or both
      The parser functions can be unit-tested by running (Debug build of Qt
      Creator needed):
      qtcreator -test ProjectExplorer,testCustomOutputParsers
      The data is passed to the custom parser in
      The parser information is stored in toolchains.xml together with the
      custom toolchain. A configuration widget is provided to set up and test
      the regular expression against a sample error message.
      Change-Id: I6191df3c44432943e0aeb16c48d8e79d35845d2e
      Reviewed-by: Orgad Shaneh's avatarOrgad Shaneh <orgads@gmail.com>
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@digia.com>
  19. 02 Jul, 2013 1 commit
    • Christian Kandeler's avatar
      Device support: Make device testing a "well-known" concept. · 5bca241a
      Christian Kandeler authored
      This entails the following:
          - Rename AbstractLinuxDeviceTester to DeviceTester and
            move it up into ProjectExplorer. The class stays
            unchanged, as there was nothing Linux-specific about it.
            The same goes for the associated dialog.
          - Move the createDeviceTester() function from LinuxDevice
            to IDevice and introduce IDevice::hasDeviceTester() to
            enable generic code to make use of this feature.
          - Move device testing out of the list of opaque
            device-specific actions; instead, the device settings widget
            now uses the device tester directly, if applicable.
          - Device testing, just like remote process listing (if not more so),
            is a general concept that implementors of device classes will
            probably want to implement (and they should be encouraged to do so).
            Without the mechanism provided here, they would all need to put
            basically the same code into the actionIds(), displayNameForActionId()
            and executeAction() functions.
      This patch is the natural extension of b90e3bbd
      Change-Id: I94f2badb4ceeda9f5cd3b066c13626bb4f65505d
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
      Reviewed-by: default avatarChristian Kandeler <christian.kandeler@digia.com>
  20. 20 Jun, 2013 1 commit
  21. 06 Jun, 2013 1 commit
  22. 31 May, 2013 1 commit
  23. 30 May, 2013 1 commit
  24. 27 May, 2013 2 commits
  25. 11 Apr, 2013 3 commits
  26. 05 Apr, 2013 1 commit
  27. 12 Feb, 2013 1 commit
  28. 28 Jan, 2013 1 commit
  29. 18 Jan, 2013 1 commit
  30. 16 Jan, 2013 1 commit
  31. 12 Jan, 2013 1 commit
  32. 04 Dec, 2012 1 commit
  33. 25 Oct, 2012 1 commit