 |  |
| |
In Darwin, much is built into the system library, /usr/lib/libSystem.dylib. In particular, the following libraries are included in libSystem.
Symbolic links are provided as placeholders for these libraries. For example, libm.dylib is a symbolic link in /usr/lib that points to libSystem.dylib. Thus, -lm or -lpthread do no harm, but are unnecessary. The -lm option links to the math library, and -lpthread links to the POSIX threads library. Since libSystem provides these functions, you don't need to use these options. However, you should use them to make sure your application is portable to other systems. (Since libm.dylib and libpthread.dylib are symbolic links to libSystem.dylib, the extra -l options will refer to the same library.)
WARNING: In Mac OS X 10.1 and earlier versions, the curses screen library (a set of functions for controlling a terminal display) was part of libSystem.dylib. In Mac OS X 10.2 (Jaguar), the ncurses library (/usr/lib/libncurses.5.dylib) took the place of curses. You may still encounter source code releases that look for curses in libSystem.dylib, which will result in linking errors. You can work around this problem by adding -lcurses to the linker arguments. This is portable to earlier versions of Mac OS X as well, since /usr/lib/libcurses.dylib is a symlink to libncurses in 10.2, and to libSystem in earlier versions.
Interestingly enough, there is no symbolic link for libutil, whose functionality is also provided by libSystem. (libutil is a library that provides functions related to login, logout, terminal assignment, and logging.) So, if a link fails because of -lutil, you should try taking it out to see if it solves the problem.
|  | |
| 5. Libraries, Headers, and Frameworks |  | 5.3. Shared Libraries Versus Loadable Modules |
Copyright © 2003 O'Reilly & Associates. All rights reserved.