Have you tried the Plugins -> Project options manipulator tool?
Help on the spot. Never noticed that tool before. Thanks.
At the first look this seems to work on the cbp und workspace files directly, does it? Although there is not description in the dialog, it looks like a good way to do exotic stuff to a whole workspace that is close to impossible to do otherwise. Also it looks like you can severely destroy your workspace file if you do not know exactly what you are doing
Sadly this is not really something codeblocks supports, and this bothers me A LOT...
Seems I am lucky to to have met the problem only now for the first time
For my particular case I solved it now by renaming the compilers and restarted CodeBlocks. Was quick and worked fine.
Probably it only works because the original name used in the workspace was not available any more, so it assings the new default compiler to all workspace projects (but this is an assumption..).
I "think" there is someone in the forum who uses global variables for the compiler (msvc if i remember correctly) and this probably would work to, but you would have to search the forum for his post...
I never used global vars before I compiled C::B (not understooy for what they would be useful). But I can see that they can be easily used for what you say. I will try that to switch the default compiler by variable between x32 and x64. (since TDM has died the MinGW-W64 do provide only separate compilers) I had them in compiler setting "cards", but it annoyed my every time to scroll down this long list of emtpy exotic compiler shells to the very bottom to select the my other version. It would be much more elegant with global wars.
Thanks for the hint.