Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <20010123164332.18253.qmail@web1905.mail.yahoo.com> Date: Tue, 23 Jan 2001 08:43:32 -0800 (PST) From: =?iso-8859-1?q?Leo=20Liberti?= Subject: Using cygwin to make C++ DLL's to link with MSVC++ To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi. I have written a big application in a Unix GNU environment (GCC + tools), and I've been asked to port it to Windows. Needless to say, MSVC++ 6.0 just spits it out. So I downloaded Cygwin, and it compiled it. I then read everything I could on "how to make a .DLL" and after much struggling, I made the DLLs. But now I can't link under Windows. My guess is that the different C++ mangling scheme is causing trouble at link time (the MS linker says it can't find the functions, but in fact they are clearly there, dumpbin.exe says - but the mangled names are actually different). Anybody ever experienced this problem? In the faq it says that you can mix gcc .o and ms .obj as long as they are C. If it's C++, it says, it going to be difficult. Now, is it difficult or impossible? Thanks Leo __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple