delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1999/11/18/14:33:50

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <01BF3268.51882E10@p188-tnt6.akl.ihug.co.nz>
From: Eliot Muir <eliot DOT muir AT interfaceware DOT com>
To: "'Charles Krug Jr.'" <charles AT pentek DOT com>,
"cygwin AT sourceware DOT cygnus DOT com" <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: Trouble linking against vendor supplied DLL.
Date: Fri, 19 Nov 1999 08:30:20 +1300
Encoding: 62 TEXT

Not surprising - the import library is specific to the compiler
- in fact VC5 chokes on VC6's import libraries.

I'm not exactly sure how you would begin to export dll symbols
for gcc under cygwin.  

One possible option is to use the dumpbin 
utility from VC to find out the export functions in the DLL and
then use LoadLibrary etc. to manually load the DLL and find
the function addresses etc. to manipulate it.

Cheers,
Eliot 

--
Eliot Muir, Technical Director                 iNTERFACEWARE
mailto:eliot DOT muir AT interfaceware DOT com  
Voice 64-21-333068      http://www.interfaceware.com

Makers of iNTERFACEWARE Chameleon 
   "Program to the iNTERFACE not the implementation"

-----Original Message-----
From:	Charles Krug Jr. [SMTP:charles AT pentek DOT com]
Sent:	Friday, November 19, 1999 6:22 AM
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Trouble linking against vendor supplied DLL.

Hello List:

I'm building a program and trying to link against a vendor supplied .dll
using their .lib file.  The code in question has successfully been built
under VC.  I'm now attempting to build under cygwin.

This is supposed to be a Win32 console application.

Using this command:

gcc -Wall -omyapp.exe mysource.c c:/universe/lib/universe.lib

This results in myapp.exe being built.

Then I run myapp, and get a Win GUI message box:

"The procedure entry point could not be located in the dynamic link
library universe.dll"

I'm thinking either I gave incorrect arguments to gcc or that I have
some installation issue with the dll.  The absence of any procedure name
in the message box makes me suspect arguments for some reason.

Anyone have any experience with this that could shed some light?

Thanx


Charles

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019