Game Development Community

Error Compiling first Build

by Robert Janes · in Torque Game Engine · 08/05/2003 (7:39 am) · 8 replies

Hey Guys

I have Visual C++ 6 and SP5 installed, and I ran the C:\Torque\vc6\VC6 .cc compiling.reg In . When I go to create the first TorqueDemo_DEBUG.exe I get this error

--------------------Configuration: Torque Demo - Win32 Debug--------------------
Performing Custom Build Step on ..\engine\terrain\blender_asm.asm
'C:\DOCUME~1\ROB' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.
Error executing c:\windows\system32\cmd.exe.

torqueDemo_DEBUG.exe - 1 error(s), 0 warning(s)

----------------


Anyone have any clue as to why im getting this error. I just reformatted my computer, I never got this error when I built the client last time (before reformat)

-Rob

#1
08/05/2003 (7:49 am)
Rob,

I quick guess would be that you are using directories with spaces in them (i.e. something like C:\Documents and Settings\ROB). You should attempt the compile using a shorter non-spaced directory (i.e. C:\Torque).

Rich
#2
08/05/2003 (7:53 am)
Thats weird because its all located in C:\Torque
#3
08/05/2003 (8:05 am)
You are correct, that is weird. I looked at the error: C:\DOCUME~1\ROB' is not recognized as an internal or external command and assumed incorrectly. You say that you ran the reg file, but have rebooted by chance? Even though the reg was updated on my Windows 2000 box, I had to reboot to get it to take effect.
#4
08/05/2003 (8:16 am)
'C:\DOCUME~1\ROB' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.
Error executing c:\windows\system32\cmd.exe.


I still dont get it, i rebooted like you suggested. I am using WinXP Home.

Im thinking it has something to do with
'C:\DOCUME~1\ROB'
or
Error executing c:\windows\system32\cmd.exe.

im not sure how to go about it

-Rob
#5
08/05/2003 (8:38 am)
It looks like it is having problems executing nasmw.exe. First thing to check is that the executable is present in Torque\bin\nasm. If it is there try to execute it from a command prompt (just to make sure the exe is not damaged). If that works, check the Custom Build in Visual Studio for the module blender_asm.asm. It should look like the below:
"$(WkspDir)\..\bin\nasm\nasmw.exe" -f win32 $(InputPath) -o "$(IntDir)/$(InputName).obj"
I have seen people who have had to wrap the $(InputPath) in quotes (see this thread).

Rich
#6
08/05/2003 (8:52 am)
I'll keep this in mind after i install VC6
#7
08/05/2003 (9:30 am)
Strangely, I just had this happen to me too. It's because it uses the workspace directory to get the path for nasm, and I use one top level workspace and add the Torque projects I need to that. So, if your VC6 workspace isnt in the vc6 directory, it wont work. The fix is easy:

Open up Torque SDK.dsp and Torque Lib.dsp in a text editor, and search and replace the following:

$(WkspDir)\..\bin\nasm\nasmw.exe

and change it to:

$(ProjDir)\..\bin\nasm\nasmw.exe

That should fix it. Unless you move your project too, but then it should be pretty obvious what to change :)

Tom.
#8
10/21/2004 (3:48 pm)
Hi! I just had the same problem and figured it out before coming here. Still, wouldn't it make more sense if those $(WkspDir) would be replace by $(ProjDir) in the official release so future users don't have to go through this? I mean the Torque Lib project will always be at the same place while the workspace that includes it can be anywhere. Just a suggestion.