First of all, I know about the -std=c++11 flag to enable c++11 support and where to place it. I've appended -std=c++11
to Project -> Properties -> C/C++ Build -> Settings -> Tool Settings -> GCC C++ Compiler -> Miscellaneous -> Other Flags
and compiling just works fine. But the indexer doesn't get along, for example if I want to use the emplace
function of std::map
(c++11), it will not find the emplace function.
#include <map>
int main() {
std::map<int, int> data;
data.emplace(5,5);
I've also checked out these related questions:
- Eclipse CDT indexer does not know C++11 containers
- Enable C++11 in Eclipse CDT (Juno/Kepler/Luna) indexer
- http://www.eclipse.org/forums/index.php/mv/msg/373462/909018/#msg_909018
Update: Now that I've played around it even doesn't recognize the std::map type, although compiling fine and eclipse finding all headers...
- Compiler Mingw64 GCC 5.2.0
- Eclipse Mars 4.5
- CDT 8.7
Eclipse Mars does it a bit differently than the previous versions.
Step one gets the indexer error highlighting working - covered in Enable C++11 in Eclipse CDT (Juno/Kepler/Luna) indexer linked above. If you've already done all this, I'll be smurfed if I know what you've run into. Mars has been a bit wonky so far.
By the way, if anyone knows where the global settings are so I can default this behaviour, please let me know.
Step 2 gets the compiler working
Eclipse CDT understands the C++ code in a window by running it through an indexer. This indexer is nothing but an invocation of the GCC C++ compiler with certain compilation options. Sometimes, you might want to change the compiler options used by this indexer.
For example, I recently found that C++11 containers and classes (like future) were not resolved by the indexer and were underlined with red squiggles. This is because the compiler options used by the indexer does not have -std=c++11.
To change the compiler options of the indexer: