1. 11 Jan, 2016 4 commits
  2. 08 Jan, 2016 4 commits
  3. 07 Jan, 2016 2 commits
  4. 16 Sep, 2015 1 commit
    • Daniel Teske's avatar
      CMake: Rewrite logic for kit selection · 014a7b33
      Daniel Teske authored
      Some time ago the all the wizards for the Plain C++ were coalesced into one wizard.
      
      Since then the wizard asks first for the targets via a targetsetuppage and then
      in the CMakeOpenProjectWizard asked for the kit again.
      
      This patch clean thats up, by always using the TargetSetupPage for kit
      selection and removing code from the CMakeOpenProjectWizard for kit selection.
      
      It also adds more types of buildconfigurations
      
      Offer: Debug, Release, ReleaseWithDebugInfo, MinSizeRelease with the
      corresponding -DCMAKE_BUILD_TYPE parameters. That argument is saved
      in the build configuration and used once for the first cmake run. (Subsequent
      runs of cmake don't require passing that to cmake again.)
      
      Also do not require running cmake on creating the buildconfiguraiton, instead
      postpone that until the buildconfiguration is made active. With the current
      cmake wizard, selecting multiple kits would show a dialog per buildconfiguration.
      
      Change-Id: I3bb806113f4f529f8e291830647d2515a6c4df8a
      Task-number: QTCREATORBUG-12219
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@theqtcompany.com>
      014a7b33
  5. 31 Aug, 2015 1 commit
    • Daniel Teske's avatar
      Cmake: Read the build.ninja file only once · 13c2c406
      Daniel Teske authored
      The first getCmakeCXXFlags that reads the build.ninja file
      stores the contents in the inout parameter cachedBuildNinja.
      Further calls to getCMakeCXXFlags just use this cached value.
      
      This prevents excessive locking of this file while constructing
      the code model information.
      
      Change-Id: I81e1431194bed6913c69abb2d954068c999a5c1b
      Task-number: QTCREATORBUG-14639
      Reviewed-by: Tom Tanner
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@theqtcompany.com>
      13c2c406
  6. 28 Jul, 2015 1 commit
  7. 10 Mar, 2015 2 commits
  8. 13 Feb, 2015 1 commit
  9. 16 Jan, 2015 1 commit
  10. 07 Nov, 2014 1 commit
  11. 22 Oct, 2014 1 commit
  12. 09 Oct, 2014 1 commit
  13. 12 Sep, 2014 1 commit
  14. 17 Jul, 2014 1 commit
  15. 01 Jul, 2014 1 commit
  16. 08 Jan, 2014 1 commit
  17. 14 Oct, 2013 1 commit
  18. 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
  19. 16 Sep, 2013 1 commit
    • Oleksii Serdiuk's avatar
      CMake: Make CMake plugin work with RemoteLinux plugin. · 328a24ed
      Oleksii Serdiuk authored
      Modified CMake plugin to work correctly with RemoteLinux plugin.
      Because of not being able to extract files to be installed from CMake
      project, only executable targets are automatically added to deployment
      files. All other files have to be specified in CMakeDeployment.txt file
      which should be placed into root of CMake project. The file format is:
      > deployment/prefix
      > relative/source/file1:relative/destination/dir1
      > ...
      > relative/source/filen:relative/destination/dirn
      
      Where:
      - deployment/prefix is (absolute) path prefix to which files will be
        deployed on the remote machine.
      - relative/source/file is file path relative to CMake project root.
        Plain files - no directories or wildcards supported.
      - relative/destination/dir is destination directory path relative to
        deployment/prefix.
      
      Change-Id: I0831636c1b9aac3ff16bb6293104c512d2abfb5a
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
      328a24ed
  20. 01 Aug, 2013 1 commit
  21. 10 Jul, 2013 2 commits
  22. 09 Jul, 2013 1 commit
  23. 19 Mar, 2013 1 commit
  24. 07 Mar, 2013 1 commit
  25. 27 Feb, 2013 1 commit
  26. 29 Jan, 2013 1 commit
  27. 17 Jan, 2013 1 commit
  28. 10 Jan, 2013 1 commit
  29. 16 Nov, 2012 3 commits