1. 08 Jun, 2011 1 commit
  2. 13 Apr, 2011 1 commit
  3. 03 Mar, 2011 1 commit
  4. 21 Feb, 2011 1 commit
    • Tobias Hunger's avatar
      ToolChain: Refactor toolchain support · 8d0c4772
      Tobias Hunger authored
      Refactor ToolChains in Qt Creator:
       * Allow for several toolchains of the same type
       * Be smarter wrt. guessing what kind of output a toolchain
         produces. This allows us to eventually handle e.g. embedded
         linux setups way better than before.
       * Be smarter wrt. guessing what kind of environment a Qt version
       * Improve auto-detection of toolchains a bit
       * Decide on which debugger to use based on the kind of output
         produced by the compiler.
       * Add options page to configure toolchains
       * Remove toolchain related options from the Qt version dialog
      Reviewed-by: dt
  5. 19 Jan, 2011 1 commit
    • dt's avatar
      ProjectExplore: Introduce dis/enabling of buildconfigurations · e505604b
      dt authored
      The build actions are disabled if the buildconfiguration is disabled.
      The deploy and run actions are disabled if deploying or running invokes
      building automatically.
      Qt4BuildConfigurations are disabled while parsing.
      Task-Nr: QTCREATORBUG-2576
  6. 17 Jan, 2011 1 commit
    • dt's avatar
      Qt4projectManager: Refactor Qt4Target, split up in per target classes · 67cfb7e0
      dt authored
      Almost(*) all of the symbian and maemo specific code is now theoretically
      moveable to a separate plugin. Thus making it possible to implement
      new targets in a plugin.
      (*) Noteable missing is the qtversion, which needs to be split up
      per target too.
      Also fixes
      Task-Nr: QTCREATORBUG-2440
      Reviewed-By: hunger
      Reviewed-By: ck
  7. 13 Jan, 2011 1 commit
  8. 12 Jan, 2011 2 commits
  9. 17 Dec, 2010 1 commit
  10. 07 Dec, 2010 1 commit
  11. 17 Nov, 2010 1 commit
    • Oswald Buddenhagen's avatar
      overhaul process argument handling · 1e362b0f
      Oswald Buddenhagen authored
      get away from argument stringlists. instead, use native shell command
      lines which support quoting/splitting, environment variable expansion
      and redirections with well-understood semantics.
      Task-number: QTCREATORBUG-542
      Task-number: QTCREATORBUG-1564
  12. 01 Nov, 2010 1 commit
  13. 11 Oct, 2010 1 commit
  14. 05 Oct, 2010 1 commit
  15. 23 Sep, 2010 1 commit
  16. 01 Sep, 2010 1 commit
  17. 30 Aug, 2010 1 commit
  18. 07 Jul, 2010 1 commit
  19. 07 Jun, 2010 1 commit
  20. 21 May, 2010 1 commit
  21. 17 Mar, 2010 1 commit
  22. 12 Mar, 2010 1 commit
    • Thorbjørn Lindeijer's avatar
      Move build environment customization down to BuildConfiguration · 2a93b540
      Thorbjørn Lindeijer authored
      The functionality was duplicated between the Qt4 and CMake build
      configurations and their configuration widgets. This change moves it
      down to BuildConfiguration, in addition also making it available for the
      Generic Project.
      Also provides an upgrade path for the configuration.
      Task-number: QTCREATOR-24
      Reviewed-by: dt
      Reviewed-by: Tobias Hunger
  23. 10 Mar, 2010 1 commit
    • dt's avatar
      Use exact and aysnc .pro file evaluate · ab8fc52d
      dt authored
      This is a big change touching almost all of our .pro file parsing.
      With this patch we only evaluate once exact for all needs and once
      greedy for the filelist. That is the qt runconfigurations don't have own
      evaluaters but reuse the project wide exact evaluation.
      We reevaluate if the user changes the build directory, the qmake
      buildconfiguration or the qmake arguments. That is if you open src.pro
      (or projects.pro) of qt with a shadow build you still don't get all the
      files, but after correcting the build directory, we reevaluate the .pro
      files and find all files. So for a suitable definition of fixed, that
      bug is now fixed.
      We now get the exact defines of all .pro files instead of all defines for all
      buildconfigurations. We still don't distinguish in which
      .pro file a DEFINE is set. So the code model now knows about all the
      defines set for the given configuration but not for which files it is
      actually set. Also that includes all DEFINES set in .qmake.cache or the
      mkspecs. This means all defines from .pro files should now work.
      The intial loading is still synchronous. I haven't looked into it to
      deeply, but it seems possible to make it also async.There are probably a
      few issues which need to be solved fist.
      Also due to the asynchronous nature of the code, the executable is
      updated a few seconds after actually changing the build configuration
  24. 05 Mar, 2010 1 commit
  25. 16 Feb, 2010 1 commit
  26. 09 Feb, 2010 1 commit
    • Tobias Hunger's avatar
      Integrate target support · d1bdfcc3
      Tobias Hunger authored
       * Ease cross device development by introducing 'targets' which
         group build- and runsettings that are valid for this one target
       Most of the kudos for the code review go to dt. Con, thorbjorn,
       ckandler and others did also review parts of this patch.
      Reviewed-by: dt
  27. 01 Feb, 2010 1 commit
  28. 13 Jan, 2010 1 commit
    • dt's avatar
      Add Build to the right click menu of sub projects for Qt4 Projects · fb3ae97d
      dt authored
      They do what you expect them to do, that is build only a subtree.
      The implementation is a little bit strange. We temporarly set the sub
      node to be built on the BuildConfiguration, enqueue that
      BuildConfiguration (which calls BuildStep::init()), and then reset that
      temporary value.
      A more general way would be to have the ability to extend
      BuildConfiguration::buildProject() in a way that additional data can be
      passed to the BuildSteps.
      Task-Nr: QTCREATOR-5
      Task-Nr: QTCREATORBUG-44
  29. 12 Jan, 2010 1 commit
  30. 11 Jan, 2010 2 commits
  31. 07 Jan, 2010 1 commit
    • Tobias Hunger's avatar
      Make method naming more consistent. · a6ad7737
      Tobias Hunger authored
        * Use id() for methods returning a string used to represent
          some type of object.
        * Use displayName() for strings that are meant to be user
        * Quieten some warnings while touching the files anyway.
        * Move Factories to their products in the plugins where that
          was not done before.
      Reviewed-by: dt
  32. 14 Dec, 2009 1 commit
  33. 08 Dec, 2009 1 commit
  34. 07 Dec, 2009 3 commits
  35. 02 Dec, 2009 1 commit
    • con's avatar
      Share the code for determining used qmake arguments. · f3bdeb8c
      con authored
      Move the code that compares the Qt version's debug|release property
      with the build configuration's debug|release property
      to the new build configuration class.
      Reviewed-by: dt
  36. 30 Nov, 2009 1 commit