Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Using VC Toolkit to compile C::B
Cyberax:
--- Quote from: grv575 on September 27, 2005, 03:31:24 am ---
--- Code: ---SomeFunc(_("Text, text, text \
text continues \
end of text"));
--- End code ---
gives extra whitespace or no? (forget)
--- End quote ---
Yes, it does.
Anyway, the Right Thing (tm) to do is using resource bundles. Maybe someone should bite the bullet and extract all text strings to resource files?
tiwag:
--- Quote from: Cyberax on September 26, 2005, 02:44:50 pm ---
* 1. Compile wxWidgets:
* 2. Open CodeBlocks-wx-vc.cbp with C::B and compile it.NOTE: C::B and wxWidgets will be compiled in debug mode ...
--- End quote ---
Hi Cyberax
now i've build C::B with VisualStudio2003 (VC7.1)
using your project file adapted for wxMSW2.6.1_ansi_debug_dll
with the unicode version i couldn't open a single file !
well, the result isn't exciting till now.
It compiles with 124 warnings and works with a number of flaws (but no crash till now) and runs terribly slow !
There is a lot of work to do until we have a M$-VS port of C::B, but a start is made ...
thanks again for your input, Cyberax.
Cyberax:
--- Quote from: tiwag on September 27, 2005, 02:58:12 pm ---now i've build C::B with VisualStudio2003 (VC7.1)
using your project file adapted for wxMSW2.6.1_ansi_debug_dll
with the unicode version i couldn't open a single file !
--- End quote ---
It's strange, Unicode version of C::B worked fine for me. I was able to compile C::B from it.
--- Quote ---well, the result isn't exciting till now.
--- End quote ---
I know :(
--- Quote ---It compiles with 124 warnings and works with a number of flaws (but no crash till now) and runs terribly slow !
There is a lot of work to do until we have a M$-VS port of C::B, but a start is made ...
--- End quote ---
I've fixed some warnings in my working copy. I was also able to compile a release version of C::B (and it runs very fast), but it crashed during compilation.
I'd greatly appreciate project admins giving me a write access in CVS (in a branch or a separate directory), so I can share my bugfixes.
tiwag:
--- Quote from: Cyberax ---...
I've fixed some warnings in my working copy.
I was also able to compile a release version of C::B (and it runs very fast), but it crashed during compilation.
--- End quote ---
There is something bad with event handling - the speed-difference between debug and release versions can't be that big. My build consumes up to 95% of cpu-power just when moving the mouse around the C::B-window ! The menus react with 0.5 to 2 sec. delay ! terrible slow !
--- Quote from: Cyberax ---I'd greatly appreciate project admins giving me a write access in CVS (in a branch or a separate directory), so I can share my bugfixes.
--- End quote ---
you can make patch-files, zip them, then rename the extension .zip to .txt and post the files here in this thread.
Cyberax:
--- Quote from: tiwag on September 27, 2005, 05:14:22 pm ---
--- Quote from: Cyberax ---
--- End quote ---
There is something bad with event handling - the speed-difference between debug and release versions can't be that big. My build consumes up to 95% of cpu-power just when moving the mouse around the C::B-window ! The menus react with 0.5 to 2 sec. delay ! terrible slow !
--- End quote ---
Can you check your debugger log? If C::B constantly writes messages there, it can easily slow everything by the factor of 10.
--- Quote from: tiwag on September 27, 2005, 05:14:22 pm ---
--- Quote from: Cyberax ---I'd greatly appreciate project admins giving me a write access in CVS (in a branch or a separate directory), so I can share my bugfixes.
--- End quote ---
you can make patch-files, zip them, then rename the extension .zip to .txt and post the files here in this thread.
--- End quote ---
I'm going to setup a private SVN repository (with anonymous read-only access) and sync it with the main C::B repository using SVK (http://svk.elixus.org/).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version