CW8 Compile on Windows
by varmint · in Torque Game Engine · 12/25/2002 (9:29 am) · 7 replies
About the author
#2
it could be lots of things, but it's weird that CW7 builds and runs fine, and CW8 does on the Mac.
d
01/01/2003 (2:48 pm)
just look through the makefiles. I haven't had any time to yet. too many other things on my plate... ;)it could be lots of things, but it's weird that CW7 builds and runs fine, and CW8 does on the Mac.
d
#3
01/23/2003 (2:20 pm)
I have the exact same problem with Codewarrior 6 and WindowsXP. And Visual C++ .NET doesnt seem to agree with torque either. So im kinda at in the sh**.
#4
Well, codewarrior expressly uses some C replacements of some older ASM files. But in the 18+ months I've been working on stuff, I've never seen or heard of such issues that weren't, say, driver related or something like that.
Any other leads would be appreciated, as I'd like to try and help out here.
d
01/23/2003 (9:50 pm)
Hmmm.Well, codewarrior expressly uses some C replacements of some older ASM files. But in the 18+ months I've been working on stuff, I've never seen or heard of such issues that weren't, say, driver related or something like that.
Any other leads would be appreciated, as I'd like to try and help out here.
d
#5
01/24/2003 (7:37 am)
All I can really say is it happens on 1.1.1, 1.1.2, and the HEAD. And only when compiled with Codewarrior.
#6
It's been a LOOOOONG time since I used CW6 -- I updated to 7 in sept 01, so I can't really say what might possibly be at the core of the problem. But, back in the early days, I was building with both 6 and 7 on windows, and had no such problems.
If I have extra time (), I'll try to find and install CW6 and see what results I get... but the timing of that could be a while off yet.
d
01/25/2003 (10:12 am)
I assume you have all compiler updates installed? don't know if there could be a compiler issue there.It's been a LOOOOONG time since I used CW6 -- I updated to 7 in sept 01, so I can't really say what might possibly be at the core of the problem. But, back in the early days, I was building with both 6 and 7 on windows, and had no such problems.
If I have extra time (
d
#7
Note that some modules (the milkshape exporter, opengl2d3d, etc.) can only be compiled and linked with Visual Studio; they flat out can't be linked with CodeWarrior, due to the use of the D3DX stuff (the extended templates).
If you can either post the specific details of your problem (i.e. the exact error message), I may be able to help.
So far as VS.NET goes, it is possible to use VC 7 to compile the executable; CW 7 produced a smaller and faster executable with optimization off and debugging on than VS.NET produced with optimization on -- measured using TorqueDemo.
01/27/2003 (10:43 am)
If you send me an e-mail with what's going on with CW 6, I've talked about four other people through getting it going with CW 6.Note that some modules (the milkshape exporter, opengl2d3d, etc.) can only be compiled and linked with Visual Studio; they flat out can't be linked with CodeWarrior, due to the use of the D3DX stuff (the extended templates).
If you can either post the specific details of your problem (i.e. the exact error message), I may be able to help.
So far as VS.NET goes, it is possible to use VC 7 to compile the executable; CW 7 produced a smaller and faster executable with optimization off and debugging on than VS.NET produced with optimization on -- measured using TorqueDemo.
Torque Owner David Chait
I can't explain why it would build but not work. CW7 and CW6 did just fine...
Will have to look into it in the next week or two as I find time from other projects.
d