Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: cktdesigner on January 08, 2009, 07:52:56 pm
-
I am trying to use C::B to write code for an embedded project. I have multiple targets: One is a local test environment that uses the Cygwin GCC compiler. This works fine.
The HW embedded target is a MIPS varient that I have a GCC generated tool-chain for. This tool-chain works fine when used in a standalone (command line) environment.
I have tried to add a target that uses the MIPS GCC compiler from within C::B. I did this by:
1. Setting up the compiler path, executable names, and includes, etc. from the Settings->Compiler... setup
2. Selecting this compiler for the HW target
To test I select the HW build target, select a single source file and request that the file be built.
C::B Pops up a "Microsoft Visual C++ Runtime Library" error box indicating:
"Runtime Error!"
"Program: C:\Program Files\CodeBlocks\codeblocks.exe"
"This application has requested the Runtime to terminate it in an unusal way."
"Please contact the application's support team for more information"
Did I miss something in the specification of the target compiler?
Thanks...
-
In my mind, Code::blocks doesn't need any thing from "visual C++ runtime library". So, I guess that you compiler or other command tool chain need Visual c++ libraries. :D.
-
In my mind, Code::blocks doesn't need any thing from "visual C++ runtime library". So, I guess that you compiler or other command tool chain need Visual c++ libraries. :D.
That's not 100% correct, C::B needs MinGW-dll(s), and MinGW uses MSVCRT.dll and there can be the problem.
Mabe you find a solution in this thread: http://forums.codeblocks.org/index.php/topic,7691.0.html (http://forums.codeblocks.org/index.php/topic,7691.0.html)