A piece of binary code that provides a set of operations and datastructures like a normal library, but which does not need to be physically incorporated into the executables that use it until they are actually executed. Virtually always implemented on machines with virtual memory by mapping the memory pages holding the library into the address space of each executable image in memory that uses the lib. Many operating systems also support dynamic libraries which are an extension of shared libraries that can be loaded during the execution of the program and not just when it is loaded. Operating systems without shared libs are really horrible and inefficient to use, since you end up with many copies of the same code from the C library in memory. Thankfully, the world has moved on
A library created using the ld(1) command that contains one or more position-independent code object modules. Shared library file names end with .sl or a version number. See also: archive library
In general, any code module that can be accessed and used by many programs. Shared libraries are used primarily for sharing common code between different executable files or for breaking an application into separate components, thus allowing easy upgrades. In the Visual C++ documentation, "shared library" usually refers to a code module that is an Apple Shared Library Manager (ASLM) file for the Apple Macintosh. In Windows, shared libraries are usually referred to as dynamic-link libraries (DLLs).
A library that is used by more than one program. Loaded when an executable that links to it (statically) is loaded.
A collection of object files grouped using the aCC command and comprised of position-independent code. At link time, all object files are made available.
Like an archive library, a shared library contains relocatable object code. However, ld treats shared libraries quite differently from archive libraries. When linking an object file with a shared library, ld does not copy object code from the library into the executable file; instead, the linker simply notes in the executable file that the code calls a routine in the shared library. The actual linkage does not occur until the program is run. Shared libraries can be implicitly or explicitly loaded.
A library of routines that can be linked to an executable program at runtime and shared by several programs simultaneously. The names of shared libraries have the .sl extension. See also See also archive library..
A collection of object modules. When the linker scans a shared library, it does not copy modules into the application's code section, as it does with an archive library. Instead, the linker preserves information in the application's code section about which unresolved references were resolved in each shared library. At run time, the shared library is mapped into memory.
library of routines that can be linked to an executable program at runtime, allowing the shared library to be used by several programs simultaneously. See also archive library.
a collection of routines that different object files or executables can share
a collection of subroutines that can be shared among many programs
an executable module that is compiled and linked separately
an object module that can be loaded at run time at an arbitrary memory address, and it can be linked to by a program in memory
an operating system file, such as a Windows DLL or a Solaris shared object, that stores the coded implementation of external procedures
a shared object file that contains functions and data
a single-segment code resource, which is post-linked into a
A library, created by the ld command, which contains one or more PIC object modules. Shared library file names end with .sl. Compare with "archive library."
A library device that is shared among multiple Tivoli Storage Manager servers.
On the AIX operating system, a library created by the ld command that contains at least one subroutine that can be used by multiple processes. Programs and subroutines are linked as before, but the code common to different subroutines is combined in one library file that can be loaded at run time and shared by many programs. A key to identify the shared library file is left in the header of each subroutine. A shared library file has the file extension .shr. See dynamic link library.
Set of routines that may be accessed by many executable programs simultaneously.
A library that contains routines that are used by applications, are loaded into memory by the operating system as they are needed, and are shared with other applications.
