How to build a compiler-independent C++ library (for Solaris Studio and gcc)?

I would like to extend my library, which currently compiles only using gcc, to be used by Solaris Studio as well.

My idea is to do the following:

1. Write wrapper functions in C, which expose the relevant parts of the interface with extern C linkage.
2. Then build this library using gcc. The resulting c-header and binary are compiler independent as there is no name mangling anymore.
3. Include the c-header and link into the project compiled with Solaris Studio.

Question: Is this a feasible approach or is there a better solution to this problem?

Note: Besides name mangling, also watch out for problems related to exception handling.

Your plan is correct.

As long as your library exposes a C API compatible with platform ABI (sizes and alignments of C types, calling conventions) and does not throw C++ exceptions you are not going to have troubles linking your library using other compilers or languages.

You could also add a C++ header only wrapper for your C API to make it easily reusable from C++ and exception safe.