.NET 2003 Compiling errors (galore)
by Danner Jones · in Torque Game Engine · 10/10/2003 (3:43 pm) · 4 replies
Hello!
I just downloaded the HEAD version of the SDK and made a copy to a separate folder. Trying to compile using VS 1.1 gives a number of errors, including:
==============
...\gllist.h(12): fatal error C1083: Cannot open include file: 'iostream.h': No such file or directory
...\netInterface.cc(58): error C2039: 'getSequence' : is not a member of 'NetConnection'
==============
And a WHOLE lot more.
Here's what I tried:
1. Run VSVARS32.Bat in my VC7\bin folder
2. Run "VC7 .cc compiling.reg" from the Torque SDK's \vc7 folder
3. Open the "Torque SDK.sln" solution from the \vc7 folder
4. In VS, Build->Build Torque Demo
I've also tried loading the VC++ DSW workspace file but receive similar errors.
I CAN compile successfully with VC++ 6.0 (VS 6 with SP5 and I run the VCVARS32.BAT from that folder plus the appropriate .REG file from Torque) .
I've tried removing the ".h" from the include to remove the first error and prefix some of the objects with stdext:: (I think) to try and correct things, but I still get a ton of errors.
NOTE: Between each subsequent build attempt, I delete my temp sdk folder and copy in the files so that I'm always starting fresh from the HEAD version of the code.
Since others don't seem be having any of these issues, I'm hoping I need to set something up differently in my environment. Any ideas?
Thanks,
Dan Jones
I just downloaded the HEAD version of the SDK and made a copy to a separate folder. Trying to compile using VS 1.1 gives a number of errors, including:
==============
...\gllist.h(12): fatal error C1083: Cannot open include file: 'iostream.h': No such file or directory
...\netInterface.cc(58): error C2039: 'getSequence' : is not a member of 'NetConnection'
==============
And a WHOLE lot more.
Here's what I tried:
1. Run VSVARS32.Bat in my VC7\bin folder
2. Run "VC7 .cc compiling.reg" from the Torque SDK's \vc7 folder
3. Open the "Torque SDK.sln" solution from the \vc7 folder
4. In VS, Build->Build Torque Demo
I've also tried loading the VC++ DSW workspace file but receive similar errors.
I CAN compile successfully with VC++ 6.0 (VS 6 with SP5 and I run the VCVARS32.BAT from that folder plus the appropriate .REG file from Torque) .
I've tried removing the ".h" from the include to remove the first error and prefix some of the objects with stdext:: (I think) to try and correct things, but I still get a ton of errors.
NOTE: Between each subsequent build attempt, I delete my temp sdk folder and copy in the files so that I'm always starting fresh from the HEAD version of the code.
Since others don't seem be having any of these issues, I'm hoping I need to set something up differently in my environment. Any ideas?
Thanks,
Dan Jones
#2
From what I gather, VC++ .NET wants the include for iostream to NOT have the .h. Also, the objects need to be prefixed with std:: or stdext:: (I think). But those changes alone didn't help very much.
I should note, is the HEAD version still tagged "Release_1_1_2", as on this page? Seems quite out of date. I did use WinCVS to get the source and specified that tag, maybe it's too old?
-Dan Jones
10/10/2003 (9:56 pm)
Visual Studio 1.1, or .NET 2003. I meant version 1.1 of the Framework, but I'm using Visual Studio 2003 :)From what I gather, VC++ .NET wants the include for iostream to NOT have the .h. Also, the objects need to be prefixed with std:: or stdext:: (I think). But those changes alone didn't help very much.
I should note, is the HEAD version still tagged "Release_1_1_2", as on this page? Seems quite out of date. I did use WinCVS to get the source and specified that tag, maybe it's too old?
-Dan Jones
#3
I've used WinCVS again to get the HEAD version and it compiles fine now. I won't be eating up any more bandwidth for awhile :)
-Dan
10/10/2003 (11:03 pm)
Excuse me - I'm used to Visual Source Safe. I was assuming that HEAD meant the latest stable build and that by entering the tag "Release_1_1_2" I'd be getting the latest "HEAD" release.I've used WinCVS again to get the HEAD version and it compiles fine now. I won't be eating up any more bandwidth for awhile :)
-Dan
#4
10/13/2003 (11:31 pm)
Heheh... Glad you got things resolved :) 
Associate Kyle Carter