libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool shouldn't switch to creating static library if it can't crea


From: Vadim Zeitlin
Subject: Re: libtool shouldn't switch to creating static library if it can't create the shared one under Windows
Date: Tue, 21 Jun 2011 12:29:37 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Charles Wilson <libtool <at> cwilson.fastmail.fm> writes:

> >  A more interesting question is if the current situation with libtool can
> > be improved because I continue to believe that getting a static library
> > when you're trying to build a shared one can be very unexpected. And this
> > can be the case even under Unix where there would be presumably too much
> > resistance to change the way --disable-static works if it is controversial
> > even under Windows where I thought it would be "obviously correct".
> > 
> >  So it seems the only solution with any chance of acceptance would be to
> > add a different option doing what I want, e.g. --enable-shared-only. Or
> > maybe allow --enable-shared=(yes|no|only)?
> 
> No, I think --disable-static, if specified, should actually *disable
> static*.  That should be sufficient.
> 
> If it's not doing that, then it's a bug IMO.

 Just to confirm: no, currently it doesn't do this. The example of my
original message came from libxml2 build configured with --disable-static.

 So should I try to create a patch making libtool fail in this case?

 Thanks,
VZ





reply via email to

[Prev in Thread] Current Thread [Next in Thread]