1. 19 Jun, 2014 1 commit
  2. 18 Jun, 2014 1 commit
    • Dale Marchand's avatar
      Fixed compilation error on RHEL 5.10. · ff52061e
      Dale Marchand authored
      
      
      Nesting the namespace "Internal" inside of other namespaces and using
      sequential "using namespace" directives *or* relying on a "using
      namespace" directive to resolve a method name that contained the
      "Internal" namespace for resolution resulted in ambiguous resolution
      errors when compiling with the RHEL5.10 stock compiler (GCC 4.1.2).  A
      sample error is provided below:
      
      Compilation error encountered was:
      reference to 'Internal' is ambiguous
      /usr/lib/gcc/x86_64-redhat-
      candidates are: namespace Internal { }
      qt-creator/src/libs/cplusplus/PPToken.h:106: error:
      namespace CPlusPlus::Internal { }
      
      Modifying the using namespace directives to reflect the nested nature of
      the namespace names resolved the compilation errors.  For example:
      
      using namespace CppEditor;
      using namespace Internal;
      
      produced errors.  However,
      
      using namespace CppEditor;
      using namespace CppEditor::Internal;
      
      resolved the compilation errors by removing the ambiguity.
      
      Change-Id: I6d5051e20acb2c147bd7ee1c6c6e1e3b2b4ff0f9
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      ff52061e
  3. 16 Jun, 2014 1 commit
  4. 13 Jun, 2014 2 commits
  5. 12 Jun, 2014 1 commit
  6. 11 Jun, 2014 1 commit
  7. 06 Jun, 2014 3 commits
  8. 05 Jun, 2014 1 commit
  9. 04 Jun, 2014 1 commit
  10. 03 Jun, 2014 3 commits
  11. 02 Jun, 2014 2 commits
    • Oswald Buddenhagen's avatar
      avoid that a bad qmakespec path crashes the evaluator · e017a1dc
      Oswald Buddenhagen authored
      
      
      assigning a relative path to QMAKESPEC or QMAKESPEC_ORIGINAL (in the qt4
      windows legacy code) would lead to an assert further down the line.
      just ignore such attempts silently.
      
      Task-number: QTCREATORBUG-8477
      Change-Id: Ie53d0ef004c743284b85de4e89f112e0161ff4b7
      Reviewed-by: default avatarDaniel Teske <daniel.teske@digia.com>
      e017a1dc
    • Andreas Pakulat's avatar
      Fix matching of partial paths on Windows · cf6e4b8d
      Andreas Pakulat authored
      
      
      The paths against which the match is done always have forward slashes (i.e.
      uniform separator on all platforms). However the needle passed in has
      backward slashes on Windows usually, since this is how the paths are shown
      to the users and what is natural on windows too. Even explicitly using
      forward slash in the needle does not work here, since then the needle is
      not detected as containing a path (hasPathSeparator is false since it uses
      the native separator).
      
      Since it seems that the code internally favors the 'uniform' separators
      using slashes, simply convert the needle from native to uniform separators
      and use the forward slash to decide whether the needle has a path in it.
      
      Side effect of this is that it is now possible to use forward slashes when
      typing into the locator UI on windows. The opposite does not work on Unix
      though. That could be considered a feature though for cross-platform
      developers.
      
      Task-number: QTCREATORBUG-12007
      Change-Id: I5064bd9c60936466dd04671ef42a578df26ea7b8
      Reviewed-by: default avatarDavid Schulz <david.schulz@digia.com>
      cf6e4b8d
  12. 30 May, 2014 1 commit
  13. 28 May, 2014 2 commits
  14. 26 May, 2014 2 commits
  15. 22 May, 2014 2 commits
  16. 20 May, 2014 1 commit
  17. 19 May, 2014 4 commits
  18. 16 May, 2014 1 commit
  19. 14 May, 2014 1 commit
  20. 13 May, 2014 3 commits
  21. 12 May, 2014 2 commits
  22. 09 May, 2014 2 commits
  23. 08 May, 2014 1 commit
  24. 07 May, 2014 1 commit