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

compile C::B with msvc

(1/3) > >>

Joerg:
Hi,
is there a VC project around for C::B anywhere?
I really don't want to use mingw.
Or can I just open one of the .cbp files and compile
C::B within C::B with msvc?
A visual studio project would be better for debugging I think.
Thank you!

MortenMacFly:

--- Quote from: rekisum on January 16, 2009, 10:23:16 am ---is there a VC project around for C::B anywhere?

--- End quote ---
No and there can't be. C::B was designed to be compiled with GCC only and is not VC compatible. It would even make no sense as C::B is a cross-platform IDE which shall also run under e.g. Linux and/or MAC where you don't have a VC compiler. So why shall we invest in VC compatibility if we have no use for it?

thomas:

--- Quote from: MortenMacFly on January 16, 2009, 11:51:57 am ---No and there can't be. C::B was designed to be compiled with GCC only and is not VC compatible.
--- End quote ---
That might be misinterpreted :)

Code::Blocks was not designed to be compiled specifically with GCC, and it isn't incompatible with Visual C++. It is rather that Visual C++ is not compatible with C++, and no workarounds specific to Visual C++ deficiencies are implemented.

Code::Blocks was designed to be standard C++ to the best of our knowledge and ability (this ability is somewhat limited by several factors, such as for example some of the 3rd party libraries that we use), and to build reasonably warning-free.
When non-standard GCC extensions are used, these are (should be) guarded by corresponding preprocessor statements.
Errors, mistakes, and misconceptions are of course possible, but making Code::Blocks not compile on a particular compiler is not a design criterium :)

XayC:

--- Quote from: MortenMacFly on January 16, 2009, 11:51:57 am ---It would even make no sense as C::B is a cross-platform IDE which shall also run under e.g. Linux and/or MAC where you don't have a VC compiler. So why shall we invest in VC compatibility if we have no use for it?

--- End quote ---

So I guess even the wxWidgets files to compile the library with Visual C++ make no sense.

MortenMacFly:

--- Quote from: XayC on January 16, 2009, 03:17:43 pm ---So I guess even the wxWidgets files to compile the library with Visual C++ make no sense.

--- End quote ---
If you plan to use wxWidgets under Windows only, no.
If you work cross platform, probably need VC and/or are willing to do a separate project (meaning:using another IDE/compiler framework) under Windows, no.
Depends on - for C::B it makes no sense. That's all I said.

Navigation

[0] Message Index

[#] Next page

Go to full version