1. 01 Oct, 2013 1 commit
  2. 18 Sep, 2013 1 commit
  3. 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
  4. 11 Sep, 2013 2 commits
  5. 09 Sep, 2013 1 commit
  6. 04 Sep, 2013 1 commit
  7. 03 Sep, 2013 2 commits
    • Christian Kandeler's avatar
      QbsProjectManager: Fix potential crashes when resolving a project. · 5b21ee59
      Christian Kandeler authored
      
      
      First case: Re-parsing is requested while a project is being resolved.
      The respective function can be entered more than once due to signal
      callbacks, resulting in double deletion of the job object.
      Second case: Closing Creator while a project is being resolved lets the
      resolve job run unattended, resulting in a crash on exit.
      
      Change-Id: I99e034a211ebe730dd02096ce76d601fbc848f5c
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@digia.com>
      5b21ee59
    • Christian Kandeler's avatar
      QbsProjectManager: Add support for remote targets. · f27b738f
      Christian Kandeler authored
      
      
      After parsing, we tell the target about deployable files
      and executables, so it can make use of that information
      for deployment and remote execution, respectively.
      In addition, the current default deploy configuration (consisting of
      just an install step) is now set up only for the desktop device,
      since other targets will likely provide specialized deployment
      solutions.
      The most noticeable effect of this patch is that the RemoteLinux
      target and its descendants now work out of the box with qbs projects.
      
      Change-Id: I512d4e215f2fa540efd4de5f5c1e53abaa0596d1
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@digia.com>
      f27b738f
  8. 02 Sep, 2013 1 commit
  9. 30 Aug, 2013 2 commits
  10. 28 Aug, 2013 1 commit
  11. 21 Aug, 2013 1 commit
  12. 20 Aug, 2013 1 commit
  13. 19 Aug, 2013 1 commit
  14. 09 Aug, 2013 1 commit
  15. 02 Aug, 2013 1 commit
  16. 22 Jul, 2013 1 commit
  17. 09 Jul, 2013 2 commits
  18. 24 Jun, 2013 1 commit
  19. 21 Jun, 2013 3 commits
  20. 18 Jun, 2013 2 commits
  21. 17 Jun, 2013 1 commit
  22. 12 Jun, 2013 1 commit
  23. 10 Jun, 2013 1 commit
  24. 06 Jun, 2013 4 commits
  25. 30 May, 2013 1 commit
  26. 28 May, 2013 1 commit
  27. 23 May, 2013 1 commit
  28. 17 May, 2013 2 commits
  29. 15 May, 2013 1 commit