Thanks Bidski for your help!
I found what my mistake was and it was that I forgot to set the proper 
variable under "Settings->Compiler/Debugger->Toolchain 
Executables->Compiler's Installation Directory".

Thanks!

On 9/3/2010 5:40 PM, Bidski wrote:
> Im not sure if CB is one of them, but some IDEs have a specific set of 
> directories that it will search for MinGW. The standard directory is 
> usually C:\MinGW, if you have installed MinGW to a different location 
> it may not know where to find it (some IDEs dont even look at the PATH 
> variable).
>
> Regards
> Bidski
>
> -----Original Message----- From: ArbolOne
> Sent: Friday, September 03, 2010 11:55 PM
> To: [email protected]
> Subject: [Mingw-w64-public] Win7-64 - TDM-GCC & C::B
>
>  I just got a new Win7-64; I proceeded to download/install  TDM-GCC
> Compiler Suite for Windows, having done that I continued with the
> installation of CodeBlocks. I am currently trying to compile a simple
> "Hello" program, but to no avail. I get this error message:
> ======
> "testingCB - Debug" uses an invalid compiler. Probably the toolchain
> path within the compiler options is not setup correctly?! Skipping...
> Nothing to be done.
> ======
> However, the MinGW64/bin directory has been added to the "%path%"
> (twice!), once by the installer and once by me.
> In an attempt to resolve this issue, I have change the toolchain in the
> "Settings->Compiler/Debugger->Toolchain Executables"  from the default
> "gcc" to "x86_64-w64-mingw32-gcc.exe". I did the same with the g++'s
> entries. But this did not change anything.
>
> What am I doing wrong?
> Can anybody help?
>
> TIA
>
>


------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to