digitalmars.com
Last update Sun Mar 4 11:58:08 2018
Compiler & Tools Guide
Tools
BCC
CHMOD
CL
COFF2OMF
COFFIMPLIB
DMC
DIFF
DIFFDIR
DMAN
DUMP
DUMPOBJ
DUMPEXE
EXE2BIN
FLPYIMG
GREP
HC
HTOD
IMPLIB
LIB
LIBUNRES
MAKE
MAKEDEP
ME
OBJ2ASM
PATCHOBJ
RC
RCC
SC
SHELL
SMAKE
TOUCH
UNMANGLE
WHEREIS
Compiling
Compiling Code
C Implementation
C++ Implementation
C++0x Implementation
Language Extensions
Mixing Languages
Assembly Language
Inline Assembler
Optimizing Code
Numerics Programming
Regular Expressions
Acrtused
Pragmas
Precompiled Headers
Predefined Macros
Warning Messages
Error Messages
Runtime Messages
Linking
Optlink
Switches
Module Definition Files
Operation and Design
Error Messages
Win32 Programming
Win32 Programming
DOS and Win16 Programming
Memory Models
16 Bit Pointer Types and Type Modifiers
Handle Pointers
DOS
DOS 32 (DOSX)
Win16
Win16 DLLs
Win16 Prolog/Epilog
Virtual Memory For 640Kb DOS
C/C++ Extensions
Contract Programming
__debug statement
__debug declaration
Dynamic Profiling
Embedding C in HTML
Porting to DMC++
Switching to DMC++
from Microsoft
from Borland
Porting Guide
<h1><a name="lib">LIB: Object File Librarian</a> </h1> A library manager is a utility that maintains object library files. Object libraries are collections of related object (<tt>.obj</tt>) files, such as a set of graphics functions, or the run-time libraries supplied with this compiler. Object libraries are useful for linking them as a single, convenient file, rather than as many separate files. Creating an object library does not change the contents of the object files or how they work. A library just gathers object files in one place. <p> Use <strong>lib</strong> to create, maintain, and customize object library files. <strong>lib</strong> enables putting objects into libraries, replacing objects with newer versions, deleting objects from libraries, and extracting objects from libraries. <strong>lib</strong> can generate a text listing of the contents of a library. <p> <strong>lib</strong> handles both 16-and 32-bit object files in Intel OMF format. <h2><strong>lib</strong> command syntax</h2> <pre><strong>lib</strong> <em>switches</em>... <em>libfile</em> <em>objfiles</em>... </pre> <dl> <dt><em>switches</em>...</dt> <dd>Zero or more of the following. If none of -c, -d or -x is specified, the default action is to add the <em>objfiles</em> to the library. <table class="structure"><caption>Switches</caption> <tr><th>Switch</th> <th>Description</th></tr> <tr><td><strong>-c</strong></td> <td>Create new library and insert <em>objfiles</em> into it</td></tr> <tr><td><strong>-d</strong></td> <td>Delete <em>objfiles</em> from library</td></tr> <tr><td><strong>-h</strong></td> <td>Print brief help</td></tr> <tr><td><strong>-i</strong></td> <td>Ignore case of public symbols. The default is to be case sensitive</td></tr> <tr><td><strong>-n</strong></td> <td>Do not make a backup file of the original library</td></tr> <tr><td><strong>-l</strong></td> <td>Create text listing file of the symbols in the library. The listing file will be the name of the library with the <strong>.lst</strong> extension</td></tr> <tr><td><strong>-p</strong><em>nnn</em></td> <td>Set page size to <em>nnn</em> (a power of 2)</td></tr> <tr><td><strong>-x</strong></td> <td>Extract <em>objfiles</em> from library</td></tr> </table> </dd> <dt><em>libfile</em></dt> <dd>The name of the library file. The default extension is <strong>.lib</strong>.</dd> <dt><em>objfiles</em>...</dt> <dd>List of object files to be added, deleted, or extracted. The default extension is <strong>.obj</strong>. Library files can also be specified here, in order to insert whole libraries. </dd> </dl> <h3>Backup Libraries</h3> <p>If a library file is modified or rewritten, an existing library file of the same name is renamed to a file with a <strong>.bak</strong> extension. (This action is disabled with the <strong>-n</strong> switch.) Any previous file of the same name with the <strong>.bak</strong> extension is deleted. </p> <h3>Examples</h3> <pre>lib -h </pre> <p>Print help message.</p> <pre>lib foo a b c.obj </pre> <p>Create a library <tt>foo.lib</tt> and insert the object files <tt>a.obj</tt> <tt>b.obj</tt> and <tt>c.obj</tt>. </p> <pre>lib -l foo </pre> <p>Create listing file <tt>foo.lst</tt> of contents of <tt>foo.lib</tt>.</p> <pre>lib -d foo.lib a </pre> <p>Delete the object <tt>a.obj</tt> from <tt>foo.lib</tt>.</p> <pre>lib -x foo.lib b </pre> <p>Extract the object <tt>b.obj</tt> from <tt>foo.lib</tt> and write it to file <tt>b.obj</tt>.</p> <pre>lib foo.lib bar.lib a.obj </pre> <p>Add the contents of <tt>bar.lib</tt> and <tt>a.obj</tt> to <tt>foo.lib</tt>.</p> <h3>Using <strong>lib</strong> with SMAKE</h3> The usual technique is: <pre>OBJS=a.obj b.obj c.obj foo.lib : $(OBJS) lib -c foo.lib $(OBJS) </pre> <p>If the list of OBJS gets too long for the command line, SMAKE can automatically create a response file. Use an SMAKE command like:</p> <pre>OBJS=a.obj b.obj c.obj foo.lib : $(OBJS) lib -c foo.lib \ @<< $(OBJS) << </pre> <h3>Using <strong>lib</strong> with MAKE</h3> <p>The usual technique is:</p> <pre>OBJS=a.obj b.obj c.obj foo.lib : $(OBJS) lib -c foo.lib $(OBJS) </pre> <p>If the list of OBJS gets too long for the command line, MAKE will automatically create a response file that <strong>lib</strong> will use.</p> <hr> <h2>Obsolete <strong>lib</strong> command syntax</h2> <p>For compatibility with older makefiles and batch files, <strong>lib</strong> supports an older command line syntax. Such makefiles should be upgraded to the new command syntax. </p> <p>Arguments are passed to <strong>lib</strong> via:</p> <ol> <li> the command line <li> a response file (similar to the linker response file) <li> interactively from the command prompt </ol> <strong>lib</strong> commands have the following format: <pre><strong>lib</strong> <em>lib-file</em> [<em>switches</em>][<em>action-files</em>]<strong>,</strong>[<em>list-file</em>][<strong>;</strong>] </pre> <p><em>lib-file</em> is the name of the library file to create or change. Its default file extension is <strong>.lib</strong>. </p> <p>The <em>switches</em> are: </p> <table class="structure"><caption>Switches</caption> <tr><th>Switch</th> <th>Description</th></tr> <tr><td><strong>/?</strong>, <strong>/H</strong></td> <td>Print help information</td></tr> <tr><td><strong>/B</strong></td> <td>Run <strong>lib</strong> in batch mode</td></tr> <tr><td><strong>/C</strong></td> <td>Create a new library <em>lib-file</em> if one does not exist. Use to create a new library without being prompted to do so</td></tr> <tr><td><strong>/I</strong></td> <td>Ignore case in public symbols (default)</td></tr> <tr><td><strong>/N</strong></td> <td>Do not back up the original library. The default behavior is to save a backup of the original library file with the extension <strong>.bak</strong></td></tr> <tr><td><strong>/NOE</strong></td> <td><strong>lib</strong> ignores this switch</td></tr> <tr><td><strong>/NOI</strong></td> <td>Treat uppercase and lowercase letters as distinct, and mark the library as case-sensitive. This applies only to public symbols. The default is <strong>/I</strong></td></tr> <tr><td><strong>/NOL</strong></td> <td>Do not display copyright message</td></tr> <tr><td><strong>/P:</strong><em>num</em></td> <td>Set page size to <em>num</em> (a power of 2)</td></tr> </table> <p>The <em>action-files</em> specify the objects on which to act and what to do with them. The <em>action-files</em> must be one or more object files in the current directory. The default extension for object files is <strong>.obj</strong>. When <strong>lib</strong> puts an object file into a library, it gives the object's module the name of the object file in uppercase and without an extension. </p> <p>To specify what to do with each object file, put one of the following switches before the name(s) of the <em>action-files</em>: </p> <table class="structure"><caption>Switches</caption> <tr><th>Switch</th> <th>Description</th></tr> <tr><td><strong>-</strong></td> <td>Removes the object from the library</td></tr> <tr><td><strong>+</strong></td> <td>Adds the object to the library If the library already contains an object of the same name, <strong>lib</strong> prints an error message and doesn't add the object</td></tr> <tr><td><strong>*</strong></td> <td>Copies the object into a separate object file, leaving the object in the library</td></tr> <tr><td><strong>+-</strong>, <strong>-+</strong></td> <td>Replaces an existing object in the library with a new version</td></tr> <tr><td><strong>*-</strong>, <strong>-*</strong></td> <td>Extracts the object module into an object file and deletes it from the library</td></tr> </table> <p>The <em>list-file</em> produces a file listing the contents of the library. The file first lists all the public symbols in alphabetical order with the name of the modules to which they belong. Next, it lists the modules alphabetically with the public symbols in them. The default <em>list-file</em> extension is <strong>.lst</strong>. If there is a <em>list-file</em> but no <em>action-files</em>, <strong>lib</strong> produces a list file without modifying the library. </p> <h3>Concatenating libraries</h3> <p>To concatenate two libraries, specify one as the <em>lib-file</em> and the other as an <em>action-file</em>. <strong>lib</strong> adds the modules from the <em>action-file</em> library to the other library without changing the names of the modules. </p> <p><strong>Note:</strong> <strong>lib</strong> doesn't allow two modules to contain the same public symbol. </p> <h3>Using <strong>lib</strong> interactively</h3> <p>If <strong>lib</strong> is run with no arguments, it prompts for the required arguments. Use the ampersand (<strong>&</strong>) character to continue input on a new line. </p> <h3>Response files</h3> <p>You can use <strong>lib</strong> with a response file, which contains the responses that the compiler would ask for if used interactively. For example, the response file below adds several objects to the library <tt>mywindow.lib</tt> and produces a listing file: </p> <pre>\dm\lib\mywindow.lib /c +winopen+winblank+winmove+winhide& +winshow+winputs+wingets+winprint \dm\mywin.lst; </pre> <p>If the response file is <tt>makewin.rsp</tt>, use <strong>lib</strong> like this:</p> <pre>lib @makewin.rsp </pre> <p>Don't use filenames beginning with <strong>@</strong> because <strong>lib</strong> mistakes it for a response file.</p> <h3>Using <strong>lib</strong> with <strong>smake</strong></h3> <p>The usual technique is:</p> <pre>OBJS=a.obj b.obj c.obj foo.lib : $(OBJS) -del foo.lib lib foo.lib/C/NOI +a+b+c; </pre> <p>If the list of OBJS gets too long for the command line, <strong>smake</strong> can automatically create a response file. Use an <strong>smake</strong> command like:</p> <pre>OBJS=a.obj b.obj c.obj foo.lib : $(OBJS) -del foo.lib lib foo.lib/C/NOI \ @<< +a& +b& +c; << </pre> <h3>Using <strong>lib</strong> with <strong>make</strong></h3> <p>The usual technique is:</p> <pre>OBJS=a.obj b.obj c.obj foo.lib : $(OBJS) -del foo.lib lib foo.lib/C/NOI +a+b+c; </pre> <p>If the list of OBJS gets too long for the command line, use multiple <strong>lib</strong> commands:</p> <pre>OBJS=a.obj b.obj c.obj foo.lib : $(OBJS) -del foo.lib lib foo.lib/C/NOI +a+b; lib foo.lib/NOI +c; </pre> <hr> <h3>Error Messages</h3> <dl> <dt><tt><a name="redefinition">Warning: Public '<em>symbol name</em>' already in library, redefinition ignored.</a> </tt> </dt> <dd>The librarian builds a dictionary of object files corresponding to public symbols in those object files. This is so that an unresolved public symbol can be looked up in the library's dictionary, and the corresponding object file is then linked in. If a particular <tt><em>symbol name</em></tt> appears in more than one object file, there is no longer a unique mapping of symbol names to object files, hence the warning.</dd> </dl> <hr> <h3>Bugs</h3> <ul> <li> <strong>lib</strong> doesn't work with COFF files. To work around, use <a href="/index.cgi/contrast/https://digitalmars.com/ctg/coff2omf.html">coff2omf</a> to convert them to Intel OMF format. <li>Due to the Microsoft OMF library file format, there is a hard limit on the length of an identifier of slightly less than 512 characters. The only way around this is to use a shorter name, or to link in those modules separately that use longer names. </ul> </div> <div id="footernav"> <a href="https://www.digitalmars.com/" title="digitalmars.com">Home</a> | <a href="/index.cgi/contrast/https://digitalmars.com/ctg/../rtl/rtl.html" title="Runtime Library Reference">Runtime Library</a> | <a href="/index.cgi/contrast/https://digitalmars.com/ctg/../ugr/ugr.html" title="IDDE Reference">IDDE Reference</a> | <a href="/index.cgi/contrast/https://digitalmars.com/ctg/../stl/index.html" title="Standard Template Library">STL</a> | <a href="https://www.digitalmars.com/advancedsearch.html" title="Search Digital Mars web site">Search</a> | <a href="https://www.digitalmars.com//download/freecompiler.html" title="download C++">Download</a> | <a href="https://www.digitalmars.com/NewsGroup.html" title="Forums">Forums</a> </div> <div id="copyright"> Copyright © 1999-2018 by Digital Mars ®, All Rights Reserved | Page generated by <a href="https://dlang.org/spec/ddoc.html">Ddoc</a>. </div> </div><div class="naked_ctrl"> <form action="/index.cgi/contrast" method="get" name="gate"> <p><a href="http://altstyle.alfasado.net">AltStyle</a> によって変換されたページ <a href="https://digitalmars.com/ctg/lib.html">(->オリジナル)</a> / <label>アドレス: <input type="text" name="naked_post_url" value="https://digitalmars.com/ctg/lib.html" size="22" /></label> <label>モード: <select name="naked_post_mode"> <option value="default">デフォルト</option> <option value="speech">音声ブラウザ</option> <option value="ruby">ルビ付き</option> <option value="contrast" selected="selected">配色反転</option> <option value="larger-text">文字拡大</option> <option value="mobile">モバイル</option> </select> <input type="submit" value="表示" /> </p> </form> </div> </body> </html>