1. 05 Oct, 2010 2 commits
  2. 23 Sep, 2010 2 commits
  3. 22 Sep, 2010 1 commit
  4. 16 Sep, 2010 1 commit
  5. 15 Sep, 2010 1 commit
  6. 13 Sep, 2010 1 commit
    • Tobias Hunger's avatar
      Preserve invalid Qt versions when loading a project · d1c23f58
      Tobias Hunger authored
      Now that we have 2.0 out we can be less strict when checking
      project consistency when loading .user files.  The strictness
      was necessary due to upgrading non-target projects to target
       * Allow for invalid Qt versions when loading a .user file that was not
         updated from the pre-target era.
       * Update the UI to show invalid Qt versions as invalid. Remove
         the Invalid version as soon as a valid one is imported.
      This does preserve the buildsteps, too.
  7. 01 Sep, 2010 1 commit
  8. 30 Aug, 2010 3 commits
  9. 16 Aug, 2010 1 commit
    • Tobias Hunger's avatar
      Fix import of existing builds · 8cd3b549
      Tobias Hunger authored
       * Report what kind of build we have in the tooltip
       * Create only debug/release configuration for debug/release
         configured directories
       * Create debug and release configuraions for debug_and_release
         configured directories
       * Add debug_and_release to options in QMakeStep UI
       * Do not add CONFIG+=debug/release to CONFIG+=debug_and_release builds
  10. 11 Aug, 2010 1 commit
  11. 02 Aug, 2010 1 commit
    • Tobias Hunger's avatar
      Refactor deployment · ee4a04a2
      Tobias Hunger authored
       * Add a DeployConfiguration class to hold settings related
         to deployment.
       * Add BuildStepsList to hold a list of buildsteps
       * Update BuildConfiguration to use BuildStepLists instead of
         manageing lists of buildsteps itself.
       * Update BuildManager to use BuildStepLists in its interfaces
       * Fix fallout introduced by API changes
       * Update .user file to new way of storing settings
      Task-number: QTCREATORBUG-1427
      Task-number: QTCREATORBUG-1428
      Task-number: QTCREATORBUG-1811
      Task-number: QTCREATORBUG-1930
  12. 07 Jul, 2010 1 commit
  13. 06 Jul, 2010 1 commit
  14. 21 May, 2010 1 commit
  15. 19 May, 2010 1 commit
  16. 14 Apr, 2010 1 commit
  17. 08 Apr, 2010 1 commit
  18. 07 Apr, 2010 1 commit
  19. 26 Mar, 2010 1 commit
  20. 25 Mar, 2010 2 commits
  21. 17 Mar, 2010 1 commit
  22. 16 Mar, 2010 2 commits
  23. 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
  24. 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
  25. 05 Mar, 2010 1 commit
  26. 19 Feb, 2010 1 commit
  27. 17 Feb, 2010 4 commits
    • Friedemann Kleint's avatar
      Symbian/Linux: Enable building with makefile-based system. · 7c9c99dc
      Friedemann Kleint authored
      - Autodetect SDK by environment variable EPOCROOT and qt directory
      - Environment::appendOrSet/prependOrSet: Avoid duplicate entries
      - Rename toolchain enumeration value
      - Adapt S60ToolChainMixin to new GnuPoc setup, provide routines for
        all required variables.
      - RVCTToolChain: Make RVCT detection smarter (Check for RVCT<v1><v2>BIN
        variable). Set all required variables in case of RVCTToolChain/GnuPoc
      - QtVersionManager: Detect toolchain and Qt version properly, make S60
        device run config accept toolchain.
      - Modify S60DeviceRunControl to execute 'make sis'
      - Modify S60Devices::detectQt...() to check for Qt installed into SDK
        first and symlink as fallback.
    • Tobias Hunger's avatar
      Default to not shadowbuilding · efe3ac59
      Tobias Hunger authored
       when not set to true in the .user-file.
    • Tobias Hunger's avatar
      Remove default Qt version entry · 563983c4
      Tobias Hunger authored
       * Remove default Qt version from list of available versions
    • dt's avatar
  28. 16 Feb, 2010 1 commit
  29. 10 Feb, 2010 1 commit
  30. 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
  31. 02 Feb, 2010 1 commit