Is there a case where you have two different linker executables (one for C and one for C++) and they are not the same as the compiler executables?
In my small world i only know GCC and MSVC but in CodeBlocks there is a long list of other compilers and i don't know how they work. I don't know how often these other compilers are used and how much people will complain if something doesn't work anymore, your changes are about solving issues, don't introduce new ones by using wrong magic
p.s. I plan to add a setting for asm compiler. Should we add a linker for asm after that?
I never had to deal with assembler code in my projects so i can't even offer dangerous superficial knowledge here. That needs an own linker to link with what, a regular C/C++ project? Or are you talking about standalone support for a plain ASM compiler like for Fortran, which i also never used
? Beside C++-sources i only have to deal with
.wxrc and
.proto p.p.s. Do you have a valid case where you really want to force a project to compile as C?
I am a C++ developer and so far i only had problems with some C sources i needed to include into a project that just don't compile in C++ mode. Shame on me i didn't even know you need a different linker on GCC to produce a C-only executable
. In MSVC you don't and that one offers global switches to turn on C mode or C++ mode, but still this doesn't have any influence on the linker stage. On second thought maybe that use-different-linker-if-everything-is-c is kind of a GCC internal and automagic could solve this invisible to the user
.