User forums > Using Code::Blocks
invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!]? Toolchain path?
Ceniza:
I think this is the video I watched before: http://www.youtube.com/watch?v=ec-yYMTUV3c (at 2:40).
oBFusCATed:
--- Quote from: jens on August 27, 2010, 10:03:08 pm ---Newer revisions of C::B give this error-message:
--- Quote ---The compiler's setup is invalid so Code::Blocks cannot find/run the compiler. Probably the toolchain path within the compiler options is not setup correctly?! Skipping...
--- End quote ---
It might be easier to understand.
--- End quote ---
Probably it should be:
--- Quote ---The compiler's setup is invalid so Code::Blocks cannot find/run the compiler. Probably the toolchain path within the compiler options is not setup correctly?!
To fix you compiler options go to "Settings -> Compiler & Debugger -> Compiler -> [the compiler used for current project/target] ->Toolchain executables" and verify that the path is correct.
Code::Blocks failed to find and execute: [full path to the executable]
Skipping...
--- End quote ---
bendwalk:
In order to increase your pool of known solutions to this problem, I wanted to let you know that I had this issue and discovered I did not have a compiler installed. I had assumed the compiler would have come with the Code::Blocks install, but a quick download later from http://tdm-gcc.tdragon.net/ and I had my compiler. Then I just had to change the "Toolchains-executable" path to C:\MinGW32 and it worked for me. However, the Auto-detect feature did not find it...
Thanks for all the tips across multiple threads.
Yamakuzure:
Sorry for resurrecting this thread, but doing a forums search on the current error message "The compiler's setup is invalid so Code::Blocks cannot find/run the compiler. Probably the toolchain path within the compiler options is not setup correctly?! Skipping..." does _not_ find anything, and when searching for "compiler invalid" this thread is the top one with most "relevance" factor.
--- Quote from: stahta01 on August 27, 2010, 10:28:51 pm ---Based on the Times I helped users on this issue the three top causes are
1. User does not have an compiler installed.
--- End quote ---
Visual Studio 2008 with C/C++ and Service Pack 1 is installed on this machine.
--- Quote from: stahta01 on August 27, 2010, 10:28:51 pm ---2. C::B is not configured right to use the installed compiler.
--- End quote ---
Neither the Visual Studio's VC nor the VC/bin directory seems to be right. Debugging tools and SDK are set as additional paths.
When opening cmd the command cl.exe provides:
--- Code: ---P:\Codeblocks>cl.exe
Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version 15.00.30729.01 für 80x86
Copyright (C) Microsoft Corporation. All rights reserved.
Syntax: cl [ Option... ] Dateiname... [ /link Linkeroption... ]
--- End code ---
So path and environment are correctly set.
--- Quote from: stahta01 on August 27, 2010, 10:28:51 pm ---3. The user did NOT install the Compiler Correctly; example missing part of the MinGW installation
--- End quote ---
Visual Studio 2008 is working fine. Including nmake.exe, cdb.exe, link.exe and cl.exe from the command line.
I have tried deleting the default.conf file and restarting C::B with a new config. Autodetect works fine, setting all paths and toolchain executables by itself. But unfortunately that's all.
I was completely stuck here, because the message appears immediately when trying to compile. I had an issue with a folder not set in the path environment variable, so a .dll could not be found when trying to start cl.exe. But this issue is fixed.
How can I be sure that Code::Blocks _really_ tries to execute cl.exe in the specified path? And if it does why isn't there a message stating what went wrong?
My settings:
Compiler's installation directory: P:\VStudio2008\VC
C++ compiler: cl.exe
--- Code: ---P:\VStudio2008\VC>dir /B bin\*.exe
bscmake.exe
cl.exe
cvtres.exe
dumpbin.exe
editbin.exe
lib.exe
link.exe
ml.exe
nmake.exe
pgocvt.exe
pgomgr.exe
pgosweep.exe
undname.exe
xdcmake.exe
--- End code ---
So what is the solution here?
The solution is, that although Code::Blocks is correctly configured, the project is a cross-platform project copied from a linux machine.
If all your settings are correct, you might want to make sure, that the Build Options of your project show the same compiler used you set up. ;)
Cheers
P.S.: Edith fixed some typos, but probably not all...
oBFusCATed:
--- Quote from: Yamakuzure on December 30, 2010, 01:09:04 pm ---If all your settings are correct, you might want to make sure, that the Build Options of your project show the same compiler used you set up. ;)
--- End quote ---
So you fixed your problem?
@devs: Would you accept a patch that implements the error message I've suggested?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version