cofused about CVS
by Anthony Rosenbaum · in Torque Game Engine · 10/18/2001 (2:05 pm) · 7 replies
are we suppost ot install it over the previous v12 folder? if now why arn't their workspaces in the torque folder? Anthony
About the author
#2
10/18/2001 (2:57 pm)
If you download the latest release from CVS you should not put it into the same folder as the old v12.
#3
10/18/2001 (4:24 pm)
do you only build the torque sdk.dsw instead of doing lib then engine and then tools?
#4
10/18/2001 (5:27 pm)
The torque_SDK.dsw builds the entire project including the libraries. Use Batch Build and the Rebuild All button to build the entire project.
#5
LINK : fatal error LNK1104: cannot open file "\torque\engine\out.VC6.DEBUG\itfdump.obj"
Error executing link.exe.
torqueDemo_DEBUG.exe - 1 error(s), 15 warning(s) and no exe is made
any clues?
10/19/2001 (7:38 am)
when I do that I get Linking...LINK : fatal error LNK1104: cannot open file "\torque\engine\out.VC6.DEBUG\itfdump.obj"
Error executing link.exe.
torqueDemo_DEBUG.exe - 1 error(s), 15 warning(s) and no exe is made
any clues?
#6
If you right click each of them they will build and you can copy those object files to the directory it is looking in. Then rebuild and it will work.
I know I left somehting out when I did it because it should copy the objs to the correct because it should copy them for you. Anyone know where this part is?
10/19/2001 (8:01 am)
I had this problem last night. Look for the assembly files in the project. Right click each of them and change the path for nasmw. Just chop off the path and let it begin with nasmw.If you right click each of them they will build and you can copy those object files to the directory it is looking in. Then rebuild and it will work.
I know I left somehting out when I did it because it should copy the objs to the correct because it should copy them for you. Anyone know where this part is?
#7
You can update by doing the checkout using the the "Dev_Stable" tag into the same directory as last time. WinCVS should just update that directory to the latest.
10/19/2001 (8:26 am)
The "Dev_Stable" version of the SDK checked into CVS has a fix for the nasm thing. I'm not sure it fixes it for everyone, but you might want to try that. It's easier than messing with the VC6 settings :)You can update by doing the checkout using the the "Dev_Stable" tag into the same directory as last time. WinCVS should just update that directory to the latest.
Torque Owner Karsten "Clocks" Viese
// Clocks out