Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com From: =?ISO-8859-15?Q?J=F6rg?= Schaible Subject: RE: Trying to link an MSVC DLL with a Cygwin Application Date: Tue, 04 May 2004 19:42:22 +0200 Lines: 16 Message-ID: References: <8ED2FA87C8ACC04192709688DDFD5F5F09B9BF AT calttsv025 DOT cal DOT riotinto DOT org> <20040504055710 DOT 27230 DOT qmail AT web20604 DOT mail DOT yahoo DOT com> Reply-To: joerg DOT schaible AT gmx DOT de Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8Bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: pd9eb81ad.dip0.t-ipconnect.de Mail-Copies-To: never User-Agent: KNode/0.7.7 john george wrote: > Can i resolve the name mangling issue by adding the > extern "C" declaration for every function that I'm > exporting in the MSVC created DLL. > I tried this but doesn't seem to work.Is there any > other way to do this. Be aware, that there is more than just a compatible call. You have to recognize, that you have two different RT-libs and therefore also two memory managers. Said that, you cannot allocate memory from the first one and set it free on the second. While this is quite obvious with malloc and friends, you have also to take care of strdup or fopen or ... Regards, Jörg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/