Re: Forcing static link of libstdc++

[Mike Melanson]

Bob Proulx wrote:
> What I suggest is to bundle up all of the shared libraries called by
> the application and then including them in your installation bundle.
> If your only issue is ancillary shared libraries then simply reference
> them through LD_LIBRARY_PATH set in a invoking wrapper script.

Sounds like a useful possible solution. However, what if the primary 
functionality actually resides in a shared library itself? This is a 
proprietary plugin that another program is expected to load and call. Is 
there some sort of wrapper trick for that, or is that up to the 
communication between the app and the plugin?

        Thanks...
--
        -Mike Melanson