Hello Jason, * Jason Kraftcheck wrote on Fri, Jan 15, 2010 at 07:10:21PM CET: > I am trying to build a static library that is implemented in C++ and has a C > API. The resulting .la does not appear to include any information > indicating that the library needs to be either linked with C++ or explicitly > include the C++ runtime libraries. Thus when I try to link a simple test > application written in C, the link step fails because of unresolved symbols > provided by the C++ runtime libraries. What are my options at this point? > The ideal solution (for me) would be for libtool to include the C++ runtime > libraries in dependency_libs for the .la. Is this possible?
Not really. Your easiest bet is to just use the C++ compiler driver to link the test application. In case you are using Automake, you can force the C++ linker for otherwise C code with something like if FALSE nodist_prog_SOURCES += dummy.cpp endif or, more generally, by overriding prog_LINK or LINK. Cheers, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
