Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@sourceware.cygnus.com>
List-Subscribe: <mailto:cygwin-subscribe@sourceware.cygnus.com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin@sourceware.cygnus.com>
List-Help: <mailto:cygwin-help@sourceware.cygnus.com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner@sourceware.cygnus.com
Delivered-To: mailing list cygwin@sourceware.cygnus.com
Reply-To: <ssiddiqi@nspm.ipass.net>
From: "Suhaib Siddiqi" <sssiddiqi@ipass.net>
To: "Eliot Muir" <eliot.muir@interfaceware.com>,
        "'Charles Krug Jr.'" <charles@pentek.com>,
        <cygwin@sourceware.cygnus.com>
Subject: RE: Trouble linking against vendor supplied DLL.
Date: Thu, 18 Nov 1999 14:33:04 -0500
Message-ID: <NDBBLHPPKKBKPBLLMFJBMEPHCEAA.sssiddiqi@ipass.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <01BF3268.51882E10@p188-tnt6.akl.ihug.co.nz>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal


Use dlltools and dllwrap to create libuniverse.a from vendor
supplied
universe.dll.  It is simple.  Search mail archive, you will 100s of
messages discussing dlltool and dllwrap.

Suhaib


> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Eliot Muir
> Sent: Thursday, November 18, 1999 2:30 PM
> To: 'Charles Krug Jr.'; cygwin@sourceware.cygnus.com
> Subject: RE: Trouble linking against vendor supplied DLL.
>
>
> 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.muir@interfaceware.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@pentek.com]
> Sent:	Friday, November 19, 1999 6:22 AM
> To:	cygwin@sourceware.cygnus.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@sourceware.cygnus.com
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com