Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3BF3F9D7.23674166@ece.gatech.edu>
Date:	Thu, 15 Nov 2001 12:22:31 -0500
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Mailer:	Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language:	en
MIME-Version:	1.0
To:	David Westbury <David DOT Westbury AT ipaper DOT com>
CC:	cygwin AT cygwin DOT com
Subject:	Re: Linking to commercial dll's
References:	<OF8B6193A7 DOT B4A10832-ON85256AFF DOT 004E05C7 AT ipaper DOT com>
X-Virus-Scanned:	by amavisd-milter (http://amavis.org/)

David Westbury wrote:

> 
> Dll's seem to be an especially difficult subject in cygwin, requiring
> detailed knowlege of the MS way of doing things.

Unfortunately, yes.

> Are dll's not
> standardized? 

Unfortunately, no.

> Is a "cookbook" approach to dll linking not possible? 

Not yet.  Soon this will be possible, but not quite yet (we're still
waiting for the final piece, libtool-with-autoimport-support).  Work is
progressing.

> The
> issue seems to be a steep hill for an average working programmer, like
me,
> to climb. 

Yep.  I'm afraid that right now, you must actually learn some new
stuff.  Eventually it will be turnkey, but not yet.

See http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/dll-stuff 

--Chuck

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -