Visual C++ Compile Errors
by Matt Fairfax · in Torque Game Engine · 08/09/2001 (9:14 am) · 50 replies
Error:
Solution:
The registry entries needed to make Visual C++ compatble with the .cc file extension haven't been added. Browse to the /v12/vc++ folder and Double click on "VC6 .cc compiling.reg" to add it to your registry. You will also want to add "VC6 .cc editing.reg" to your registry so that the .cc files will be syntax colored like a normal C++ file.
Quote:
--------------------Configuration: v12 Engine - Win32 Debug--------------------
Performing Custom Build Step on .\math\mMathSSE_ASM.asm
Performing Custom Build Step on .\math\mMathAMD_ASM.asm
Performing Custom Build Step on .\math\mMath_ASM.asm
Performing Custom Build Step on .\interior\itfdump.asm
Linking...
itfdump.obj : error LNK2001: unresolved external symbol _texGen0
itfdump.obj : error LNK2001: unresolved external symbol _texGen1
itfdump.obj : error LNK2001: unresolved external symbol _fogCoordinatePointer
LINK : error LNK2001: unresolved external symbol _mainCRTStartup
out.VC6.DEBUG/v12Test_DEBUG.exe : fatal error LNK1120: 4 unresolved externals
Error executing link.exe.
v12Test_DEBUG.exe - 5 error(s), 0 warning(s)
Solution:
The registry entries needed to make Visual C++ compatble with the .cc file extension haven't been added. Browse to the /v12/vc++ folder and Double click on "VC6 .cc compiling.reg" to add it to your registry. You will also want to add "VC6 .cc editing.reg" to your registry so that the .cc files will be syntax colored like a normal C++ file.
About the author
I am a Game Designer at PopCap who has worked on PvZ Adventures, PvZ2, Peggle Blast, and Bejeweled Skies. I am an ex-GarageGames employee who helped ship TGE, TGEA, Torque 3D, and Constructor.
#2
08/09/2001 (9:42 pm)
Hey guys this probably isn't the place for this but i need help, not with the v12 yet but with getting viual c++ to work. You see it keeps giving me the error spawning cl.exe and i found out it is because i don't have the file called mspdb60.dll. Can anyone here help me?
#3
08/09/2001 (10:48 pm)
What Service Pack do you have installed? You need Service Pack 5.
#5
08/09/2001 (11:03 pm)
Not sure but it most likely will...I've never tried compiling without a service pack installed so I haven't seen that exact error. You will definitely need Service Pack 5 though.
#6
08/09/2001 (11:05 pm)
I am currently downloading the service pack now and hopefully waiting for it to finsih...Thanks Matt.
#8
Solution:
You need to install Nasm in order to compile assembly files. Please refer to the Install docs for directions onhow to install Nasm.
08/10/2001 (12:39 am)
Error:Quote:
Performing Custom Build Step on .\interior\itfdump.asm
Linking...
LINK : fatal error LNK1104: cannot open file ".\out.VC6.DEBUG\interior\itfdump.obj"
Error executing link.exe.
Solution:
You need to install Nasm in order to compile assembly files. Please refer to the Install docs for directions onhow to install Nasm.
#9
--------------------Configuration: v12 Engine - Win32 Debug--------------------
Performing Custom Build Step on .\math\mMathSSE_ASM.asm
Bad command or file name
Performing Custom Build Step on .\math\mMathAMD_ASM.asm
Bad command or file name
Performing Custom Build Step on .\math\mMath_ASM.asm
Bad command or file name
Performing Custom Build Step on .\interior\itfdump.asm
Bad command or file name
I have Nasm installed. My VC++ tools->options->directories has the Nasm directory list. VC++ has service pack 5 installed. The ".cc" files seems to compile alright; it's only barfing on the ".asm" files.
08/10/2001 (7:41 pm)
Deleting intermediate files and output files for project 'v12 Engine - Win32 Debug'.--------------------Configuration: v12 Engine - Win32 Debug--------------------
Performing Custom Build Step on .\math\mMathSSE_ASM.asm
Bad command or file name
Performing Custom Build Step on .\math\mMathAMD_ASM.asm
Bad command or file name
Performing Custom Build Step on .\math\mMath_ASM.asm
Bad command or file name
Performing Custom Build Step on .\interior\itfdump.asm
Bad command or file name
I have Nasm installed. My VC++ tools->options->directories has the Nasm directory list. VC++ has service pack 5 installed. The ".cc" files seems to compile alright; it's only barfing on the ".asm" files.
#10
08/10/2001 (8:10 pm)
Make sure that Nasm is in your path...VC++'s Directories doesn't always work right.
#11
Before I installed Nasm, I was getting a "bad command or filename" message. Now with Nasm installed, VC++ is crashing when it tries to assemble the first file.
08/10/2001 (8:25 pm)
VC++ is now crashing.Quote:
--------------------Configuration: v12 Engine Lib - Win32 Debug--------------------
Performing Custom Build Step on .\math\mMathSSE_ASM.asm
Before I installed Nasm, I was getting a "bad command or filename" message. Now with Nasm installed, VC++ is crashing when it tries to assemble the first file.
#12
Did you follow all of the steps in the installation and setup guide? Stuff about adding it to your compile exe list or something.
08/10/2001 (8:38 pm)
Try downloading and installing nasm again. You may have gotten a corrupt file, or some of the file may have been lost while downloading. Just a suggestion. Did you follow all of the steps in the installation and setup guide? Stuff about adding it to your compile exe list or something.
#14
What should I do next?
08/10/2001 (9:18 pm)
Each time I try the build, VC++ crashes. I have to kill the vcspawn task to regain control of VC++. After that, the system becomes unstable and runs out of memory. I have to cold boot. This didn't happen before I installed Nasm (twice) version 0.98.What should I do next?
#15
08/10/2001 (11:31 pm)
What happens when you drop to a command line and just type in nasmw.exe?
#16
08/11/2001 (6:08 am)
I just extracted the nasm archive (all of the files) to c:\windows\command. c:\windows\command is (by default) always in the PATH.
#17
C:\WINDOWS>nasmw
nasm: no input file specified
type 'nasm -h' for help
C:\WINDOWS>
08/11/2001 (7:17 am)
From the DOS prompt:C:\WINDOWS>nasmw
nasm: no input file specified
type 'nasm -h' for help
C:\WINDOWS>
#18
PATH=C:\Programming\Nasm;C:\GNU\make\make-3.79.1\WinRel;C:\PERL\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\Dignus\;C:\Tachyon;C:\Tcl\bin\;C:\Program Files\GNU\WinCvs1.2;C:\Program Files\Microsoft Visual Studio\VC98\Bin
C:\WINDOWS>
08/11/2001 (7:19 am)
C:\WINDOWS>pathPATH=C:\Programming\Nasm;C:\GNU\make\make-3.79.1\WinRel;C:\PERL\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\Dignus\;C:\Tachyon;C:\Tcl\bin\;C:\Program Files\GNU\WinCvs1.2;C:\Program Files\Microsoft Visual Studio\VC98\Bin
C:\WINDOWS>
#19
Should we add the "cs" extension as well as the "cc"?
08/11/2001 (9:53 am)
Just a quick question on the first message of the topic...Should we add the "cs" extension as well as the "cc"?
#20
08/11/2001 (11:44 am)
No, the .cs files are script files in the example/ directory. They are used by the engine itself, not VC++. There is no need to add that extension too. 
Associate Matt Fairfax
PopCap
Soultion:
You haven't compiled the support libraries that the engine and tools link to. The support libraries need to be built before the engine or the tools. Browse to /v12/libs and open Libraries.dsw. Do a Build->Batch Build to build all of the needed support libraries. If you are building the engine or tools in the Debug configurtion, you need to build the support libraries in the Debug configuration. If you are building the engine or tools in the Release configuration, you need to build the support libraries in the Release configuration.