Re: exclusive static or shared

[Christopher Hulbert]

Ok, I sent the patch to libtool-patch.

Another question I have wondered is as follows:

Lets say I build library liba as both static and shared (thus I have
liba.a and liba.so or liba.lib and liba.dll).  I later want to build
libb.so or libb.dll against the installed liba.  From my observations
it always takes the shared liba.  Is this true, or is there a flag to
tell it to use static libraries where available (similar to -i-static
for intel compiler).

I was thinking something like -libtool-static or
-libtool-static=-la,-lxyz where the comma-separated list is a list of
libraries this rule applies to.  Any thoughts on the matter?

On 2/15/06, Ralf Wildenhues <address@hidden> wrote:
> [ off-list ]
>
> Hi Christopher,
>
> * Christopher Hulbert wrote on Wed, Feb 15, 2006 at 02:24:10PM CET:
> > On 2/15/06, Ralf Wildenhues <address@hidden> wrote:
> > >
> > > Well, some of the issues arise from the first MSVC patches: a couple of
> > > times there was the assumption that on win32, non-gcc compiler meant
> > > MSVC.  You'd need to undo that.  And then go and set the flags in
> > > _LT_COMPILER_PIC correctly (for both CXX and other tags).  And then you
> > > can check all the other PORTME instances in libtool.m4 to see whether
> > > they need adaptation, too.  ;-)