1 .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.40.4.
2 .TH LIBTOOL "1" "October 2011" "libtool 2.4.2" "User Commands"
4 libtool \- manual page for libtool 2.4.2
7 [\fIOPTION\fR]... [\fIMODE-ARG\fR]...
10 [\fIOPTION\fR]... \fI--mode=compile COMPILE-COMMAND\fR... \fISOURCEFILE\fR
13 [\fIOPTION\fR]... \fI--mode=link LINK-COMMAND\fR...
16 [\fIOPTION\fR]... \fI--mode=execute COMMAND \fR[\fIARGS\fR]...
19 [\fIOPTION\fR]... \fI--mode=install INSTALL-COMMAND\fR...
22 [\fIOPTION\fR]... \fI--mode=finish \fR[\fILIBDIR\fR]...
25 [\fIOPTION\fR]... \fI--mode=uninstall RM \fR[\fIRM-OPTION\fR]... \fIFILE\fR...
28 [\fIOPTION\fR]... \fI--mode=clean RM \fR[\fIRM-OPTION\fR]... \fIFILE\fR...
30 Provide generalized library\-building support services.
33 show all configuration variables
36 enable verbose shell tracing
38 \fB\-n\fR, \fB\-\-dry\-run\fR
39 display commands without modifying any files
42 display basic configuration information and exit
44 \fB\-\-mode\fR=\fIMODE\fR
45 use operation mode MODE
47 \fB\-\-preserve\-dup\-deps\fR
48 don't remove duplicate dependency libraries
50 \fB\-\-quiet\fR, \fB\-\-silent\fR
51 don't print informational messages
53 \fB\-\-no\-quiet\fR, \fB\-\-no\-silent\fR
54 print informational messages (default)
57 don't display warning messages
59 \fB\-\-tag\fR=\fITAG\fR
60 use configuration variables from tag TAG
62 \fB\-v\fR, \fB\-\-verbose\fR
63 print more informational messages than default
66 don't print the extra informational messages
69 print version information
71 \fB\-h\fR, \fB\-\-help\fR, \fB\-\-help\-all\fR
72 print short, long, or detailed help message
74 MODE must be one of the following:
77 remove files from the build directory
80 compile a source file into a libtool object
83 automatically set library path, then run a program
86 complete the installation of libtool libraries
89 install libraries or executables
92 create a library or an executable
95 remove libraries from an installed directory
97 MODE\-ARGS vary depending on the MODE. When passed as first option,
98 `\-\-mode=MODE' may be abbreviated as `MODE' or a unique abbreviation of that.
100 GNU libtool home page: <http://www.gnu.org/software/libtool/>.
101 General help using GNU software: <http://www.gnu.org/gethelp/>.
103 Description of compile mode:
105 Compile a source file into a libtool library object.
107 This mode accepts the following additional options:
109 \fB\-o\fR OUTPUT\-FILE
110 set the output file name to OUTPUT\-FILE
113 do not suppress compiler output for multiple passes
116 try to build PIC objects only
118 \fB\-prefer\-non\-pic\fR
119 try to build non\-PIC objects only
122 do not build a `.o' file suitable for static linking
125 only build a `.o' file suitable for static linking
128 pass FLAG directly to the compiler
130 COMPILE\-COMMAND is a command to be used in creating a `standard' object file
131 from the given SOURCEFILE.
133 The output file name is determined by removing the directory component from
134 SOURCEFILE, then substituting the C source code suffix `.c' with the
135 library object suffix, `.lo'.
137 Description of link mode:
139 Link object files or libraries together to form another library, or to
140 create an executable program.
142 LINK\-COMMAND is a command using the C compiler that you would use to create
143 a program from several object files.
145 The following components of LINK\-COMMAND are treated specially:
148 do not do any dynamic linking at all
150 \fB\-avoid\-version\fR
151 do not add a version suffix if possible
153 \fB\-bindir\fR BINDIR
154 specify path to binaries directory (for systems where
155 libraries must be found in the PATH setting at runtime)
158 `\-dlpreopen' FILE if it cannot be dlopened at runtime
160 \fB\-dlpreopen\fR FILE
161 link in FILE and add its symbols to lt_preloaded_symbols
163 \fB\-export\-dynamic\fR
164 allow symbols from OUTPUT\-FILE to be resolved with dlsym(3)
166 \fB\-export\-symbols\fR SYMFILE
167 try to export only the symbols listed in SYMFILE
169 \fB\-export\-symbols\-regex\fR REGEX
170 try to export only the symbols matching REGEX
173 search LIBDIR for required installed libraries
176 OUTPUT\-FILE requires the installed library libNAME
179 build a library that can dlopened
181 \fB\-no\-fast\-install\fR
182 disable the fast\-install mode
185 link a not\-installable executable
187 \fB\-no\-undefined\fR
188 declare that a library does not refer to external symbols
190 \fB\-o\fR OUTPUT\-FILE
191 create OUTPUT\-FILE from the specified objects
193 \fB\-objectlist\fR FILE
194 Use a list of object files found in FILE to specify objects
196 \fB\-precious\-files\-regex\fR REGEX
197 don't remove output files matching REGEX
199 \fB\-release\fR RELEASE
200 specify package release information
203 the created library will eventually be installed in LIBDIR
206 add LIBDIR to the runtime path of programs and libraries
209 only do dynamic linking of libtool libraries
211 \fB\-shrext\fR SUFFIX
212 override the standard shared library file extension
215 do not do any dynamic linking of uninstalled libtool libraries
217 \fB\-static\-libtool\-libs\fR
218 do not do any dynamic linking of libtool libraries
220 \fB\-version\-info\fR CURRENT[:REVISION[:AGE]]
221 specify library version info [each variable defaults to 0]
224 declare that the target provides the LIBNAME interface
228 \fB\-Xcompiler\fR FLAG
229 pass linker\-specific FLAG directly to the compiler
234 pass linker\-specific FLAG directly to the linker
236 \fB\-XCClinker\fR FLAG
237 pass link\-specific FLAG to the compiler driver (CC)
239 All other options (arguments beginning with `\-') are ignored.
241 Every other argument is treated as a filename. Files ending in `.la' are
242 treated as uninstalled libtool libraries, other files are standard or library
245 If the OUTPUT\-FILE ends in `.la', then a libtool library is created,
246 only library objects (`.lo' files) may be specified, and `\-rpath' is
247 required, except when creating a convenience library.
249 If OUTPUT\-FILE ends in `.a' or `.lib', then a standard library is created
250 using `ar' and `ranlib', or on Windows using `lib'.
252 If OUTPUT\-FILE ends in `.lo' or `.o', then a reloadable object file
253 is created, otherwise an executable program is created.
255 Description of execute mode:
257 Automatically set library path, then run a program.
259 This mode accepts the following additional options:
262 add the directory containing FILE to the library path
264 This mode sets the library path environment variable according to `\-dlopen'
267 If any of the ARGS are libtool executable wrappers, then they are translated
268 into their corresponding uninstalled binary, and any of their required library
269 directories are added to the library path.
271 Then, COMMAND is executed, with ARGS as arguments.
273 Description of install mode:
275 Install executables or libraries.
277 INSTALL\-COMMAND is the installation command. The first component should be
278 either the `install' or `cp' program.
280 The following components of INSTALL\-COMMAND are treated specially:
282 \fB\-inst\-prefix\-dir\fR PREFIX\-DIR
283 Use PREFIX\-DIR as a staging area for installation
285 The rest of the components are interpreted as arguments to that command (only
286 BSD\-compatible install options are recognized).
288 Description of finish mode:
290 Complete the installation of libtool libraries.
292 Each LIBDIR is a directory that contains libtool libraries.
294 The commands that this mode executes may require superuser privileges. Use
295 the `\-\-dry\-run' option if you just want to see what would be executed.
297 Description of uninstall mode:
299 Remove libraries from an installation directory.
301 RM is the name of the program to use to delete files associated with each FILE
302 (typically `/bin/rm'). RM\-OPTIONS are options (such as `\-f') to be passed
305 If FILE is a libtool library, all the files associated with it are deleted.
306 Otherwise, only FILE itself is deleted using RM.
308 Description of clean mode:
310 Remove files from the build directory.
312 RM is the name of the program to use to delete files associated with each FILE
313 (typically `/bin/rm'). RM\-OPTIONS are options (such as `\-f') to be passed
316 If FILE is a libtool library, object or program, all the files associated
317 with it are deleted. Otherwise, only FILE itself is deleted using RM.
319 When reporting a bug, please describe a test case to reproduce it and
320 include the following information:
323 x86_64\-apple\-darwin11.2.0
335 /usr/llvm\-gcc\-4.2/libexec/gcc/i686\-apple\-darwin11/4.2.1/ld (gnu? no)
341 automake (GNU automake) 1.11.1
344 autoconf (GNU Autoconf) 2.68
346 Written by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996
348 Report bugs to <bug\-libtool@gnu.org>.
350 Copyright \(co 2011 Free Software Foundation, Inc.
352 This is free software; see the source for copying conditions. There is NO
353 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
355 The full documentation for
357 is maintained as a Texinfo manual. If the
361 programs are properly installed at your site, the command
365 should give you access to the complete manual.