libtool option to build both static and shared?

2009-11-12 Thread Stepan Kasal
Hello, I'd like to ask you to help with the following problem: A project contains sources for several libraries. Most of them should be built as shared libraries only, but one of them is to be built both as a shared library and as a static one. The user would like to use

Re: libtool option to build both static and shared?

2009-11-12 Thread Bob Friesenhahn
On Thu, 12 Nov 2009, Stepan Kasal wrote: Is there an option that would tell libtool to build both, even though it was configured with --disable-static? I invented a solution that should work: configure with --enable-static and then use -shared in CFLAGS or AM_CFLAGS for all but libraries but

Re: libtool option to build both static and shared?

2009-11-12 Thread Stepan Kasal
Hello Bob, thank you for your answer. On Thu, Nov 12, 2009 at 10:50:03AM -0600, Bob Friesenhahn wrote: On Thu, 12 Nov 2009, Stepan Kasal wrote: Is there an option that would tell libtool to build both, even though it was configured with --disable-static? I invented a solution that should

Re: libtool option to build both static and shared?

2009-11-12 Thread Ralf Wildenhues
Hi Stepan, * Stepan Kasal wrote on Thu, Nov 12, 2009 at 05:11:00PM CET: A project contains sources for several libraries. Most of them should be built as shared libraries only, but one of them is to be built both as a shared library and as a static one. The user would like to use

Re: libtool option to build both static and shared?

2009-11-12 Thread Bob Friesenhahn
On Thu, 12 Nov 2009, Stepan Kasal wrote: This is the solution which currently does work, as long as the OS, tools, and libraries are capable of it. Note that using --disable-static is not portable so attempting to force only a shared build decreases portability. [...] I understand that