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:	<001201c17fd9$69222240$0900a8c0@sknet01>
From:	"Stephano Mariani" <sk DOT cygml AT btinternet DOT com>
To:	"Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc:	<cygwin AT cygwin DOT com>
References:	<001801c17f50$7dff0220$6c00a8c0 AT sknet01> <3C1129AF DOT 95B70B97 AT ece DOT gatech DOT edu>
Subject:	Re: Autotools
Date:	Sat, 8 Dec 2001 11:13:48 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

I managed to get the GNU build system to build shared libs on cygwin and
linux, albeit with a lot of hacks which I suspected automake would be clever
enough to do. I will soon test it on solaris.

Thanks for your help.

Stephano

----- Original Message -----
From: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
To: "Stephano Mariani" <sk DOT cygml AT btinternet DOT com>
Cc: <cygwin AT cygwin DOT com>
Sent: Friday, December 07, 2001 8:42 PM
Subject: Re: Autotools


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



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