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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ingolf Steinbach <Ingolf.Steinbach@xxxxxxxxxxxxxxxx> writes:

> Hi,
> 
> what are the necessary steps with gcc/g++ to solve the following
> problem:
> 1. Target is a static library
> 2. The library presents a C language API
> 3. Internally, the library is implemented in C++ and makes
>    heavy use of standard components from the stdc++ library
> 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. 

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

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux