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
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 and
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
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
* 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
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
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
-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
-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
Hi!
Florian Schricker [EMAIL PROTECTED] schrieb am 14.02.06 17:02:12:
Hi!
(again - you helped me out on some automake issue already! :-))
On Tue, 2006-02-14 at 11:49 +0100, Ralf Wildenhues wrote:
Currently I am on the way on moving some software projects from custom
makefiles to
CVSROOT:/cvsroot/libtool
Module name:libtool
Branch:
Changes by: Ralf Wildenhues [EMAIL PROTECTED] 06/02/15 19:14:49
Modified files:
. : ChangeLog
doc: libtool.texi
Log message:
* doc/libtool.texi: Update copyright
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 and
The attached patch fixes the empty wl variable and the MS toolchain
assumption of -link -dll.
pgi.patch
Description: Binary data
Applied to HEAD.
Cheers,
Ralf
* doc/libtool.texi: Update copyright years.
Index: doc/libtool.texi
===
RCS file: /cvsroot/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.209
diff -u -r1.209 libtool.texi
---
14 matches
Mail list logo