![[GNU Libtool]](libtool.jpg)
GNU Libtool - The GNU Portable Library ToolCopyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc.
Originally by Gordon Matzigkeit, 1996.
Home | News | Documentation | Future Directions | Contributing | Administration
Current Release Versions Stable Release GNU Libtool 1.5.22 18 December 2005 Changelog Development Release of Stable Branch GNU Libtool 1.5.23b 17 February 2007 Changelog Daily CVS Snapshot of Stable Branch GNU Libtool 1.5.23c Today Changelog Development Release GNU Libtool 1.9f 23 October 2004 Changelog Daily CVS Snapshot GNU Libtool 2.1a Today Changelog Introduction
GNU libtool is a generic library support script. Libtool hides the complexity of using shared libraries behind a consistent, portable interface.
To use libtool, add the new generic library building commands to your Makefile, Makefile.in, or Makefile.am. See the documentation for details.
Availability
The latest official stable release is available via ftp from your nearest GNU mirror. Download instructions and a list of ftp mirror sites are here.
Daily snapshots of the repository are available via http from finch.finkproject.org/~pogma/libtool/.
Anonymous CVS
The latest libtool development sources are available via anonymous CVS.
Use the following commands to check them out:
$ export CVS_RSH=ssh $ cvs -z3 -d :pserver:anonymous@cvs.sv.gnu.org:/sources/libtool co libtoolOnce you have the tree checked out, you can keep it up to date by using cvs update. There are two interesting branches right now, which you can check out by using the -r <tag> switch to cvs co or cvs update:
Tag Details HEAD The main development trunk, working towards release 2.0 branch-1-5 The 1.5 release branch. Patch releases for 1.5.x will come from here You can browse the cvs archive live from the subversions repository with the help of viewcvs.
If you want to mirror the entire Libtool cvs repository, we provide an anonymous rsync server at rsync://cvs.sv.gnu.org/sources/libtool/. Please contact cvs-hackers@gnu.org if you do publicly mirror the repository, so that we can list your name here.
The CVS version of GNU libtool often depends on some yet to be released versions of GNU Autoconf and GNU Automake.
Before using CVS Libtool, you ought to have installed recent versions of GNU Autoconf and Automake, then run ./bootstrap in the newly-created libtool directory in order to regenerate the configure script and Makefile.in files.
Resources
Online Documentation
For more information, read the libtool documentation.
You can read about various features that we hope to include in future versions of libtool.
Mailing Lists
Libtool has four mailing lists hosted at gnu.org. These lists have moderation turned on for mails from non-subscribed addresses. If you would like to prevent the delay caused by moderation until the moderators have white-listed your address, you may consider subscribing your email address and then subsequently turning off delivery of list messages to it. Archives of these lists are stored at http://mail.gnu.org/pipermail/:
- libtool@gnu.org is for discussion of libtool development, porting to new platforms, ideas for the future, general libtool usage or problems. New alpha and stable releases are announced here. You can subscribe or unsubscribe on the web with mailman, or by sending an email to libtool-request@gnu.org with subscribe as the subject line. Volume is typically low.
- libtool-patches@gnu.org is where the patches to the libtool repository are posted for peer review before being commited to CVS. You can subscribe or unsubscribe on the web with mailman, or by sending an email to libtool-patches-request@gnu.org with subscribe as the subject line. Volume is typically low, though individual messages can be quite large.
- libtool-commit@gnu.org is where summaries of changes commited to the CVS repository are automatically posted. If you wish to see these changes as they happen, you can subscribe or unsubscribe on the web with mailman, or by sending an email to libtool-commit-request@gnu.org with subscribe as the subject line. Volume is sporadic, but typically low.
- There is also a special list for reporting bugs, bug-libtool@gnu.org, to enable the developers to track submitted bug reports. You can subscribe or unsubscribe on the web with mailman, or by sending an email to bug-libtool-request@gnu.org with subscribe as the subject line. If you think you have found a bug in libtool, then you should, in the first instance send as complete a report as possible to this list, including the version of Libtool that you are using. Ideally, you should include the text you get by running config.guess, the text you see when you run configure, and if you can, a patch made with diff -u5 which fixes the problem. If you can send a small script, modelled after the scripts in the tests directory of the distribution which fails with the unpatched distribution, but passes with your patch applied we can add the test to the distribution to make sure the bug doesn't reappear.
Home | News | Documentation | Future Directions | Contributing | AdministrationReturn to GNU's home page.
Please send FSF & GNU inquiries & questions to gnu@gnu.org. There are also other ways to contact the FSF.
Please send comments on these web pages to webmasters@www.gnu.org, send other questions to gnu@gnu.org. This article
Copyright © 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
$Date: 2007/02/17 09:50:38 $ $Author: rwild $