Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3BF3F9D7.23674166@ece.gatech.edu> Date: Thu, 15 Nov 2001 12:22:31 -0500 From: Charles Wilson X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: David Westbury CC: cygwin@cygwin.com Subject: Re: Linking to commercial dll's References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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/