This is the mail archive of the
mailing list for the GCC project.
Re: C++ code with external C API --> static library?
Ingolf Steinbach <Ingolf.Steinbach@jena-optronik.de> writes:
> On Friday 11 June 2004 18:50, email@example.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
I don't remember, and I can't seem to make time to test it out. I
> (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?
I'm sorry, I don't know.