1. 11 Mar, 2014 1 commit
  2. 27 Feb, 2014 1 commit
  3. 25 Feb, 2014 1 commit
  4. 19 Feb, 2014 2 commits
  5. 12 Feb, 2014 1 commit
    • Orgad Shaneh's avatar
      Clean up single namespace forward-declarations · 7ed15760
      Orgad Shaneh authored
      Done using the following ruby script:
      
      Dir.glob('**/*.h').each { |file|
        if File.file?(file)
          s = File.read(file)
          t = s.gsub(/^namespace .+ \{\n\s*class .*;\n\s*\}.*$/) { |m| m.gsub(/\n\s*/, ' ').gsub(/\s*\/\/.*$/, '') }
          if t != s
            puts file
            File.open(file, 'w').write(t)
          end
        end
      }
      
      Change-Id: Iffcb966e90eb8e1a625eccd5dd0b94f000ae368e
      Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
      7ed15760
  6. 11 Feb, 2014 1 commit
  7. 07 Feb, 2014 1 commit
  8. 14 Jan, 2014 1 commit
  9. 10 Jan, 2014 2 commits
  10. 08 Jan, 2014 4 commits
  11. 12 Dec, 2013 2 commits
  12. 10 Dec, 2013 1 commit
  13. 15 Nov, 2013 1 commit
  14. 31 Oct, 2013 1 commit
  15. 23 Oct, 2013 3 commits
  16. 14 Oct, 2013 1 commit
  17. 09 Oct, 2013 2 commits
  18. 01 Oct, 2013 2 commits
    • Daniel Teske's avatar
      ProjectPart: Add meta information · e462c962
      Daniel Teske authored
      Add displayname and project file path and a pointer back to the
      project.
      
      Change-Id: Ic9a18f52a6291493bd3a95fd3456ed0e1a3c63e3
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      e462c962
    • Tobias Hunger's avatar
      BuildConfigurationFactory: Introduce priorities · ac6a3fd5
      Tobias Hunger authored
      Introduce priorities for build configuration factories. This way
      plugins can register specialized build configuration factories, that
      e.g. can provide additional build steps.
      
      A negative priority signifies that a factory is not prepared to
      handle a request, the default build configuration factory shipped by
      the build system plugin will report a priority of 0. Add 100 to that
      for each specialization you add (e.g. a remote linux buildconfiguration
      factory would report 100, a specialization of that for mer will
      should report 200, etc.).
      
      Change-Id: I141a7a5a79166afdb7657d46eb7e86bd18d3abf6
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
      Reviewed-by: default avatarMichal Klocek <michal.klocek@digia.com>
      ac6a3fd5
  19. 27 Sep, 2013 1 commit
    • 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>
      921f86df
  20. 24 Sep, 2013 1 commit
  21. 22 Sep, 2013 1 commit
  22. 20 Sep, 2013 1 commit
  23. 17 Sep, 2013 1 commit
    • 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>
      d2adc303
  24. 13 Sep, 2013 1 commit
  25. 11 Sep, 2013 1 commit
  26. 09 Sep, 2013 1 commit
  27. 03 Sep, 2013 1 commit
  28. 28 Aug, 2013 1 commit
  29. 21 Aug, 2013 1 commit
  30. 19 Aug, 2013 1 commit