Can the problem come from the 13.12 version ?It is possible. Have you tried a nightly?
EDIT :I didn't modify the folder hierarchy.
I tried with C::B 4.8.1, C::B 10503 and same MinGW 4.7.3 as ollydbg, I even tried to modify the folder hierarchy but ofcourse the compiler was lost.
I tried on Ubuntu 15.04 with gcc 4.9.2, same thing, you dont have autocompletion for thread, array etc ...Normally, if you have "enabled the C++" option in your project or target, then CC will use this option to obtain the correct predefined macros, such as __cplusplus__, which could reflect the C++11 option. Then the parser can parse something like:
I have no more ideas to obtain this proper autocompletion.
#if _cplusplus__ > 20110301
#include <thread>
#endif
I downloaded MinGW 4.9.3 SEH POSIX 64 bits compiler and I created a new compiler in the IDE.
Thanks for your suggestion. I tried renaming the "classic" MinGW build I DL and the one provided by Qt but in both cases, auto-detection fails.
Maybe the way C::B was designed, it recognizes efficiently only TDM compilers files names.
D:\mingw\i686-w64-mingw32\includerespectively into both the global Compiler Settings and Compiler Include Search Paths as well as the project's local Build Options and C/C++ Parser Options Additional Search Paths, and while I've finally got the STL header files like <vector> to be CC'ed, I still can't CC a std::vector.
D:\mingw\i686-w64-mingw32\include\c++
D:\mingw\i686-w64-mingw32\include\c++\bits
Is there a conclusion? I have some similar problems with mingw-builds' GCC 5.2.0 + Code::Blocks svn 10595.Why do you add those paths manually? Our CC's parser will automatically call the GCC command with the "-E" option, and grab the GCC's search paths.
I've enabled C++14 and addedQuoteD:\mingw\i686-w64-mingw32\includerespectively into both the global Compiler Settings and Compiler Include Search Paths as well as the project's local Build Options and C/C++ Parser Options Additional Search Paths, and while I've finally got the STL header files like <vector> to be CC'ed, I still can't CC a std::vector.
D:\mingw\i686-w64-mingw32\include\c++
D:\mingw\i686-w64-mingw32\include\c++\bits
Weird is that things like std::bad_alloc can be CC'ed. What's going on? Doe this have anything to do with HeaderFixup in Environment Settings?
...Done in rev10618. You guys can test it if you can build c::b from source yourself.
Maybe, you may see the bug here Re: Release 15.12, RC1 has arrived (http://forums.codeblocks.org/index.php/topic,20729.msg141532.html#msg141532), I'm going to commit a fix soon.
Why do you add those paths manually? Our CC's parser will automatically call the GCC command with the "-E" option, and grab the GCC's search paths.Thanks for the tip. I added the paths and kept them there back in some old days when CC couldn't even sometimes locate the C++ headers. It used to work until I updated my compiler toolchain and the IDE. It looks like things have changed, maybe somehow improved as removing them actually solves my old and new problems here. I might give the latest svn a try when I get the time to.
If you have enabled the C++11, then CC will call GCC command with the C++11 option.
Maybe, you may see the bug here Re: Release 15.12, RC1 has arrived (http://forums.codeblocks.org/index.php/topic,20729.msg141532.html#msg141532), I'm going to commit a fix soon.