Getting Torque to compile with VS6

#1 I'm not a programmer, but I'm sure you need service pack 5 from Microsofts website. Its mentioned in the documentation.

Hope that helps

-=::=-

#2 Thanks for the reply, I wish it was that. :)

I have installed..and reinstalled both the VS6 and the service pack 5.
As well as openAL and DirectX8.1

The workspace file contains all the correct data or so it seemes, when I open it in notepad.

I tried on another computer with the same VS6 edition, but same thing there...

I have no clue what it could be?

-Bendik

#3 It's in the VC6 Setup Documentation about 2/3 of the way down. Search for 'cc_comp.reg'

--Rick

#4 not that either. I ran both of the .reg files.
I even used regedit to check that it was added to the registery. That part shoudl be right too.


*scratches head*

#5 What is very important is to reboot the computer after executing the two .reg files. More over, VC6 will never recognize the cc file as C++ file but you will be able to edit them with syntax color enabled.

BTW, Visual .NET has not that problem.

#6 You'll at least have to restart VC6. ...but with windows who knows a reboot is never a bad idea.

#7 Rick, it is important to reboot the computer if under Win ME or 98. On XP, the registry is well updated but on Me or 98, it seems it does not work well (I have to did it on my laptop).

#8 I have rebooted, reinstalled, updated, edited the registry, rebooted, and tried it all over again...
...and again. (Running MSVS6-enteprise@win2k)

The 'Torque SDK.dsw' file just won't open the right way.
(but looks all fine in a text editor)

I just tried on another computer with VS6-pro on and its the same thing....

Could it be somthing wrong with the files I have downloaded?

Shall I get some other programming tool?

Can I rename all the .cc files to .cpp ?

#9 ...now I am getting a little confused.

So it the TorqueSDK.dsw that doesn't open, you have not even tried to compile yet then? If that is the case I would delete the *.dsw, *.dsp files in the torque/vc6 direcory and update them from cvs.

--Rick

#10 I've seen a problem like yours (file looks ok in some text editors but VS won't parse it) when the file had suffered an extraneous Nl/CRNL conversion.

In WinCVS there is an option under "Global options" for Check-Out that says "Check out files with Unix LF (0x0a)". I have that option UNchecked, but then I never update the sources directly from GG, so your mileage may vary. Try it both ways.

#11 ive had this Exact issue when first submitting this project to my cvs server in linux and then doing a full checkout from windows..

resolved it to nuke the whole vs6 folder and resubmit as binary ..
linux cvs thinks its ok to modify these files ..
when it is not
so nuke the folder vs6 and get it again..
you are using wincvs on the machine that downloads these files from gg and then running on that machine right?
I dont understand how you got this to happen if that is the case

#12 Hurray!
Downloading it all again did wonders!!
Thanks for the help!!

*bows*
-Bendik