[Top][All Lists]

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

Re: problem --enable-shared and --enable-static together

From: Ralf Wildenhues
Subject: Re: problem --enable-shared and --enable-static together
Date: Sat, 5 Dec 2009 13:33:06 +0100
User-agent: Mutt/1.5.20 (2009-10-28)

Hello Andreas,

besides answers already given:

* Andreas Otto wrote on Fri, Dec 04, 2009 at 09:41:16AM CET:
> as you see both *lo and *.o are created. the *.o are useless and just
> extend the compiling time

> Q: what can I do to avoid build static libraries ...

foo_LIBTOOLFLAGS = -tag=disable-static

for a target 'foo'.

> I use "../libmsgque/*.lo" for in-project libraray dependency to avoid to
> link to my own shared libraray

Sounds like you could profit from using convenience archives.

> 2. executables should build without library dependency. This mean that
> if configured with "--enable-static" the static object files should be used
> and if configureed without the shared object files should be used.

Link the program against the library with -static.

Hope that helps.


reply via email to

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