|
|
| Re: Symbol 'std' could not be resolved [message #778988 is a reply to message #778572] |
Sat, 14 January 2012 10:17   |
 Jeroonk 
Messages: 1
Registered: January 2012 |
Junior Member |
|
|
Do you perhaps have an operating system which is not set to US English as default language?
I am working with a set-up almost exactly as you have, and have been struggling with a similar problem since I upgraded MinGW to 4.6.2.
Normally, CDT should detect the installation of MinGW and also auto-discover include configurations and symbols when you build a project.
There should be no need to manually add those standard include paths.
The way CDT does this is by compiling a small file, and analyzing the output of the compiler.
It then extracts all necessary compiler configuration from this output, e.g. include-paths and symbols.
You can find these option under: "(Project) Properties -> C/C++ Build -> Discovery Options".
Since a few versions ago (I don't know the exact one), MinGW enabled support for localized compiler output.
If you are running a French operating system, you will get French compiler warnings and messages.
CDT doesn't like this; it's auto-discovery becomes broken, and you are left with an editor which doesn't know about the standard library includes.
To fix this, I forced the compiler to use English output when building:
Under "Window -> Preferences -> C/C++ -> Build -> Environment", add two new environment variables "LANG" and "LC_ALL" and set them both to "en_US".
Rebuild your project, and CDT should discover the correct include paths again.
[Updated on: Sat, 14 January 2012 12:02] Report message to a moderator |
|
|
| Re: Symbol 'std' could not be resolved [message #779668 is a reply to message #778694] |
Mon, 16 January 2012 09:43 |
Axel Mueller
Messages: 1973
Registered: July 2009 |
Senior Member |
|
|
framontb framontb wrote on Fri, 13 January 2012 17:41It is a bug reported and not solved: Bug 353719 - Built-in includes seem to be broken for Cross GCC
Now I'm using the previous version eclipse Helios that works without the bug.
Regards: framontb
You should select the MinGW-Toolchain in Eclipse and not Cross GCC. Then scanner discovery will find all the includes automatically.
Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
- google
|
|
|
Powered by
FUDForum. Page generated in 0.02613 seconds
] 
Search
Help
Register
Login
Home
