Should have the "selected compiler" name at the top of the window that show up. I suggest trying to find out the default compiler. IIRC, when compiling without a project the default compiler is used. In this case, it sounds like CB detected a compiler and made it the default compiler. The normal cause is the user has no Compiler installed on their computer. If you have more CB related questions, you will probably get better answers here: all else fails, back up your c files, uninstall and reinstall CB, which will default back to original settings.Actually this in one question you are not likely to get better answers on the CB site asking. If you didn't have the build log open, then it would appear that nothing happens when you try to build.The toolchain message has to do with specifying the path to the relevant directories that the compiler needs to access, and depends on the compiler that you have chosen. Anything and everything related to the C::B nightly builds. Nothing to be " in done in the build log. This forum is for discussing the use of Code::Blocks for embedded development. When you try to build a program that has already been built, you should see something like "Target is up to date. When using CB, you can press F2 to see the logs window. You can try choosing MinGW as the compiler. CB(for Windows) might come with MingGW though, which is a Windows port of GCC. If it works with the Intel compiler, then change it back to that, or copy the code into a new project set with the Intel compiler.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |