[Merc, let's discuss this in the open on debian-x]
On Tue, Sep 05, 2000 at 04:38:34PM -0400, Zephaniah E. Hull wrote:
> In short, I am pretty close to having glide3 ready for testing, except
> for one thing, glide3 needs libXxf86dga and libXxf86vm as shared libs
> instead of static libs.
These aren't compiled as dynamic libraries because they have no real API.
Not one that anyone is willing to commit to yet, anyway.
> The glide3 new build system uses autoconf, automake, and libtool, the
> first two are no problem, the latter is another issue, glide3 links
> against libXxf86dga and libXxf86vm, both of which are provided only as
> static librarys.
>
> Not a big problem, until you interduce libtool, which absolutely refuses
> to link a shared library with a non-libtool static library, there is no
> quick override to say 'I know what I'm doing, now link the damn thing!',
> in fact, there is no way to do that at all.
Well, that's just plain stupid. There are all kinds of valid reasons to
link statically to a library.
> So I have three options.
> 1: Have libXxf86dga and libXxf86vm as shared libs.
> 2: Rewrite the entire glide3 build system.
> 3: Learn and rewrite libtool.
>
> Obviously, the latter two are not high on my list of things I'd love to
> do, the first depends on you.
I am highly reluctant to do that unless it really turns out to be the only
option. Is there a chance that the libtool maintainer(s) can be taught to
see reason? Know anyone who can stalk and beat them in a dark alleyway?
> Let me know ASAP so I can start the rewrite of the glide3 build system
> if I need to.
Let's see if we can't accomplish something with threats and intimidation
against our common enemy first.
gcc -DLIBTOOL_IS_A_FOOL
--
G. Branden Robinson |
Debian GNU/Linux | Exercise your freedom of religion. Set
[EMAIL PROTECTED] | fire to a church of your choice.
http://deadbeast.net/~branden/ |
PGP signature
