You're not forced to make a Makefile... you can compile from the command line if you know what you are doing.
For example, a command-line compile and linking can look like this:
Quote:
MKDIR Release
CD Release
CALL "C:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32.BAT"
CL.EXE /nologo /MT /W3 /GX /O2 /I "..\..\metamod" /I "..\..\..\devtools\sdk\Single-Player Source\dlls" /I "..\..\..\devtools\sdk\Single-Player Source\common" /I "..\..\..\devtools\sdk\Single-Player Source\engine" /I "C:\Some\Other\Include\Path" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "yourproject_EXPORTS" /YX /FD /c ..\yourproject_file1.cpp
REM add other CL.EXE lines for each .cpp file to compile
LINK.EXE kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /dll /machine:I386 /def:"..\yourproject.def" yourproject_file1.obj yourproject_file2.obj yourproject_fileN.obj
ECHO.build complete
CD ..
|