Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Build CodeBlocks using Microsoft Visual C++
oBFusCATed:
Ceniza:
You need Visual Assists in VS 2010, so they failed to make the CC work again?
It is normal for VS to be better, because it is 10+ developers working part time vs 10-20-100 working full time.
The remarkable thing is how close (and even better for some things) C::B is to VC in many aspects.
(I've not tried 2010, yet)
Biplab:
My few cents!
First of all I'd like to say Thanks to Loaden for this effort. :)
I do agree VS debugger is better in some cases. I am also facing a similar issue with my 64 bit porting. GDB can't give me any meaningful reply on why C::B is crashing. So I think once C::B source can be compiled with VC, I may get some clue. Personally I am also working on patching C::B source to be compatible with VC (I have compiled upto SDK). But after Loaden's patch it will be easier for me.
I differ on some opinions expressed on using ifdefs. Personally my opinion is - as long as it doesn't affect officially supported compiler, ifdef's should be ok. They add bloat to the source; not to the binary. And with the code-folding feature in any modern IDE/Editor, it is not an issue anymore that source code will become unreadable. :)
Loaden & others - Keep up the good work! Cheers!
oBFusCATed:
Biplab: debugging on 64bit is harder than 32bit in general and it is because of the way the processors work.
Have you tried to use -fno-omit-frame-pointer (inspect the manual for the correct option) (it is default on 64bit archs)?
Ceniza:
--- Quote from: oBFusCATed on April 06, 2011, 05:22:20 pm ---Ceniza:
You need Visual Assists in VS 2010, so they failed to make the CC work again?
--- End quote ---
The integrated IntelliSense seems to be good (barely tried it), but Visual Assist X is just great. I had already got it before switching to VS 2010, and life is just not the same once you get used to it. The renewal is quite cheap also, and, once again, I am not the one paying for it.
I still do not get why you say 64 bits is harder to debug. You get more, and wider, registers, and the calling convention defaults to fastcall. Other than that it is pretty much the same as with 32 bits. Am I missing anything?
oBFusCATed:
I was using VAssist and then stopped... now I'm using "find in files" or "thread search" ... and I don't feel I've lost something in the functionality.
The backtraces have less info in them (there is a doc at work describing the problems) ...
Also http://www.rotateright.com/faq.html#UserInterface_2
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version