Knowing more than one compiler is a good thing. I am not saying that your switching compilers is a path to doom, of course. I have seen several projects die because the team could not stand to admit mistakes and kept chugging along on a path to doom. But it is OK to backtrack if you ever find out that your original decision was not the best one. If you want to do it that badly, you do not need to justify the decision to me. Now it seems like you are reaching for any reason to switch compilers.

Now you have to learn what a whole new set of errors mean.Īnyway, VC++ is too big and Code::blocks is smaller ) I have never gotten an error that I could not decipher after a some thinking, and I guess everyone else is the same, so switching compilers because you do not like the errors is a step backward. That is why relying on google to solve your problems is not the best idea. The 'Toolchain Executables' seems key, and I found it odd that the specified directory was one up from the bin directory (but I guess it does have this note in red).īut i've read about some which come only in VC++ and googling usually doesn't fix the issue :/Īll compilers throw errors like that. I did a BC55 install, grabbed the 'rest of' Code::Blocks (I was previously only using the MinGW port), did the configuring you mention doing, and was able to build a Hello World with no such errors. I was led to project>build options where i confirmed that the selected compiler was Borland. It still was stubborn and showed that error. So i set the SELECTED COMPILER dropdown to Borland C++ compiler(5.5, 5.82) and in search directories, set the path to the respective directories. I have Borland C++ compiler in, say, C:/Borland/BCC55. Skipping.įollowed some google links that told me to see the compiler and debugger settings, and check to see the compiler. Thing is, when i decided to compile the program, it wouldn't compile.

Installed it and stuff with ease, and decided to test it with a helloworld program.

Codeblocks compiler not starting