Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Shared libraries


Related Topics

In the News (Sat 26 Dec 09)

  
  Shared Libraries   (Site not responding. Last check: 2007-11-07)
With shared libraries we can have executables that are well below that size.Smaller executables save as well space in the release build domain; less disk space consumption might be of importance for the Solaris builds which tend to approach the 2 GB filesystem limit at SLAC.
Shared libraries have to contain code that is both, relocatable and re-entrant.
This will run 'shlib' to build a shared library for all packages in the test release, then do the standard shared linking procedure which is: linking shared libraries in the path first, followed by resolution of undefined symbols from static libraries.
www.ep1.ruhr-uni-bochum.de /~marcel/SharedLibs.html   (703 words)

  
 MkLinux Shared Library Support
The primary reason to use shared libraries is that you achieve a reduction in disk and memory use.
Another advantage of shared libraries is that when a library is updated, e.g., to fix a bug, all programs which use the library immediately enjoy the fix, without have to be rebuilt.
RPMs that require shared libraries can be identified by the convention that their names have an upper case letter as part of the revision number, e.g.
www.snake.net /people/paul/mklinux/shlib-setup.html   (1551 words)

  
 Shared Libraries without an MMU   (Site not responding. Last check: 2007-11-07)
Each shared library can assume a virtual address for the location of its writable static data segment and the MMU can be programmed to map to a physical address that is only used by that process.
Even if shared libraries are not used, the text segments for programs are still shared; If multiple instances of a program are running, they would be running from the same text space.
For the purposes of the shared library support, the import feature provided by the GOT is the ability to re-direct data references: The GOT forces a layer of indirection between each variable access.
www.ridgerun.com /xflat/NoMMUSharedLibs.html   (2959 words)

  
 [uClinux-dev] Shared libraries   (Site not responding. Last check: 2007-11-07)
The only known restriction on shared libraries at this point is that the environ global variable will not be initialised until the main program has started its execution.
In this implementation, each library is allocated a specific library identification number and this number is used to determine the offset used to locate its private data segment.
For n shared libraries there is an overhead of 4n+4 bytes per data segment and with up to n+1 data segments per application this quickly adds up.
mailman.uclinux.org /pipermail/uclinux-dev/2002-April/007786.html   (1173 words)

  
 shared libraries
If a shared library uses relocatable code, then this relocation must be performed every time the shared library is loaded into a new program, at a new place in memory.
If relocation wasn't required, then all copies of a shared object in memory would be identical, and in fact, it would be possible for all programs simultaneously requiring the same shared library to share the same copy in memory (thus the name "shared" library).
If a library was not made using -h, then the name under which programs using that library will look for it under is the name under which the linker found the library when those programs were produced.
tinf2.vub.ac.be /~dvermeir/manuals/shared_info.html   (3902 words)

  
 Shared Libraries
For shared libraries to support all of these desired properties, a number of conventions and guidelines must be followed.
The soname has the prefix ``lib'', the name of the library, the phrase ``.so'', followed by a period and a version number that is incremented whenever the interface changes (as a special exception, the lowest-level C libraries don't start with ``lib'').
According to the FHS, most libraries should be installed in /usr/lib, but libraries required for startup should be in /lib and libraries that are not part of the system should be in /usr/local/lib.
www.tldp.org /HOWTO/Program-Library-HOWTO/shared-libraries.html   (3393 words)

  
 Macromedia - Flash TechNote : Using shared libraries   (Site not responding. Last check: 2007-11-07)
Shared libraries allow multiple movies to share media such as movie clips, graphics, buttons and sounds.
For example, a shared library might contain several different buttons and sounds that are used in several different Flash movies.
In this example, the shared library file and the file that we will link to media in the shared library in the next step, will reside in the same web directory.
www.macromedia.com /cfusion/knowledgebase/index.cfm?id=tn_14767   (1772 words)

  
 Shared Libraries on HP-UX   (Site not responding. Last check: 2007-11-07)
The "text file busy" messages indicate that some process is accessing that shared library, and that process is running on the same machine that you are running on.
Because NFS is used at DIII-D, you may sometimes have the case where a process is accessing the shared library on another host in the LSF cluster.
A static library is a library that must by linked into the executable at compile time.
web.gat.com /comp/analysis/mdsplus/textfilebusy.html   (694 words)

  
 Debian Policy Manual - Shared libraries
Packages containing shared libraries must be constructed with a little care to make sure that the shared library is always available.
If you have several shared libraries built from the same source tree you may lump them all together into a single shared library package, provided that you change all of their sonames at once (so that you don't get filename clashes if you try to install different versions of the combined shared libraries package).
Shared libraries should not be installed executable, since the dynamic linker does not require this and trying to execute a shared library usually results in a core dump.
www.us.debian.org /doc/debian-policy/ch-sharedlibs.html   (1526 words)

  
 Ian Sharpe - Technical Notes - Shared Libraries & Ada
Shared libraries are binary files containing code that is intended to be linked with executing processes at run-time rather than during the link phase of executable development.
As long as a mechanism exists to call shared library routines (and ensure that the structure of the passed data is correct) the programming language of the caller and the library is unimportant.
The difference is in the way in which the shared library is loaded rather than in the library itself.
homepage.ntlworld.com /ian.sharpe/isharpe/technote/ada_sl.htm   (992 words)

  
 AMCA Shared Libraries
If more AMCA chorus libraries (current libraries especially) are accessible on this web site, it becomes very easy to do a Search for a particular title (or to search other information about music) and see if any other director/chorus has found a Male Chorus arrangement of that selection.
The usefulness of this "Shared Library" depends upon how willing choruses/directors are to share the "often-protected and private" (non-of-your-business) chorus libraries that they maintain.
Hopefully this will be enhanced if we continue to expand this "shared library" reference and develop a standard format.
amcofa.net /sl.shtml   (802 words)

  
 Unix Lisp based shared libraries
Allegro CL supports building shared libraries that can be used by C/C++ programs in the same manner as they use any other function libraries.
The wrapper C shared library is loaded and foreign function definitions are made as necessary.
If you don't call tcm() in your C shared library wrapper, then you will be able to see print and format that you may put in your Lisp code for debugging purposes.
www.franz.com /support/documentation/7.0/doc/unix-shared-library.htm   (2480 words)

  
 Shared Libraries Considered Harmful
The cost of not using a shared library, which means each application has to have its own copy of the code, means you end up taking ten megabytes of RAM and disk space instead of one.
And any issues of version conflicts at the protocol level are precisely the same whether you use shared libraries or not, as are the solutions to those issues.
Libraries that come with the operating system should not be visible as separate "shared libraries" at all.
www.geek-central.gen.nz /peeves/shared_libs_harmful.html   (1050 words)

  
 Writing shared libraries
This document is intended to describe best practices for writing shared libraries on Free ELF-based operating systems such as Linux and the BSD family.
Basically what this means is that if your library can run callbacks in user code, your library needs to be re-entrant: ie at any point at which you run a callback, execution can start again from the top of any of the library functions.
Very few libraries document their level of re-entrancy, it is assumed that any library which performs callbacks is totally re-entrant.
plan99.net /~mike/writing-shared-libraries.html   (3673 words)

  
 RISC OS Shared Libraries
Shared code and data are kept in a dynamic area on 32-bit systems, or in the RMA otherwise.
The module identifies ‘resolved’ areas from the ‘shared’ ones by checking their symbols for function entry points — if there are any, and we're running on a 32-bit system, the area will have to be copied out to application space so that the branch instructions can reach it.
Keeping unused libraries in memory in the expectation that they might be required again shortly may have some value.
www.comp.lancs.ac.uk /computing/users/ss/software/roshlibs   (1969 words)

  
 BeBits - Category - BeBits/System Files/Shared Libraries
Expat is an XML parser library written in C. It is a stream-oriented p...
JpegTools-6B is a widely used free library for JPEG image compression,...
Parts of xpdf compiled as a shared library for Intel and PowerPC.
www.bebits.com /browse/27   (337 words)

  
 rewindlife: Shared Libraries   (Site not responding. Last check: 2007-11-07)
Posted by Chafic at July 30, 2003 02:52 PM I've been working on a project that uses Shared Libraries a lot.
If you are using shared libraries make sure to test on different players as you are likely using some of the abilities that were fixed/added in that release.
Shared libraries are great once you get them setup.
www.rewindlife.com /archives/000043.cfm   (316 words)

  
 11 Shared Libraries
This chapter describes the shared libraries both in UNIX (shared libraries) and in Windows (DLLs).
When the project is compiled, the methods in modules in the dyn_libs libraries appear as "unregistered." When you run a project executable in which AVS/Express encounters unregistered methods in libraries for which the dyn_libs property is set, AVS/Express uses the library path variable to look for the methods.
Within AVS/Express itself, the W3C (Web) library (Read_URL, ReadWebField and ReadWebGeom macros) and the Read/Write image libraries are implemented as DLL libraries that share express.dll with the main executable.
help.avs.com /Express/doc/help_62/books/usersguide/UG11sharedlib.html   (4019 words)

  
 Shared Libraries in SunOS - Gingell, Lee, Dang, Weeks (ResearchIndex)   (Site not responding. Last check: 2007-11-07)
Abstract: The design and implementation of a shared libraries facility for Sun's implementation of the UNIX+ operating system (SunOS) is described.
Shared libraries extend the resource utilitization benefits obtained from sharing code between processes running the same program to processes running different programs by sharing the libraries common to them.
In this design, shared libraries are viewed as the result of the application of several more basic system mechanisms, specifically # kernel-supplied...
citeseer.ist.psu.edu /gingell87shared.html   (396 words)

  
 Troubleshooting Shared Libraries   (Site not responding. Last check: 2007-11-07)
Shared libraries provide a useful and powerful tool for speeding linking and execution of programs.
However, the implementation of shared libraries in most operating systems leaves much to be desired.
shared libraries are, you need to ensure that both the process that you run
www-unix.mcs.anl.gov /mpi/mpich/docs/mpichman-chp4/node82.htm   (472 words)

  
 Creating and Loading Shared Libraries   (Site not responding. Last check: 2007-11-07)
Procedures for creating and loading shared libraries are platform dependent.
The shared library file name requires a "lib" prefix and a ".so" extension.
The platform-dependent wrapper script or application shell can use the appropriate mechanism to indicate where shared libraries are located.
medialab.di.unipi.it /doc/tutorial/native1.1/stepbystep/_library.html   (262 words)

  
 ► » AIX shared libraries and lazyloading.   (Site not responding. Last check: 2007-11-07)
When are shared libraries that are attached to 0xd segment
libraries, in all libraries it uses same definition while in main it
libraries or should it be put in a.a.
www.all-unix.org /-AIX-shared-libraries-and-lazyloading--9164400.html   (342 words)

  
 Extending ROOT with Shared Libraries
In this tutorial we will show how to extend a running ROOT module with shared libraries.
Loading a shared library in a running ROOT session is trivial, first start
This is all there is to it to load a shared library into a running ROOT session.
root.cern.ch /root/Sharedlib.html   (202 words)

  
 Building Shared Libraries   (Site not responding. Last check: 2007-11-07)
However, if you are using ELF, you can easily make shared libraries, so each binary you link against your library doesn't keep it's own copy of all the code - resulting in smaller binaries.
This shouldn't be used if you are distributing binaries, and people won't have a copy of the library on their computer.
By convention, minor versions are compatible, but just bug fixes or whatever, while major versions are not compatible with each other.
www.bluegum.com /Software/Shared.html   (213 words)

  
 Debian -- Software Packages in "stable", libs section
Library for computing Fast Fourier Transforms on AMD K7 kdebindings-java (4:3.3.2-1)
an Ogg/Vorbis Library for Allegro - shared libraries
C++ wrapper for the OpenGL Extension to GTK (shared libraries)
packages.debian.org /stable/libs   (2451 words)

  
 Re: Shared libraries   (Site not responding. Last check: 2007-11-07)
If xpdf was available as a shared library, it certainly would..
If xpdf was available in KDE as a shared KDE wrapper library then it certainly would.
One practical problem is where do you put the common library.
dot.kde.org /1106325152/1106362760/1106364660   (325 words)

  
 LWN: Dissecting shared libraries (developerWorks)
"In this article, we'll review the underlying technology used for shared libraries and the way in which shared library versioning helps prevent the compatibility nightmares that naive shared library implementations have had in the past.
For more information, see my Program Library HOWTO, including the additional sources of information it lists.
Also see How to Write Shared Libraries by Ulrich Drepper: http://people.redhat.com/drepper/dsohowto.pdf
lwn.net /Articles/119007   (117 words)

  
 ► » shared libraries   (Site not responding. Last check: 2007-11-07)
versions of the same library in the same directory, you're best off
Other unixes seem to like having a handful of shared libraries in the same
Other unixes seem to like having a handful of shared libraries in the
www.all-unix.org /-shared-libraries-9157320.html   (300 words)

  
 Shared Libraries   (Site not responding. Last check: 2007-11-07)
We are in the process of converting our code to LInux and then will attempt to run the code on a Beowulf platform.
At this point the code has compiled and we are attempting to dynamically link to shared libaries.
We have been able to build statically linked applications, but not dynamically linked.
www.beowulf.org /pipermail/test/1998-December/003713.html   (137 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.