Compiling Latest...
by Joe Melton · in Torque Game Engine · 10/19/2003 (11:28 pm) · 6 replies
I am having trouble compiling the latest release, as well as the latest HEAD. I am using Visual Studio .NET, version 7.0.9466. When I choose the VC7 project, VS tells me it can't be opened because it's for version 7.10. Is 7.10 the same as VS.NET 2003? If so, does this mean I will need to build from the VS6 project, because someone inadvertently updated the VC7 project to VS.NET 2003? Any help would be appreciated. Thanks.
#2
In older release, you had a torque/bin/nasm directory with Nasm.
And the custom settintg were :
"$(WkspDir)\..\bin\nasm\nasmw.exe" -f win32 $(InputPath) -o "$(IntDir)/$(InputName).obj"
Now, there is no more bin directory, and the setting is :
nasmw.exe -f win32 $(InputPath) -o $(IntDir)/$(InputName).obj
So you must have Nasm somewhere on your disk, and the Nasm directory must be in your default path in order to Visual to find Nasm...
Hope it helps,
PS : It was easier when nasm was included in the project, so we could compile torque 'out of the box'
10/20/2003 (4:27 am)
Nasm is no more included in the latest release.In older release, you had a torque/bin/nasm directory with Nasm.
And the custom settintg were :
"$(WkspDir)\..\bin\nasm\nasmw.exe" -f win32 $(InputPath) -o "$(IntDir)/$(InputName).obj"
Now, there is no more bin directory, and the setting is :
nasmw.exe -f win32 $(InputPath) -o $(IntDir)/$(InputName).obj
So you must have Nasm somewhere on your disk, and the Nasm directory must be in your default path in order to Visual to find Nasm...
Hope it helps,
PS : It was easier when nasm was included in the project, so we could compile torque 'out of the box'
#3
10/20/2003 (8:13 am)
Thanks for your help. I'll try to make it work tonight.
#4
So, VC7.0 users should import the VC6 workspaces. This process should work fine though, or at least I've never had a problem.
You might try checking to see if the engine is pointing the .ASM files to NASM correctly, if at all.
10/20/2003 (8:43 am)
GarageGames is no longer keeping VC7.0 (.NET 2002) workspaces. They have all been updated to be VC7.10 (.NET 2003) workspaces instead.So, VC7.0 users should import the VC6 workspaces. This process should work fine though, or at least I've never had a problem.
You might try checking to see if the engine is pointing the .ASM files to NASM correctly, if at all.
#5
.NET -> .NET 2003 = more $$, right?
10/21/2003 (12:22 am)
Great. I'll work on that NASM thing, and hopefully I'll be able to build it. Thanks for the prior warning guys, both for the workspace version and for the NASM problem. =D.NET -> .NET 2003 = more $$, right?
#6
The only problem I found is that you will have to redo the custom build settings.
10/21/2003 (12:52 am)
You can convert the .NET 2003 project files to .NET 2002 files if you use a text editor.The only problem I found is that you will have to redo the custom build settings.
Torque Owner Joe Melton
Fails At Making Games
Torque Demo error PRJ0019: A tool returned an error code: "Performing Custom Build Step"
I haven't had any trouble compiling before. However, this is a brand new computer I built last weekend, so maybe I missed someting on the VS.NET configuration...?