Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!kth!draken!tut!santra!saha.hut.fi!s33957e
From: s33957e@saha.hut.fi (Petri Kalervo Havanto)
Newsgroups: comp.windows.ms
Subject: Trouble with DLL-libs
Summary: Linker seems to forget them
Keywords: DLL link4 no-go
Message-ID: <23614@santra.UUCP>
Date: 13 Jul 89 09:27:34 GMT
Sender: news@santra.UUCP
Reply-To: s33957e@saha.hut.fi.UUCP (Petri Kalervo Havanto)
Organization: Helsinki University of Technology, Finland
Lines: 24


	I am having some trouble with DLL-libraries. Though they are 
seemingly properly defined, my link4 doesn't find the functions in them,
it acts exactly as if the name of the importlibrary wasn'n on commandline.

The LIBRARY-statement in DEF-file is okay, I think the EXPORT-statements
are OK as well, but about them I am really not that sure, anyway,
the implib has noting to complain, and the names of exported functions
are in the 'stublibrary'. Now some questions arise:

	How does one make it clear to the linker that should read
an importlibrary? Is there maybe something wrong with the DEF-files
(either library's or the program's that is to be linked)

	Then when (if) I finally succeed in linking, where does
the system look for the actual library?

	I had a couple of other questions too, but let's leave them
to another time...

--
Petri Havanto

s33957e@saha.hut.fi.UUCP