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.
Look into the build-time options -rpath and -rpath-link,
and the undocumented feature of "${ORIGIN}" in search paths.
Re: Dijkstra on the Usefulness of Hierarchy ... >> Dijkstra on the Usefulness of Hierarchy... > How many OO applications had Djikstra developed at the time he wrote this? ... > Citation and Context award for pulling comments out of context ... (comp.object)
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: Application logic and Business logic ... We should consider all applications that may access the account object as ... That process runs in a larger application called session.... This hierarchical structure of applications is one of scopes where objects ... would live somewhere amidst this hierarchy.... (comp.object)
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: 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)
