Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C1129AF.95B70B97@ece.gatech.edu>
Date: Fri, 07 Dec 2001 15:42:23 -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: Stephano Mariani <sk DOT cygml AT btinternet DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Autotools
References: <001801c17f50$7dff0220$6c00a8c0 AT sknet01>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)

Stephano Mariani wrote:
> 
> With the release of the new autotools build system I was under the
> impression that with libtool, automake supported building dlls under cygwin.

wrong impression.  It isn't ready yet.  Automake and autoconf are fine,
but I haven't finished the system libtool changes necessary, yet.

> I seem not to be able to do this, no dlls are produced and
> despite --disable-static, I get .a & .la. I am able to build dlls manually
> perfectly, and yet cannot do this using with automake??

libtool is a strange beast.  Ordinarily, libtoolized packages create
their own copy of libtool during the configure process, and it is based
on the version of libtool that was used by the upstream maintainers to
'libtoolize' it.  *Ordinarily*, you don't even USE the system libtool.

ONCE cygwin has a working system libtool, then you still need to do the
following (for each package that you want to build DLLs from):
  a) delete a number of files in the source tree
  b) run the system libtoolize script to 're-libtoolize' the package
using cygwin's version
  c) THEN configure and build as normal

Long term, it is hoped that the cygwin-specific changes to libtool will
get pushed into the REAL libtool, and then we can start pestering the
maintainers of various packages (not the cygwin package maintainers, but
those guys higher up the foodchain) to relibtoolize using the (then)
current libtool.

At that point, then, stuff will dllize OOB on cygwin.

But we ain't there yet.  We ain't even close.

--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/