Path: utzoo!attcan!uunet!decwrl!sdd.hp.com!cs.utexas.edu!ut-emx!linus!sjsca4!poffen
From: poffen@sj.ate.slb.com (Russ Poffenberger)
Newsgroups: comp.windows.ms
Subject: Re: Linking Problem with SDK 3.0 Sample Codes
Message-ID: <1990Jul31.190737.20947@sj.ate.slb.com>
Date: 31 Jul 90 19:07:37 GMT
References: <1990Jul31.033448.8929@watserv1.waterloo.edu>
Reply-To: poffen@sj.ate.slb.com (Russ Poffenberger)
Organization: Schlumberger Technologies, San Jose, CA.
Lines: 19

In article <1990Jul31.033448.8929@watserv1.waterloo.edu> batman@watsci.uwaterloo.ca (Marcell Stoer) writes:
>When linking the generic sample codes that came with SDK 3.0
>with link v3.65 (the one that comes with Microsoft Compiler v5.1),
>got unresolved externals error.  The unresolved functions are the
>ones in c:\windev\lib\libw.lib.  The LIB environment variable is
>set to c:\windev\lib;c:cl\lib.
>Can anybody help me?


As has been stated here recently, there are TWO linkers on the MSC 5.1 disks.
You need the other one. The installation should have copied it as "link4".

Note that the MSC 6.0 distribution only has one linker, the correct one.


Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254