development / crossrootfs.git / blame
| Commit | Line | Data |
|---|---|---|
| 6dca1d21 JB |
1 | .TH LIBTOOL 1 "August 2003" "Library Support" "User Manuals" |
| 2 | .SH NAME | |
| 3 | libtool \- Provide generalized library-building support services. | |
| 4 | .SH SYNOPSIS | |
| 5 | .B libtool | |
| 6 | .BI [ OPTION ] ... | |
| 7 | .BI [ MODE\-ARG ] ... | |
| 8 | .SH "DESCRIPTION" | |
| 9 | The `libtool' program provides a standard way to generate both static | |
| 10 | and shared libraries. It hides the complexities of platform\-specific | |
| 11 | library generation behind an interface that is the same across all | |
| 12 | platforms supported by libtool. | |
| 13 | .SH "OPTIONS" | |
| 14 | libtool accepts the following options: | |
| 15 | .TP | |
| 16 | .B \-\-config | |
| 17 | Display libtool configuration variables and exit. | |
| 18 | .TP | |
| 19 | .B \-\-debug | |
| 20 | Dump a trace of shell script execution to standard output. This | |
| 21 | produces a lot of output, so you may wish to pipe it to `less' (or | |
| 22 | `more') or redirect to a file. | |
| 23 | .TP | |
| 24 | .BI \-n | \-\-dry-run | |
| 25 | Don't create, modify, or delete any files, just show what commands | |
| 26 | would be executed by `libtool'. | |
| 27 | .TP | |
| 28 | .B \-\-features | |
| 29 | Display basic configuration options. This provides a way for packages | |
| 30 | to determine whether shared or static libraries will be built. | |
| 31 | .TP | |
| 32 | .B \-\-finish | |
| 33 | Same as | |
| 34 | .BR \-\-mode=finish . | |
| 35 | .TP | |
| 36 | .B \-\-help | |
| 37 | Display a help message and exit. If | |
| 38 | .BI \-\-mode= MODE | |
| 39 | is specified, then detailed help for | |
| 40 | .I MODE | |
| 41 | is displayed. | |
| 42 | .TP | |
| 43 | .BI \-\-mode= MODE | |
| 44 | Use | |
| 45 | .I MODE | |
| 46 | as the operation mode. By default, the operation mode is inferred | |
| 47 | from the | |
| 48 | .IR MODE\-ARGS . | |
| 49 | ||
| 50 | If | |
| 51 | .I MODE | |
| 52 | is specified, it must be one of the following: | |
| 53 | .IP | |
| 54 | .B clean | |
| 55 | Remove files from the build directory | |
| 56 | .IP | |
| 57 | .B compile | |
| 58 | Compile a source file into a `libtool' object. | |
| 59 | .IP | |
| 60 | .B execute | |
| 61 | Automatically set the library path, then run a program. | |
| 62 | .IP | |
| 63 | .B finish | |
| 64 | Complete the installation of libtool libraries. | |
| 65 | .IP | |
| 66 | .B install | |
| 67 | Install libraries or executables. | |
| 68 | .IP | |
| 69 | .B link | |
| 70 | Create a library or an executable. | |
| 71 | .IP | |
| 72 | .B uninstall | |
| 73 | Remove libraries from an installed directory. | |
| 74 | .TP | |
| 75 | .B \-\-quiet | |
| 76 | Same as `\-\-silent'. | |
| 77 | .TP | |
| 78 | .B \-\-silent | |
| 79 | Don't print informational messages. | |
| 80 | .TP | |
| 81 | .B \-\-tag=TAG | |
| 82 | Use configuration variables from tag | |
| 83 | .I TAG | |
| 84 | .TP | |
| 85 | .B \-\-version | |
| 86 | Print version information. | |
| 87 | .P | |
| 88 | The | |
| 89 | .I MODE\-ARGS | |
| 90 | are a variable number of arguments, depending on the selected | |
| 91 | operation mode. In general, each | |
| 92 | .I MODE\-ARG | |
| 93 | is interpreted by programs libtool invokes, rather than libtool itself. | |
| 94 | .SH "SEE ALSO" | |
| 95 | .BR libtoolize (1), | |
| 96 | .BR automake (1) | |
| 97 | .br | |
| 98 | `libtool', `libtoolize' and `automake' are fully documented via the | |
| 99 | Info system. | |
| 100 | .SH AUTHOR | |
| 101 | This manual page was created by Ossama Othman <ossama@debian.org>. It | |
| 102 | is based on the "Invoking Libtool" menu entry in the `libtool' TEXINFO | |
| 103 | documentation, and the output from the | |
| 104 | .B \-\-help | |
| 105 | option. It was updated for Libtool 1.5 by | |
| 106 | Scott James Remnant <scott@netsplit.com>. |