Alright! Thanks Yiannis! I guess I'll add it to the "current issues". Please tell us when it's fixed, anyway.
I might as well state the problem here.
The problem has to do with templates (obviously
). There's a piece of code in C::B that, when a project is created from a template, sets the default compiler to be the new project's compiler. This piece of code is commented-out for RC2 (and quite some time for CVS).
So, this is the reason for the behaviour stated in this topic.
Now, you may ask why I did that.
Well, the current template format is a little restrictive for this matter.
Some templates (like console app, win app, dll, etc), have nothing compiler-specific in their options. For them, the compiler could be set on project creation.
Some other templates though (like wxWidgets, Ogre, Irrlicht) have different configs for different compilers. This can be seen in the "Project options" field of the "New project" wizard, as they have different entries for GCC and MSVC (under windows anyway). For these templates it would be bad to set the compiler after creation.
Say you have GCC as default compiler. And you create a new Ogre project for MSVC (which you have installed). Now, how nice it would be if you pressed "Build" and a whole lot of errors appeared and after searching around you discovered that the compiler was (automatically) set to GCC? You would bitch against Code::Blocks and that would be fair enough
See the dilema?
Maybe a flag in the template specification allowing (automatic) compiler change after project creation, would do the trick?
Your views on the subject please...