1. 04 Apr, 2012 1 commit
  2. 16 Feb, 2012 1 commit
    • Erik Verbruggen's avatar
      Supply c++11 flags and per-project info to c++ code model. · 3aab8bea
      Erik Verbruggen authored
      
      
      A manual squash/merge of the changes below, plus a couple of subsequent
      code fixes.
      
      59085aa5fbb99e2d786cd2c1a06c24a111ccb49f:
          Modify CppModel::ProjectInfo
      
          Adding per project node information, to pass on the correct
          defines/includes for each file, instead of aggregating them incorrectly.
      
          Also split up SOURCES and OBJECTIVE_SOURCES.
      
          Also ask the toolchain to convert the compilerflags to flags the
          codemodel understands, for now only gcc and only c++11.
      
          Also make the toolchain aware of the flags used to compile, so that it
          can emit the correct defines.
      
          Note: No header files are passed on.
      
      74028802314cd4e75b41b46407433e07090a304d:
          GCC: Evaluate cxxflags when checking for predefined macros
      
      ebaaa4957e4c02cc9637a998eddae1d0acd74f83:
          MSVC: Take cxxflags into account when checking for predefined macros
      
      9bfce7e889bcf7bcc47bf880e3ea25945ca7d0d7:
          Compile fixes
      
      Change-Id: I9de94ad038dfc5dc1987732e84b13fb4419c96f5
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@nokia.com>
      3aab8bea
  3. 09 Feb, 2012 3 commits
  4. 01 Feb, 2012 1 commit
  5. 31 Jan, 2012 3 commits
  6. 30 Jan, 2012 1 commit
    • Tobias Hunger's avatar
      Use QUuids to identify tool chains · 52b47364
      Tobias Hunger authored
      
      
      Save/Restore has been updated to reflect this:
      
      We now save manual as well as auto-detected tool chains into the user
      toolChains.xml file.
      
      When loading we load the SDK as well as the user toolChains.xml files.
      We then do a autodetection run. All the tool chains restored that are
      marked up as auto-detected are then checked again:
       * the tool chain was autodetected again: Throw away the newly auto-
         detected tool chain and reuse the saved one. This makes sure we
         keep the QUuid that is now part of the tool chains id.
       * the tool chain was not autodetected again: Throw away the saved
         tool chain.
       * the tool chain was newly autodetected: Add the new tool chain
      
      We keep the old id around in the legacyId() method. It is used when
      loading old .user files only. So there is no need to implement this
      method for new tool chains.
      
      Task-number: QTCREATORBUG-6702
      
      Change-Id: Ifc0a216e5351a8a57db03615ba329e355e7d5f59
      Reviewed-by: default avatarDaniel Teske <daniel.teske@nokia.com>
      52b47364
  7. 26 Jan, 2012 1 commit
  8. 19 Jan, 2012 1 commit
  9. 17 Jan, 2012 1 commit
  10. 06 Jan, 2012 1 commit
  11. 07 Dec, 2011 1 commit
  12. 03 Nov, 2011 1 commit
  13. 08 Sep, 2011 1 commit
    • Tobias Hunger's avatar
      ABI: Improve tool chain selection for Qt projects · aaf260c0
      Tobias Hunger authored
      * Set a null-ABI for toolchains where detection of ABI failed: This
        allows the user to select any tool chain.
      
      * Warn if ABI detection fails by showing a message in the Qt version
        setup dialog
      
      * Do not override the mkspec if the Qt version has a null ABI only:
        We (have to) trust the user to know what he is doing in that case.
      
      * GCC: Add version information to GCC tool chain and use it to select
        the mkspec on Mac.
      
      * GCC: Do not override mkspec if we do a cross-compile
        (and actually detect that).
      
      * GCC: Leave out -32 or -64 from mkspec if the compiler binaries ABI
        matches the target ABI.
      
      * Linux-generic is compatible with all other linuxes (both ways)
        The targets themselves do additional filtering and will remove
        anything that does not work for them anyway.
      
      Task-number: QTCREATORBUG-5756
      Task-number: QTCREATORBUG-5960
      Change-Id: Ib3c0ac91f3aa8e2a823e3e9891a02bdccb97af14
      Reviewed-on: http://codereview.qt-project.org/4281
      
      
      Reviewed-by: default avatarQt Sanity Bot <qt_sanity_bot@ovi.com>
      Reviewed-by: default avatarDaniel Teske <daniel.teske@nokia.com>
      aaf260c0
  14. 18 May, 2011 1 commit
  15. 17 May, 2011 1 commit
  16. 13 May, 2011 2 commits
    • Tobias Hunger's avatar
      Toolchain: Add clang toolchain · f823791d
      Tobias Hunger authored
      Note: Parsing of error messages is still missing. So Build Issues
            are not properly reported yet.
      f823791d
    • Tobias Hunger's avatar
      ToolChain: Add support for mkspecs · df7aa6b5
      Tobias Hunger authored
      Make the toolchains report their mkspec files and use the mkspec of the
      toolchain if it does provide one. Fall back to the Qt version's mkspec
      otherwise.
      
      Task-number: QTCREATORBUG-4396
      df7aa6b5
  17. 06 May, 2011 1 commit
  18. 19 Apr, 2011 1 commit
  19. 13 Apr, 2011 1 commit
  20. 10 Mar, 2011 1 commit
    • Tobias Hunger's avatar
      GCC: Better targetAbi support · 2af69217
      Tobias Hunger authored
      * Save ABI in toolchain
      * have guessGccAbi return a list of possible matches.
      
      Tasknumber: QTCREATORBUG-3996
      Reviewed-by: dt
      2af69217
  21. 28 Feb, 2011 1 commit
  22. 23 Feb, 2011 1 commit
  23. 22 Feb, 2011 2 commits
  24. 21 Feb, 2011 1 commit
    • Tobias Hunger's avatar
      ToolChain: Refactor toolchain support · 8d0c4772
      Tobias Hunger authored
      Refactor ToolChains in Qt Creator:
      
       * Allow for several toolchains of the same type
       * Be smarter wrt. guessing what kind of output a toolchain
         produces. This allows us to eventually handle e.g. embedded
         linux setups way better than before.
       * Be smarter wrt. guessing what kind of environment a Qt version
         needs.
       * Improve auto-detection of toolchains a bit
       * Decide on which debugger to use based on the kind of output
         produced by the compiler.
       * Add options page to configure toolchains
       * Remove toolchain related options from the Qt version dialog
      
      Reviewed-by: dt
      8d0c4772