Re: exclusive static or shared

2006-02-17 Thread Ralf Wildenhues
Hi Christopher, * Christopher Hulbert wrote on Wed, Feb 15, 2006 at 04:10:20PM CET: 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

Re: exclusive static or shared

2006-02-17 Thread Ralf Wildenhues
Hi Christopher, * Christopher Hulbert wrote on Fri, Feb 17, 2006 at 08:21:07PM CET: I normally do not create shared libraries. The ONE place I do though is with Matlab MEX functions which are nothing more than a shared library with the mexFunction as an exported function. I link my Matlab

Re: exclusive static or shared

2006-02-17 Thread Christopher Hulbert
I normally do not create shared libraries. The ONE place I do though is with Matlab MEX functions which are nothing more than a shared library with the mexFunction as an exported function. I link my Matlab code against static libraries that contain my real functions (The matlab interface serves

Re: exclusive static or shared

2006-02-15 Thread Ralf Wildenhues
Hi Christopher, * Christopher Hulbert wrote on Tue, Feb 14, 2006 at 11:08:28PM CET: I have a number of directories most of which I ONLY want to build shared libraries from. There are a couple that I ONLY want static libraries. Is there a way to turn on/off shared/static libraries. I saw

Re: exclusive static or shared

2006-02-15 Thread Christopher Hulbert
On 2/15/06, Ralf Wildenhues [EMAIL PROTECTED] wrote: Hi Christopher, * Christopher Hulbert wrote on Tue, Feb 14, 2006 at 11:08:28PM CET: I have a number of directories most of which I ONLY want to build shared libraries from. There are a couple that I ONLY want static libraries. Is

Re: exclusive static or shared

2006-02-15 Thread Ralf Wildenhues
Hi Christopher, * Christopher Hulbert wrote on Wed, Feb 15, 2006 at 12:28:59PM CET: On 2/15/06, Ralf Wildenhues [EMAIL PROTECTED] wrote: Here's a set of rules. I guess I didn't make it clear enough that ALL the subdirectories were under the same configure script and doesn't make logical

Re: exclusive static or shared

2006-02-15 Thread Ralf Wildenhues
* Christopher Hulbert wrote on Wed, Feb 15, 2006 at 12:28:59PM CET: On 2/15/06, Ralf Wildenhues [EMAIL PROTECTED] wrote: --tag=disable-shared --tag=disable-static - These flags need to go before the compiler: speaking in Automake terms, they would fit in LIBTOOLFLAGS but not in

Re: exclusive static or shared

2006-02-15 Thread Christopher Hulbert
On 2/15/06, Ralf Wildenhues [EMAIL PROTECTED] wrote: Hi Christopher, * Christopher Hulbert wrote on Wed, Feb 15, 2006 at 12:28:59PM CET: On 2/15/06, Ralf Wildenhues [EMAIL PROTECTED] wrote: Here's a set of rules. I guess I didn't make it clear enough that ALL the subdirectories

Re: exclusive static or shared

2006-02-15 Thread 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