Jump to content

GNU Libtool: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m updated version + switched to cquote template
Line 1: Line 1:
{{Infobox_Software |
{{Infobox_Software
name = GNU Libtool |
| name = GNU Libtool
logo = [[Image:Libtool.jpg|200px]] |
| logo = [[Image:Libtool.jpg|200px]]
developer = [[GNU|The GNU Project]] |
| developer = [[GNU|The GNU Project]]
latest_release_version = 2.2|
| latest_release_version = 2.2.6a
latest_release_date = [[March 01]], [[2008]] |
| latest_release_date = {{release date and age|2008|09|08}}
operating_system = [[Cross-platform]] |
| operating_system = [[Cross-platform]]
genre = [[Library (computing)|Library]] |
| genre = [[Library (computing)|Library]]
license = [[GNU General Public License|GNU GPL]] |
| license = [[GNU General Public License|GNU GPL]]
website = http://www.gnu.org/software/libtool/ |
| website = http://www.gnu.org/software/libtool/
}}
}}
'''GNU Libtool''' is a [[GNU]] [[programming]] tool from the [[GNU build system]] used for creating portable [[library (computer science)|software libraries]]. To quote the introduction in the [http://www.gnu.org/software/libtool/manual/libtool.html Libtool Manual]:
'''GNU Libtool''' is a [[GNU]] [[programming]] tool from the [[GNU build system]] used for creating portable [[library (computer science)|software libraries]]. To quote the introduction in the [http://www.gnu.org/software/libtool/manual/libtool.html Libtool Manual]:
{{cquote|In the past, if a source code package developer wanted to take advantage of the power of [[shared libraries]], it was necessary to write custom support code for each platform on which the package ran. It was also necessary to design a configuration interface so that the package installer could choose what sort of libraries were built.
<blockquote>
In the past, if a source code package developer wanted to take advantage of the power of [[shared libraries]], it was necessary to write custom support code for each platform on which the package ran. It was also necessary to design a configuration interface so that the package installer could choose what sort of libraries were built.
</blockquote>


<blockquote>
GNU Libtool simplifies the developer's job by encapsulating both the platform-specific dependencies, and the user interface, in a single script. GNU Libtool is designed so that the complete functionality of each host type is available via a generic interface, but nasty quirks are hidden from the programmer.
GNU Libtool simplifies the developer's job by encapsulating both the platform-specific dependencies, and the user interface, in a single script. GNU Libtool is designed so that the complete functionality of each host type is available via a generic interface, but nasty quirks are hidden from the programmer.
</blockquote>


GNU Libtool's interface aims to be consistent. Users are not expected to read low-level documentation in order to have a source package build shared libraries. They should only have to run the package's ''configure'' script (or equivalent), and Libtool should take care of the details.
<blockquote>
|||[http://www.gnu.org/software/libtool/manual/libtool.html Libtool Manual]}}
GNU Libtool's interface aims to be consistent. Users are not expected to read low-level documentation in order to have a source package build shared libraries. They should only have to run the package's ''configure'' script (or equivalent), and Libtool should take care of the details.
</blockquote>


Libtool is typically used with [[Autoconf]] and [[Automake]], two other tools of the GNU build system.
Libtool is typically used with [[Autoconf]] and [[Automake]], two other tools of the GNU build system.

Revision as of 16:38, 13 September 2009

GNU Libtool
Developer(s)The GNU Project
Stable release
2.2.6a / September 8, 2008; 16 years ago (2008-09-08)
Repository
Operating systemCross-platform
TypeLibrary
LicenseGNU GPL
Websitehttp://www.gnu.org/software/libtool/

GNU Libtool is a GNU programming tool from the GNU build system used for creating portable software libraries. To quote the introduction in the Libtool Manual:

In the past, if a source code package developer wanted to take advantage of the power of shared libraries, it was necessary to write custom support code for each platform on which the package ran. It was also necessary to design a configuration interface so that the package installer could choose what sort of libraries were built.

GNU Libtool simplifies the developer's job by encapsulating both the platform-specific dependencies, and the user interface, in a single script. GNU Libtool is designed so that the complete functionality of each host type is available via a generic interface, but nasty quirks are hidden from the programmer.

GNU Libtool's interface aims to be consistent. Users are not expected to read low-level documentation in order to have a source package build shared libraries. They should only have to run the package's configure script (or equivalent), and Libtool should take care of the details.

Libtool is typically used with Autoconf and Automake, two other tools of the GNU build system.

See also