|
|
Blitz Support : |
From: Patrick Guio (patrick.guio_at_[hidden])
Date: 2003-09-08 05:25:24
On Fri, 5 Sep 2003, Julian C. Cummings wrote:
Hi Julian,
Sorry not to answer earlier but I was busy with other things.
If you really want to remove libtool support I can do it. I agree somehow
that it is not entirely necessary.
Sincerely,
Patrick
>
> I would agree with this suggestion. It is not critical to have a shared
> version of the Blitz library because it is so small anyway. And it is
> trivial to create a shared library manually with your favorite linker if you
> really need to have it. There are other problems with libtool as well. It
> doesn't cope well with situations in which the C++ compiler must be used as
> the linker and requires special flags to be passed to it. Also, libtool is
> being used to manage the linking of executables such as the testsuite codes.
> It does something funky where it places the executables in a secret .libs
> subdirectory and then wraps each executable with a script to run the
> executable. Presumably this is done in order to manage run-time library
> paths and such. But the scripts don't seem to work right on some Unix
> platforms. As a result, I've ended up using the --disable-shared option
> whenever I configure Blitz.
>
> Frank, do you have enough automake/autoconf expertise to take a swing at
> excising the libtool support from the present Blitz make system? I know
> that I don't. I would be happy if someone from the community could work out
> the necessary changes for the entire Blitz package and submit them.
>
> Regards, Julian C.
>