1. 17 Aug, 2010 1 commit
    • dt's avatar
      Fix DESTDIR=. case · 46b414f5
      dt authored
      Qmake treats "." special, we need to do the same
  2. 06 Jul, 2010 1 commit
  3. 18 Jun, 2010 1 commit
  4. 16 Jun, 2010 1 commit
  5. 09 Jun, 2010 2 commits
  6. 04 Jun, 2010 1 commit
  7. 18 May, 2010 4 commits
  8. 07 May, 2010 1 commit
  9. 14 Apr, 2010 1 commit
  10. 13 Apr, 2010 1 commit
    • dt's avatar
      Fix ui completion for new projects · c58469ce
      dt authored
      The UI_DIR and MOC_DIR weren't added to the includepath for new
      projects, since at the time of parsing the directories don't exist yet.
      We now always add UI_DIR and MOC_DIR to the include path, without caring
      whether they exist.
      Task-Nr:  QTCREATORBUG-1064
      Reviewed-By: ossi
  11. 29 Mar, 2010 2 commits
  12. 22 Mar, 2010 1 commit
  13. 17 Mar, 2010 1 commit
  14. 15 Mar, 2010 1 commit
    • dt's avatar
      Add new on virtual folders adds to the wrong path. · 6ecd9cc5
      dt authored
      The solution ain't great. Essentially we need to fix that path() needs
      to be unique and a 1:1 mapping to the file system by introducing a
      separate method for the first usage.
      Task-Nr: QTCREATORBUG-828
      Reviewed-By: con
  15. 12 Mar, 2010 1 commit
  16. 11 Mar, 2010 1 commit
  17. 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
  18. 05 Mar, 2010 1 commit
  19. 26 Feb, 2010 2 commits
  20. 24 Feb, 2010 3 commits
  21. 17 Feb, 2010 1 commit
  22. 12 Feb, 2010 1 commit
  23. 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
  24. 02 Feb, 2010 2 commits
  25. 01 Feb, 2010 1 commit
  26. 25 Jan, 2010 6 commits