Shared libraries : better management strategies ?

Hi there,
I wanted to know what are the various ways in which I can better
manage my shared libraries for my applications. I would like to place
my applications and shared libraries under my own application tree
hierarchy, but the application ( and the underlying hierarchy) can be
placed any where in the filesystem as per the users choice.
I wanted know how I can manage my shared libraries and the paths to
them, without using the LD_* constructs ? Is there any way for me to
achieve the same in any other manner.
Ideally I would like to include such a procedure in my build process
so that my the user installng my application doesnt need to bother
where to place the shared libraries.

Thanks for all your help guys.. I really appreciate the help.

Dhanvi

.

Relevant Pages

  • Re: Code density and performance?
    ... >> and our top ISVs use them to reduce I$ miss substantially ... > applications, not shared libraries, which makes it be of rather ... The binary optimizer isn't yet delievered, ...
    (comp.arch)
  • Re: Code density and performance?
    ... and our top ISVs use them to reduce I$ miss substantially for their applications. ... something like a database server would be amenable to whole-program optimization and static linking, and have no need of shared libraries. ... I mean executables using few "large" libraries, each library offering a small API and only exporting those API functions, with most calls being made intra-module, and with few load-time initializations. ...
    (comp.arch)
  • Re: Shared libraries : better management strategies ?
    ... manage my shared libraries for my applications. ... my applications and shared libraries under my own application tree ... hierarchy, but the application can be ...
    (comp.os.linux.development.apps)
  • Re: Code density and performance?
    ... >> and our top ISVs use them to reduce I$ miss substantially ... >> has a very graphical illustration of the effect of such optimizations ... > applications, not shared libraries, which makes it be of rather ...
    (comp.arch)