I'm pretty new to C, and very new to building things on Win32. Can
anybody point me at some resources that will get me up to speed on
what different file types are and the basics of linking various object
files together into libraries, etc? I'm using the compiler that comes
with Visual Studio 6 from the command line (cl.exe).

Thanks very much.

--
Graham

P.S. I'm currently trying to use cl.exe to compile a .c and .h file
into a library that I can then persuade it to link to when building
another library from a .c file. To give you some idea of how little I
know about it, I'm stuck with:

C:\Program Files\Microsoft Visual Studio\VC98\BIN\cl.exe /c /nologo
/Ox /MD /W3
/GX "-Ic:\program files\python\Include" /TcCISprocess.c
/Fobuild\temp.win32-1.5\Release\CISprocess.obj CISprocess.c C:\Program
Files\Microsoft Visual Studio\VC98\BIN\link.exe /DLL /nologo
/INCREMENTAL:NO "/LIBPATH:c:\program files\python\libs"
/EXPORT:initCISprocess build\temp.win32-1.5\Release\CISprocess.obj
/OUT:build\lib.win32-1.5\CISprocess.pyd
/IMPLIB:build\temp.win32-1.5\Release\CISprocess.lib
Creating library build\temp.win32-1.5\Release\CISprocess.lib and
object build
\temp.win32-1.5\Release\CISprocess.exp
CISprocess.obj : error LNK2001: unresolved external symbol

build\lib.win32-1.5\CISprocess.pyd : fatal error LNK1120: 1 unresolved
externals

.c   ---- C file
.obj ---- object file
.lib ---- library file
.exe ---- executable file

To link various object files together into a library, use the LIB
command (unless MS have changed this recently, which they may have done,
which is one reason why it's a better idea to ask this question in a
Windows programming newsgroup).

To link an existing library into your code (let's say it's called
mylib.lib), the following should be sufficient:

cl -Za -W4 myprog.c mylib.lib

In future, please try to ask platform-specific questions like this in
platform-specific newsgroups (e.g. comp.os.ms-windows.programmer.win32)
- comp.lang.c is for questions about the C language itself, not
Microsoft tools.

Thanks.

<snip>

Check your documentation as to where in the world is the offending
function "EnumProcs" and get it's library name and then simply add the
following to the "cl"  command line (or link options if you are
working in the IDE)

/defaultlib:libname

that should do. [Note: replace the "libname" with the name of the
library including it's extension]

That should do.