[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Forcing shared libaries

From: Sander Niemeijer
Subject: Re: Forcing shared libaries
Date: Tue, 7 Oct 2003 09:50:12 +0200

Ralph Schleicher already provided a patch to libtool for such a feature, but I don't know the current status of this patch (whether it will be in the next libtool release or not; anyone???).

Ralphs patch:

A small summary explaining the rationale behind the patch:


On maandag, okt 6, 2003, at 20:04 Europe/Amsterdam, Patrick Riley wrote:

Hi all,

I've got a project which I am in the process of converting to using
autoconf, automake, and libtool. [1]

The project builds several libraries and executables. For one of the
libraries, I would like to force libtool to only create shared
libraries, not static libraries no matter what the user gives to
configure (for the use being made of the library, only a shared library
makes sense). The other libraries should still obey the various
enable/disable shared/static directives.

Ideally, I would like to do this without having to do a recursive
configure. If I do have to do a recursive configure, is it
desirable/possible/how do I only have one copy of the libtool things in
my distribution?

Thank you.

[1] The project is Only the CVS version has
GNU autotool stuff because, as I said, I'm in the midst of conversion. I
also don't think the code is very portable yet, so you might have
problems if you actually try to compile it.

Patrick Riley
Fifth Year Ph.D. Student
Computer Science Department, Carnegie Mellon University

Libtool mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]