Well, the problem is that different compilers do not use the same switches. They do not even use the same filenames or compatible library images...
There is no way you can convert a MSVC project to gcc with one click...
No, but my intention was to be able to save one same project with switches for different compilers.
i.e. storing the MSVC and GCC configs in one same cbp.
Yiannis, please explain to me because it seems i kinda missed the boat with the latest "target" changes on the build process.
For a project like Code::Blocks, which has a lot of targets, how could this (having switches for diff compilers on one same cbp) be done?
Edit: Thanks, tiwag. But look at the current "project build options" dialog. Wouldn't it be good that if you switched the compiler (i.e. from MSVC to GCC), a new set of default options would appear, and if you switched back, the first options were just like you left them before changing the compiler dropdown? Currently, whenever we switch the compiler for a project or target, the target's build options are updated. Wouldn't it be good to store the options for all the compilers used? i.e. a target having a set of options for GCC and for MSVC, and when compiling, only the options for the respective compiler were used... this (unlike being forced to use different projects/workspaces) seems very intuitive to me.
Yiannis, your stance on this?
Edit again: Thanks again, tiwag, we seem to think very alike! :lol: