Converting Torque Game Engine VC7 projects to CodeBlocks

[brandon8863]

I've been wanting to do some tutorials to help new users of the TGE platform get their feet wet with C++. CodeBlocks looks to be the perfect answer, but I'm having a couple of issues getting the VC7 project files across to CodeBlocks. Here is a small list of things I've noticed, and/or would appreciate some insight into:

1. When the project gets large, I've noticed a 'Can not wait for thread termination (error 6: the handle is invalid)' when loading up the project files. When you click 'details' it is filled with hundreds of error6 and error8 (can not wait/create/resume thread, and handle invalid errors)

2. How are the use of .DEF files from visual studio accounted for in CodeBlocks? It keeps giving me 'undefined reference to' errors from these .def file mappings.

3. Is the free VisualStudio2003 C++ Toolkit the best compiler to use when converting a VS7 solution?

4. Are there any resources or kind people able to answer some more involved questions during this coversion process? And even more important: is this conversion possible with the existing features in CodeBlocks?

Thanks,

Brandon.

[darklordsatan]

1. When the project gets large, I've noticed a 'Can not wait for thread termination (error 6: the handle is invalid)' when loading up the project files. When you click 'details' it is filled with hundreds of error6 and error8 (can not wait/create/resume thread, and handle invalid errors)

Seems like you're not the only one. I got those error msgs 24/7 when trying to import the VC6 wxwidgets project files...

[rickg22]

Stan, mind giving me an example or how to replicate it? I don't have VC++, and I'm tired of these bug reports. I want to fix them, but I haven't found a way to get those errors.

[darklordsatan]

Rick, you dont need VC6 for this... What we're talking about is importing projects inside C::B.
Im gonna pretend youre not one of the main developers, and you just downloaded C:B yesterday. So that others that might like to try on their PCs to see if they get the same results have no problems replicating this:

Go to Project->Import->MS Visual C++ Workspace, then select
$WxWidgets-2.6.1-SOURCES_FOLDER\build\msw\wx_dll.dsw

I ended up with this after like 6 mins


And C::B was actually taking up as much as 62Mb of RAM by that time...

And I attached the log, but its actually worthless... Anyway, you need to rename it to .zip

[attachment deleted by admin]

[rickg22]

Sorry, I meant that I might need VC to test the actual compilation process etc. But that's not really needed.

Thanks for the importing instructions.

[rickg22]

Couldn't replicate it!

All i got were "path blahblahblah contains too many ..!"

[darklordsatan]

Couldn't replicate it!

All i got were "path blahblahblah contains too many ..!"

What? What path, the wx one? and too many "." or ...?

[zieQ]

To add my patchs for MSVC importers, I also tried to open wx vs6 projects files with no problems. I can confirm I have still no problem to load them now with CVS V1 and HEAD versions  :shock: . But I can assure you it is way too long to load, especially with MSVC6, seems that the parser should be optimized.