1. 19 Sep, 2017 1 commit
  2. 18 Sep, 2017 3 commits
  3. 15 Sep, 2017 3 commits
  4. 14 Sep, 2017 1 commit
  5. 13 Sep, 2017 1 commit
    • hjk's avatar
      ProjectExplorer: Re-organize RunConfiguration constructors · 890c1906
      hjk authored
      The idea is to massage the setup in a way to make implementation
      of new configurations less error prone by identifying recurring patterns
      and sharing repetitive code that tends to be forgotten (see Android cloning).
      
      The former two lines of constructors (owner-and-id, owner-and-source)
      are split into a simple, shared, constructor and new setId() and
      copyFrom() functions.
      
      The change is mostly mechanical, some multiple calls to fromMap
      have been removed, though, some consts added.
      
      Otherwise, to keep the patch small it temporarily introduces two
      helper templates in IRunConfigurationFactory. Also, setId() signatures
      have not been unified yet. These won't be needed in the final setup.
      
      Change-Id: I8c0734496caae744a9883fe6d92c1d8f8e0234ea
      Reviewed-by: default avatarhjk <hjk@qt.io>
      890c1906
  6. 12 Sep, 2017 1 commit
  7. 08 Sep, 2017 5 commits
  8. 06 Sep, 2017 1 commit
  9. 05 Sep, 2017 2 commits
  10. 24 Aug, 2017 1 commit
  11. 04 Aug, 2017 1 commit
  12. 02 Aug, 2017 2 commits
  13. 01 Aug, 2017 1 commit
    • Tobias Hunger's avatar
      ProjectNodes: Do not derive Project Nodes from QObject · 45046f70
      Tobias Hunger authored
      That should save some memory per node, and since creator has a lot of nodes
      (e.g. opening the LLVM project adds about 1 000 000 nodes) this should be
      noticeable:-)
      
      Calling update inside ProjectTree::currentNode() and rename it to
      findCurrentNode() to make sure it is an still existing pointer.
      Also, try to reduce the somehow more expensive currentNode() calls
      and sprinkle some const around that usage.
      
      Change-Id: I6a7c5db01a71d53d39544d3013cad557d5b96cdc
      Reviewed-by: Tobias Hunger's avatarTobias Hunger <tobias.hunger@qt.io>
      45046f70
  14. 31 Jul, 2017 1 commit
  15. 28 Jul, 2017 3 commits
  16. 27 Jul, 2017 1 commit
  17. 26 Jul, 2017 2 commits
  18. 25 Jul, 2017 4 commits
  19. 21 Jul, 2017 1 commit
  20. 20 Jul, 2017 1 commit
  21. 19 Jul, 2017 4 commits
    • Claus Steuer's avatar
      CMake: Fix "CMake configuration changed on disk" dialog · d105ac82
      Claus Steuer authored
      The dialog is shown when the cmake configuration changes.
      The user can either apply the changes or reject them. To determine the
      decision of the user the return value of the dialog is evaluated.
      This is wrong because the dialog uses custom buttons (see documentation
      of QMessageBox::exec). As a consequence the configuration is never
      applied.
      
      Use QMessageBox::clickedButton to determine the user decision.
      Additionally change the role of the apply button from AcceptRole to
      ApplyRole as this better matches its intention.
      
      Change-Id: I1d2d1fb7186dcc8d789c192c51bb34111eb84ee5
      Task-number: QTCREATORBUG-18292
      Reviewed-by: Tobias Hunger's avatarTobias Hunger <tobias.hunger@qt.io>
      d105ac82
    • Claus Steuer's avatar
      CMake: Do not check for changes if config was changed by the user · 9916c0a7
      Claus Steuer authored
      When the cmake configuration changes, BuildDirManager checks whether
      the new configuration differs from the current configuration.
      In case of differences a dialog is opened and the user must decide if
      the changes shall be applied or rejected.
      When the user changes the cmake configuration in the projects page the
      dialog will open as well. This is unencessary since the user already
      decided to apply the changes.
      
      Let BuildDirManager not check for changes if the configuration was
      changed by the user via the projects page.
      
      Change-Id: I736ee7f4dee99fe707f2931c73b287231b1daa1d
      Reviewed-by: Tobias Hunger's avatarTobias Hunger <tobias.hunger@qt.io>
      9916c0a7
    • Claus Steuer's avatar
      CMake: Fix cmake config can't be changed by user in tealeaf mode · bf103789
      Claus Steuer authored
      Changes to the cmake configuration (via projects page) are not applied
      in tealeaf mode.
      The tealeafreader::parse method passes changed config parameters to
      cmake only if the .cpb file does not exist. Since that file always
      exists after project initialization the user can't change the cmake
      config anymore.
      
      Make tealeaf reader pass changed config parameters to cmake when
      a reparse is forced. This restores the behavior from 4.2.2
      
      Change-Id: I31ffad32d176e6290064b55758e4df96d2ffe6bc
      Reviewed-by: Tobias Hunger's avatarTobias Hunger <tobias.hunger@qt.io>
      bf103789
    • Claus Steuer's avatar
      CMake: Set project file location in tealeaf mode · 13bcdf70
      Claus Steuer authored
      The tealeafreader creates a RawProjectPart for each cmake build target.
      However, the location of the CMakeLists.txt is not set/added to
      RawProjectPart::projectFile and RawProjectPart::buildSystemTarget.
      Both properties are required by the AutoTest plugin to map
      run configurations to test configurations.
      
      Make tealeafreader use the same code as the servermodereader
      to determine the location of the CMakeLists.txt.
      
      Change-Id: Ia35444799bcd3c46f84ad897044cae56c1aa16ac
      Reviewed-by: Tobias Hunger's avatarTobias Hunger <tobias.hunger@qt.io>
      13bcdf70