This is the mail archive of the
mailing list for the Cygwin project.
cygwin C++ DLLs and inter-operation with M$OFT
- From: "Dylan Cuthbert" <dylan at q-games dot com>
- To: "Cygwin at Cygwin dot Com" <cygwin at cygwin dot com>
- Date: Wed, 13 Feb 2002 19:58:13 +0900
- Subject: cygwin C++ DLLs and inter-operation with M$OFT
To anyone who can help,
We've been having some fun creating DLLs that need to be loaded by some
Visual C++ code. The code in the dll itself, ie. the interface is C so
there aren't any name mangling problems. However, using v3.0.3 of GCC we
get unresolved symbol errors for any libstdc++ we do within the dll. These
errors don't occur after using the -V 2.95.3-5 option to gcc to revert to
the originally packaged compiler - I had a good poke around but I couldn't
work out why the symbols couldn't be resolved.
Anyway, after reverting to 2.95.3-5, our test code compiles but when we call
any cygwin dll code (from the VS application) we get an exception error in
cygwin1.dll - if the code uses any stdlib type stuff (such as memory
allocation, printf etc). There is no C++ code in there at all now.
I've read through the faqs and documentation and searched the mailing list
but I can't find any fixes for this problem (although a couple of other
people do mention it). Is there just some obvious initialisation stuff I'm
Q-Games, Dylan Cuthbert.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html