Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!pollux.usc.edu
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.windows.ms
Subject: 3.0 SDK problems
Message-ID: <26093@usc.edu>
Date: 23 Jul 90 04:03:16 GMT
Sender: news@usc.edu
Organization: Felsina Software, Los Angeles,
Lines: 34

I just got my 3.0 SDK upgrade yesterday, and these are the major problems
I found:

1. The INSTALL program fails when requested to copy the sample files.  When
I select that option, the program crashes while copying the bitmap/select.h
file.  The floppy light stays on; nothing gets copied and I have to reboot.
I had to copy the samples one by one. UGLY!

2. The INSTALL program does not create the proper libraries.  I asked the
program to create only the MEDIUM library with the MATH Emulator option.
In that case the MLIBCW.LIB was created, but no MLIBCEW.LIB appeared.

Only when I asked to create libraries for BOTH the emulation AND alternate
libraries, then both MLIBCEW.LIB and MLIBCAW.LIB were generated.

3.  The major problem is with the 5.10 linker.  It just plain doesn't
work.  It doesn't seem to be able to pick up ANY of the Windows library
symbols and tells me that all the ones I use (174) are undefined, and
then aborts.

I tried to use LINK4, and that one works just fine.  The linker that came
with Microsoft C 5.10 comes up and says "Overlay Linker V. 3.65".

Note that I made all the appropriate changes to the .INF file (add the EXETYPE
directive), and use the "recommended" compiler line:

CL -c -AM -Gsw -Os -Zpe fname.c

Has anybody gotten the 5.10 Linker to work with the 3.0 SDK?

-- Marco
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=