[Top][All Lists]

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

Re: (almost) silent creation of static lib instead of dynamic linked lib

From: Evgeny Grin
Subject: Re: (almost) silent creation of static lib instead of dynamic linked lib
Date: Fri, 18 Apr 2014 22:40:08 +0400

18.04.2014, 19:12, "Bob Friesenhahn" <address@hidden>:
> On Thu, 17 Apr 2014, Evgeny Grin wrote:
>>  Libtool always build static lib if dynamic lib can't be created.
>>  This behavior is inconsistent with other build tools. For example if GCC 
>> can't compile something, it fail with error.
>>  If I need a shared lib, this doesn't mean that static lib will satisfy me.
>>  When I run configure with "--enable-shared" (or shared enabled by default), 
>> I expect that "make" will build shared lib or fail with error.
> Did you try using --disable-static?  Enabling building shared
> libraries is not the same as disabling building static libraries.

Yes, with "--disable-static" libtool create only static lib if any depend lib 
is static.

But even with "--enable-static --enable-shared" I expect that libtool will fail 
in case that shared lib can't be created. 
GCC fail if it can't compile something, "make" fail if it can't build something 
(unless it explicitly instructed to ignore specific build error) and only 
libtool do not fail in case that something requested to be built can't be 
Why libtool think that static lib if enough for me if I configured to build a 
shared lib too?

Best Wishes,
Evgeny Grin

reply via email to

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