Game Development Community

NASM problem

by Spel · in Torque Game Engine · 10/04/2002 (12:58 pm) · 20 replies

I have visual studio 6 installed with service pack 5, I also have nasm installed. I'm running windows 2000. When i try to compile i get an error: C:\Projects\code\vc6\..\bin\nasm\nasmw.exe"' is not recognized as an internal or external command,
operable program or batch file. I also made sure that the nasm files are in a directory that is listed under executable files in VC++. Any ideas what is causing this? Help would be greatly appreciated, thanks.
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Torque Owner John Quigley
#1
10/04/2002 (7:08 pm)
What version of the code are you running? Head? 1.1.2?

Torque Owner Todd Lucht
Human, Etc.
#2
10/04/2002 (8:46 pm)
I'm having this problem also. I am trying to compile on Windows 2k with VS 7.0. Any help would be appreciated.

Torque Owner Matthew Shapiro
#3
10/04/2002 (9:21 pm)
Just to speak on spel's behalf a little (I'm his teammate, I created the cvs etc...) and basiclaly it's the latest head as of 5 days ago. I separated all the code into a seperate code directory (engine, mk, lib, tools, vc6 and bin) so I don't know if this screwed it up somehow (though i doubt it.

--KallDrexx

Torque Owner John Quigley
#4
10/04/2002 (9:38 pm)
If you changed around the paths, that might have caused it to be unable to find nasm. Consider this line from Torque Demo.dsp:

"$(IntDir)/$(InputName).obj" : $(SOURCE) "$(INTDIR)" "$(OUTDIR)"
"$(WkspDir)\..\bin\nasm\nasmw.exe" -f win32 $(InputPath) -o "$(IntDir)/$(InputName).obj"

nasmw has to be in that exact spot.

Torque Owner Matthew Shapiro
#5
10/04/2002 (9:49 pm)
err explain to me what intdir and Wrkspce Dir are.. thanks :)

--KallDrexx

Torque Owner Matthew Shapiro
#6
10/04/2002 (9:51 pm)
ok i'm a moron, i think i accidentally deleted nasmw.exe as all thats' in code/bin/nasm/ is CVS readme and License =P

thanks :)

--KallDrexx

Torque Owner John Quigley
#7
10/04/2002 (9:51 pm)
The WkspDir is the directory where the dsp/dsw file lives. The intdir I think is just the intermediate output directory it probably isn't important for this problem.

Torque Owner John Quigley
#8
10/04/2002 (9:53 pm)
Todd, what's your setup? Is the problem fixed for you too?

Torque Owner Todd Lucht
Human, Etc.
#9
10/05/2002 (9:29 am)
Sorry I posted here, I was having a problem with the getting the NASM compiler working under VS 7.0 on Windows 2k. It seems that some of the Command line configurations need quotes around the input file in order for the files to get compiled correctly. Hope that helps someone.

Torque Owner John Quigley
#10
10/05/2002 (10:12 am)
Eh, so is your problem fixed? If not, what's the error message you're getting?

Torque Owner Todd Lucht
Human, Etc.
#11
10/05/2002 (6:01 pm)
Once I fixed the Command Line parameters (described above) I was able to get everything to compile. Thanks!

Torque Owner Jeroen Verbeek
#12
07/21/2003 (5:46 am)
I also had a problem with VC7 on XPPro, but in my case nasm was found and executed.
Custom builds using nasm where reporting "multiple input files", adding quotes around the $(InputPath) parameter fixed the problem.

"$(WkspDir)\..\bin\nasm\nasmw.exe" -f win32 "$(InputPath)" -o "$(IntDir)/$(InputName).obj"

Hope this is of help to other people.

Regards,
Jeroen.

Torque Owner Dreamer
Default Studio Name
#13
05/31/2004 (11:19 pm)
I am having the same problem as Jeroen...
Where did you fix this at?

Torque Owner Ronan Hayes
#14
06/02/2004 (2:37 am)
Im having a similar problem, I went through all the asm and told them where the custom build infor was no luck. At all, I'll keep at it and post if I sort it. But if anyone knows how to fix this I woudl really appreciate it.

"$(SolutionDir)\..\bin\nasm\nasmw.exe" -f win32 "$(InputPath)" -o "$(IntDir)/$(InputName).obj"

Im using a the most recent version of Torque. and Visual Studio .Net 2002

Associate Matt Fairfax
PopCap
#15
06/02/2004 (5:49 am)
Make sure you aren't trying to compile Torque out of a directory with a space in the name (like your Desktop).

Torque Owner Ronan Hayes
#16
06/03/2004 (1:28 am)
Completly new error now:

errir PROJ0019: A tool returned an error code: "Perf Torque demo

Now Im only trying to compile the torque demo. Any ideas.?

Torque Owner Ronan Hayes
#17
06/03/2004 (1:52 am)
Completly new error now:

errir PROJ0019: A tool returned an error code: "Perf Torque demo

Now Im only trying to compile the torque demo. Any ideas.?

Torque Owner Ronan Hayes
#18
06/03/2004 (2:28 am)
Completly new error now:

errir PROJ0019: A tool returned an error code: "Perf Torque demo

Now Im only trying to compile the torque demo. Any ideas.?

Torque Owner Sikosis
#19
12/13/2004 (6:45 pm)
I'd been having the same problem all weekend ... I wish I'd checked the forums sooner ... (eg. Make sure you aren't trying to compile Torque out of a directory with a space in the name)

I'll try this when I get home.

Torque Owner Sikosis
#20
12/13/2004 (11:19 pm)
After changing the path to non-spaced and under the 8 char limit as well just in case ... it seemed like it was working then ...

Linking...
Performing Custom Build Step
c:\Torque\src\Agent26\vc6\Agent26.vcproj:1: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:2: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:3: parser: instruction expected
c:\Torque\src\Agent26\vc6\Agent26.vcproj:4: parser: instruction expected
c:\Torque\src\Agent26\vc6\Agent26.vcproj:5: parser: instruction expected
c:\Torque\src\Agent26\vc6\Agent26.vcproj:6: parser: instruction expected
c:\Torque\src\Agent26\vc6\Agent26.vcproj:7: parser: instruction expected
c:\Torque\src\Agent26\vc6\Agent26.vcproj:8: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:9: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:10: symbol 'Name' redefined
c:\Torque\src\Agent26\vc6\Agent26.vcproj:10: parser: instruction expected
c:\Torque\src\Agent26\vc6\Agent26.vcproj:11: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:12: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:13: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:14: symbol 'Name' redefined
c:\Torque\src\Agent26\vc6\Agent26.vcproj:14: parser: instruction expected
c:\Torque\src\Agent26\vc6\Agent26.vcproj:15: parser: instruction expected
c:\Torque\src\Agent26\vc6\Agent26.vcproj:16: parser: instruction expected

...

c:\Torque\src\Agent26\vc6\Agent26.vcproj:2118: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:2119: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:2120: label or instruction expected at start of line
c:\Torque\src\Agent26\vc6\Agent26.vcproj:2121: label or instruction expected at start of line
Project : error PRJ0019: A tool returned an error code: "Performing Custom Build Step"

I'm using VS 2002 7.09466

I copied bin, engine, lib and vc6 to another directory (c:\Torque\src\Agent26\) then opened the Torque workspace, removed all the projects from the solution except Torque Demo, glu2d3d, ljpeg, lpng, lungif, opengl2d3d and zlib. I renamed Torque Demo to Agent26 and that's about it.

I originally followed wazooenterprises.com's TGE Tutorial 1 - however, every file wanted to have the include changed, so I tried the method above.

Basically, I've been mucking around with the scripting, that I now want to take the code and compile it with resources and start implementing the scripting I've done into C++ code and also add new features (or basic ones such as a Forcefield for the Mission Area)