Xref: utzoo comp.sys.ibm.pc:23621 comp.lang.c:15728
Path: utzoo!utgpu!watmath!watdragon!violet!jjboritz
From: jjboritz@violet.waterloo.edu (Jim Boritz)
Newsgroups: comp.sys.ibm.pc,comp.lang.c
Subject: Re: Looking for Microsoft Windows developer's library
Message-ID: <10974@watdragon.waterloo.edu>
Date: 24 Jan 89 06:39:49 GMT
References: <3408@sdsu.UUCP> <2732@rti.UUCP>
Sender: daemon@watdragon.waterloo.edu
Reply-To: jjboritz@violet.waterloo.edu (Jim Boritz)
Organization: U. of Waterloo, Ontario
Lines: 21

In article <2732@rti.UUCP> bcw@rti.UUCP (Bruce Wright) writes:
>Probably the most essential component is the linker --
>Windows programs use a different format of .EXE file (similar to an OS/2
>.EXE file), so you can't just use the DOS linker!!

Actually the latest version of the linker which comes with C5.1 will produce
executables that will run under Windows.  

One of the most important things that comes with the Windows Software
Development Kit is the resource compiler.  This is the thing that takes
icons, menus, dialog boxes, and the like and stores them as part of the
executable.   Among the tools like an icon editor and a dialog box
editor, the latest version of the kit comes with Codeview for Windows.

Considering what you get, and the amount of time it would take you to
recreate even the minimal elements that would be necessary, I think that 
your money would be well spent.  
--

    Jim Boritz			{uunet,utai,clyde}!watmath!violet!jjboritz  
    University of Waterloo	jjboritz@violet.waterloo.edu