Re: Libtool -release and static libraries.

2006-02-15 Thread Brendon Costa
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter O'Gorman wrote: > Since you seem to want libatcppunit-1.0.6 to be the library name, I suggest > that you use it as the library name :) > > lib_LTLIBRARIES = libatcppunit-1.0.6.la > > This means that the libatcppunit.so symlink will also disappe

Re: Libtool -release and static libraries.

2006-02-15 Thread Peter O'Gorman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brendon Costa wrote: | Hi all, | | I am using libtool version 1.5.18 to create a library I wrote for | unit testing. It has come to the stage where I would find it useful to | have multiple versions of this library installed at any point in time

Libtool -release and static libraries.

2006-02-15 Thread Brendon Costa
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I am using libtool version 1.5.18 to create a library I wrote for unit testing. It has come to the stage where I would find it useful to have multiple versions of this library installed at any point in time on my machine. I had a look

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 it

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

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

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 mak

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

Re: libtool (alpha)

2006-02-15 Thread Ralf Wildenhues
Hi Julien, * Julien Lecomte wrote on Wed, Feb 15, 2006 at 04:51:54AM CET: > > I've installed the libtool alpha cvs build under MinGW. > Configuration and install was made under mSys (after replacing > config.{guess,sub}): > > ../alpha/configure --prefix=/usr > make > > Of note: I configured a

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