C++ code with external C API --> static library?

[Ingolf Steinbach]

On Friday 11 June 2004 18:50, llewelly@xmission.com wrote:
> > 4. A user shall be able to use the library with gcc without
> >    having to know that the library is implemented in C++
> >    (i.e. the library must not reference unresolved C++ related
> >    symbols; all these symbols have to be resolved when the
> >    library is created).
>
> For this, you'll need to link libstdc++ and libsupc++ to the library
>     staticly.

Thank you for your comments.

Any suggestions wrt the correct invocation of g++ to achieve
this? (Note: of course, I'd prefer to only include those parts
of the stdc++ and supc++ libraries which are really needed.)

> > 5. Only symbols from the C language API are to be exported
> >    by the library. No internal symbols shall be visible.

I found some remarks on selecting the set of exported symbols
in the GNU ld info pages, but maybe I still got something
wrong (as there still are other symbols in the resulting library).
What is the correct way to do this?

Kind regards
    Ingolf
-- 

Ingolf Steinbach                       Jena-Optronik GmbH
ingolf.steinbach@jena-optronik.de       ++49 3641 200-147
PGP: 0x7B3B5661  213C 828E 0C92 16B5  05D0 4D5B A324 EC04