Re: Statically link against helper libs?

[Braden McDaniel]

On Wed, 14 Feb 2001, Robert Boehne wrote:

> Braden McDaniel wrote:
> >
> > Is it possible to statically link against a helper library? The output of
> > the process needs to be a shared library, so configuring with
> > AM_DISABLE_SHARED isn't the answer. And I don't want to just include the
> > objects in the helper lib in the shared lib, as I don't need (or want) the
> > symbols in the helper lib to be external in the shared library. I realize
> > I could use a file specifically listing which symbols should be exported,
> > but that would be tedious to maintain so I'm hoping for a simpler
> > solution.
>
> I think it would help if you were more specific about what you are
> trying to do.  What do you mean by a "helper library"?
> In the general sense, you can't link *.a's into shared libraries,
> because the objects used to generate them are not necessarily
> position independent code.

My project uses a slightly modified third-party library. I don't want to
install the library individually, as such an installation might conflict
with an existing installation. Of course I could rename it, but it seems
like compiling it into the same binary as my project's code would be a
tidier solution.

Since I've modified the third-party library, I don't want applications
that depend on both my library and the third-party library to
inadvertently link against my library where they should be linking against
the third-party library; so I shouldn't be exporting the third-party
library's symbols in my library.

-- 
Braden McDaniel                 It is hard to know if nothing is /
http://endoframe.com            actually nothing
e-mail: address@hidden    And thus difficult to know if a policy /
Jabber: address@hidden       of doing nothing is successful
                                                -- Radiohead