Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Support for CodeBlocks in CMake

<< < (4/7) > >>

alex.neundorf:

--- Quote from: thomas on August 28, 2007, 05:23:13 pm ---tcc: ?
--- End quote ---
Tiny C Compiler. Very cool thing, but realistically it's probably of little or no significance.
If you have gcc/mingw, then you are probably making 90% of your users happy already. The intel compiler is one-way-compatible to gcc, and neither bcc nor msvc/msvc8, nor dmc are available on non-Windows platforms, so I don't think one would want to use them for a portable project anyway.
[/quote]

Well, you can write the software in such a way that it works with all these compilers :-)

Alex

Biplab:

--- Quote from: alex.neundorf on August 28, 2007, 05:15:39 pm ---bcc: Borland
cygwin: cygwin gcc
dmc/dmd: is this the D compiler ?
gcc: gcc
gnuarm: gcc (where's there difference ?)
gnuavr: gcc (as above)
icc: Intel
lcc: lcc
mingw: gcc with windows paths or with msys paths ?
msvc: msvc 6 + 7 ?
msvc8: I guess msvc 8 :-)
ow: ?
sdcc: sdcc
tcc: ?

--- End quote ---

Let me complete the blanks. Word on the left before the colon is the Compiler id used in C::B.

arm-elf-gcc: GNU ARM GCC Compiler
avr-gcc: GNU AVR GCC Compiler
msvc: MSVC 6
msvctk: Microsoft Visual C++ Toolkit 2003
ow: OpenWatcom

mandrav:

--- Quote ---I think I can add the include directories at target level.
How does the xml look for that ?
--- End quote ---

You could have a look at the wiki for a detailed description of our file formats.

alex.neundorf:
As I already noted, the generator creates makefiles + CodeBlocks project files.
The makefiles can be for GNU mingw make, cygwin make, MS nmake, Borland make, Watcom make.
This is (except cygwin) independent from the compiler, i.e. the GNU make Makefiles can use gcc or any of the MS cl 6/7/8 compilers, and the nmake makefiles can use cl or gcc or whatever.

For which purpose is the compiler option in the project file used ?
I mean, it is really the compiler, not the makefile ? So if I put "msvc" there and have cmake create mingw makefiles for cl it should be correct ?
(I think then there is no difference between version 6, 7 and 8 for the makefiles).

Alex

Biplab:

--- Quote from: alex.neundorf on August 28, 2007, 08:22:10 pm ---For which purpose is the compiler option in the project file used ?
I mean, it is really the compiler, not the makefile ? So if I put "msvc" there and have cmake create mingw makefiles for cl it should be correct ?
(I think then there is no difference between version 6, 7 and 8 for the makefiles).

--- End quote ---

The compiler name is necessary to launch the appropriate make utility. So if you put msvc there and then create a MinGW makefile, then C::B will instruct nmake to read that makefile. Nmake will fail to read the syntax and the compilation would fail. So this compiler id is necessary for successful compilation.

Navigation

[0] Message Index

[#] Next page

[*] Previous page