1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
.TH LIBTOOLIZE 1
.\" NAME should be all caps, SECTION should be 1-8, maybe w/ subsection
.\" other parms are allowed: see man(7), man(1)
.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 `AM_PROG_LIBTOOL' appears in your `configure.in'.
.TP
.B \-\-copy, \-c
Copy files from the libtool data directory rather than creating
symlinks.
.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 \-\-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"
The programs are documented fully by
.IR "Libtool: Generic library support script." ,
available 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).
|
