Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3B2ED2B9.EBB6FEE7@petig-baender.de>
Date: Tue, 19 Jun 2001 06:19:05 +0200
From: Christof Petig <christof@petig-baender.de>
Organization: Adolf Petig GmbH & Co. KG
MIME-Version: 1.0
To: Robert Collins <robert.collins@itdomain.com.au>
CC: Cygwin <cygwin@cygwin.com>
Subject: Re: Which version of Libtool to use? (or is libtool impossible)
References: <3B2A27C8.8165AAB@petig-baender.de> <015001c0f5b7$581b7a70$0200a8c0@lifelesswks>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Robert Collins wrote:

> This is an application porting question: Try searching the cygwin-apps
> archives for libtool and/or ld. There have been threads relevant to both
> recently. In particular there is an experimental libtool && binutils I
> have colated which may be of interest. These deperately need informed
> testing.

Thank you for this link. I'll test it.

> Also covering glib: you need to port it. It's trying to compile for
> win32, not cygwin, and it's not configured to support libtool .dll
> creation. Ditto for iconv. See the libtool manual for information on
> that.

Did I get you right that the e.g. the inclusion of -luser32 prevents you
from building a cygwin dll? If so it seems that I'm stuck with mingw for
library creation and runtime (which has already proven to be a tough path).
I have to build gtk+ which definitely needs win32.

Christof


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple