Galaxy_Stranger wrote:what's NASM?
Ouch!
Seriously, NASM is the Netwide Assembler, a freeware assembler distributed under the LGPL. You can, IIRC, compile both ZDoom and GZDoom without any assembler code, but the C routines that are then used instead are of course slower.
The NASM site is down at the moment (
http://nasm.sourceforge.net), so I have put a copy of the latest version at
http://www.martinsobservationpost.net/system/nasm.zip for the moment.
Once you have extracted the archive and moved the resulting folder to wherever you want it, put the pathname of the folder in your path, as makefiles for various command-line compilers will be expecting it.
To do this
1. Start|Run and then put
regedit in the open field of the dialog. Click
OK.
2. Use the left-hand pane of regedit to navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
3. In the right-hand pane, double-click
Path
4. Use the END key to go to the right-hand side of the string;
5. Add a semicolon, followed immediately by the full pathname of the folder in which NASM resides; for example, change
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem.
to
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\documents and settings\galaxy_stranger\my documents\nasm.
Case is not important, but do NOT use quotes!
6. Click
OK. If anything unexpected happens during this process, click
Cancel instead of
OK and try again. Messing around with the PATH setting can mess up a system BIG TIME if you do it wrong; it's about time MS had a proper GUI path-editing utility with safeguards and stuff.
7. You don't need to restart the system, but you do need to log off then log back on again.
If you are ONLY compiling from within the MSVC IDE, then you don't need to add it to the PATH.
You then need to use the Tools|Options|Projects page, select
VC++ directories and then select
Platform as
Win32 and
Show directories for as
Executable files. ("Directory" is the technical word for "folder"; old-timers like me still use it, and it seems MS do as well, at least in their development products). Click the "new folder" icon and browse to the same directory where NASM is. When you are there you won't be able to see any files (though you will see subfolders), but the folder name (e.g.,
nasm) will appear in the
Look in field of the dialog. Click
Open then
OK.
Then try rebuilding it. If it doesn't work, sacrifice a couple of imps to Baal and ask for the slow and painful death of Bill Gates
