|
|
Blitz Support : |
From: Theodore Papadopoulo (Theodore.Papadopoulo_at_[hidden])
Date: 2003-09-09 04:04:57
cummings_at_[hidden] said:
> Not really because of the other problems I mentioned regarding
> libtool. It doesn't handle passing linker options to the C++ compiler
> correctly, which causes trouble especially when using a compiler such
> as KCC that acts as the linker also. And it replaces standard
> executables such as the testsuite programs with little scripts to run
> the executables. These scripts don't seem to work on all platforms.
> (I had trouble on AIX.)
The scripts are there so that the application can be executed
whatever is the place of the libraries (build or install place) and
executables. This is indeed somewhat troublesome, specially for
debugging, but these should not be generated when building static
versions of the stuff. You told us you use -disable-shared to solve
your problems, so why making it the default (at least until libtool
is safe enough) is not a proper solution.
> Besides, you don't need libtool to build
> blitz as a shared library. It is trivial to add support for building
> a shared version of libblitz to the configure script without using
> libtool, if anyone actually cares about this.
Believe me, that is not true. Generating the proper combination of
flags to generate a shared library is non trivial (and non portable
across various architectures).
Compiling shared libraries is non-trivial and that is why
libtool has been created (I used to modify automake for that with
numerous variants for each system). Reporting the bugs to the libtool
community and having them fixed is IMHO the best solution.
Also, I do not quite remember correctly, but I'm not totally sure
that I was not obliged to create a dynamic library (independently of
the CVS repo and it was a good surprise for me when shared lib
support was added) just because I'm using blitz within some other dynamic
libraries (I do not recall the details, but if I remember correctly some
architecture do not allow linking static libraries within dynamic ones).
Theo.
--------------------------------------------------------------------
Theodore Papadopoulo
Email: Theodore.Papadopoulo_at_[hidden] Tel: (33) 04 92 38 76 01
--------------------------------------------------------------------