libtool: rm redundant man-pages
This commit is contained in:
parent
dc149b095b
commit
c05a127fd9
@ -1,106 +0,0 @@
|
||||
.TH LIBTOOL 1 "August 2003" "Library Support" "User Manuals"
|
||||
.SH NAME
|
||||
libtool \- Provide generalized library-building support services.
|
||||
.SH SYNOPSIS
|
||||
.B libtool
|
||||
.BI [ OPTION ] ...
|
||||
.BI [ MODE\-ARG ] ...
|
||||
.SH "DESCRIPTION"
|
||||
The `libtool' program provides a standard way to generate both static
|
||||
and shared libraries. It hides the complexities of platform\-specific
|
||||
library generation behind an interface that is the same across all
|
||||
platforms supported by libtool.
|
||||
.SH "OPTIONS"
|
||||
libtool accepts the following options:
|
||||
.TP
|
||||
.B \-\-config
|
||||
Display libtool configuration variables and exit.
|
||||
.TP
|
||||
.B \-\-debug
|
||||
Dump a trace of shell script execution to standard output. This
|
||||
produces a lot of output, so you may wish to pipe it to `less' (or
|
||||
`more') or redirect to a file.
|
||||
.TP
|
||||
.BI \-n | \-\-dry-run
|
||||
Don't create, modify, or delete any files, just show what commands
|
||||
would be executed by `libtool'.
|
||||
.TP
|
||||
.B \-\-features
|
||||
Display basic configuration options. This provides a way for packages
|
||||
to determine whether shared or static libraries will be built.
|
||||
.TP
|
||||
.B \-\-finish
|
||||
Same as
|
||||
.BR \-\-mode=finish .
|
||||
.TP
|
||||
.B \-\-help
|
||||
Display a help message and exit. If
|
||||
.BI \-\-mode= MODE
|
||||
is specified, then detailed help for
|
||||
.I MODE
|
||||
is displayed.
|
||||
.TP
|
||||
.BI \-\-mode= MODE
|
||||
Use
|
||||
.I MODE
|
||||
as the operation mode. By default, the operation mode is inferred
|
||||
from the
|
||||
.IR MODE\-ARGS .
|
||||
|
||||
If
|
||||
.I MODE
|
||||
is specified, it must be one of the following:
|
||||
.IP
|
||||
.B clean
|
||||
Remove files from the build directory
|
||||
.IP
|
||||
.B compile
|
||||
Compile a source file into a `libtool' object.
|
||||
.IP
|
||||
.B execute
|
||||
Automatically set the library path, then run a program.
|
||||
.IP
|
||||
.B finish
|
||||
Complete the installation of libtool libraries.
|
||||
.IP
|
||||
.B install
|
||||
Install libraries or executables.
|
||||
.IP
|
||||
.B link
|
||||
Create a library or an executable.
|
||||
.IP
|
||||
.B uninstall
|
||||
Remove libraries from an installed directory.
|
||||
.TP
|
||||
.B \-\-quiet
|
||||
Same as `\-\-silent'.
|
||||
.TP
|
||||
.B \-\-silent
|
||||
Don't print informational messages.
|
||||
.TP
|
||||
.B \-\-tag=TAG
|
||||
Use configuration variables from tag
|
||||
.I TAG
|
||||
.TP
|
||||
.B \-\-version
|
||||
Print version information.
|
||||
.P
|
||||
The
|
||||
.I MODE\-ARGS
|
||||
are a variable number of arguments, depending on the selected
|
||||
operation mode. In general, each
|
||||
.I MODE\-ARG
|
||||
is interpreted by programs libtool invokes, rather than libtool itself.
|
||||
.SH "SEE ALSO"
|
||||
.BR libtoolize (1),
|
||||
.BR automake (1)
|
||||
.br
|
||||
`libtool', `libtoolize' and `automake' are fully documented via the
|
||||
Info system.
|
||||
.SH AUTHOR
|
||||
This manual page was created by Ossama Othman <ossama@debian.org>. It
|
||||
is based on the "Invoking Libtool" menu entry in the `libtool' TEXINFO
|
||||
documentation, and the output from the
|
||||
.B \-\-help
|
||||
option. It was updated for Libtool 1.5 by
|
||||
Scott James Remnant <scott@netsplit.com>.
|
||||
@ -1,63 +0,0 @@
|
||||
.TH LIBTOOLIZE 1 "August 2003" "Library Support" "User Manuals"
|
||||
.SH NAME
|
||||
libtoolize \- add libtool support to your package
|
||||
.SH SYNOPSIS
|
||||
.B libtoolize
|
||||
.I "[OPTION]..."
|
||||
.SH "DESCRIPTION"
|
||||
The `libtoolize' program provides a standard way to add libtool
|
||||
support to your package. In the future, it may implement better usage
|
||||
checking, or other features to make libtool even easier to use.
|
||||
.SH "OPTIONS"
|
||||
libtoolize accepts the following options:
|
||||
.TP
|
||||
.B \-\-automake
|
||||
Work silently, and assume that Automake libtool support is used.
|
||||
|
||||
`libtoolize --automake' is used by Automake to add libtool files to
|
||||
your package, when `AC_PROG_LIBTOOL' appears in your `configure.in'.
|
||||
.TP
|
||||
.B \-\-copy, \-c
|
||||
Copy files from the libtool data directory rather than creating
|
||||
symlinks.
|
||||
.TP
|
||||
.B \-\-debug
|
||||
Enable verbose shell tracing
|
||||
.TP
|
||||
.B \-\-dry-run, \-n
|
||||
Don't run any commands that modify the file system, just print them
|
||||
out.
|
||||
.TP
|
||||
.B \-\-force, \-f
|
||||
Replace existing libtool files. By default, `libtoolize' won't
|
||||
overwrite existing files.
|
||||
.TP
|
||||
.B \-\-help
|
||||
Display a help message and exit.
|
||||
.TP
|
||||
.B \-\-ltdl
|
||||
Install libltdl in a subdirectory of your package.
|
||||
.TP
|
||||
.B \-\-ltdl\-tar
|
||||
Add the file `libltdl.tar.gz' to your package.
|
||||
.TP
|
||||
.B \-\-version
|
||||
Print `libtoolize' version information and exit.
|
||||
|
||||
If `libtoolize' detects an explicit call to `AC_CONFIG_AUX_DIR'
|
||||
in your `configure.in', it will put the files in the specified directory.
|
||||
|
||||
`libtoolize' displays hints for adding libtool support to your
|
||||
package, as well.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
.BR libtool (1),
|
||||
.BR automake (1)
|
||||
.br
|
||||
`libtool', `libtoolize' and `automake' are fully documented via the
|
||||
Info system.
|
||||
.SH AUTHOR
|
||||
This manual page was written by Frederic Lepied <Lepied@debian.org>,
|
||||
for the Debian GNU/Linux system (but may be used by others).
|
||||
It was updated by Ossama Othman <ossama@debian.org> and updated for
|
||||
Libtool 1.5 by Scott James Remnant <scott@netsplit.com>.
|
||||
Loading…
Reference in New Issue
Block a user