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 X-Originating-IP: [150.101.115.108] X-Originating-Email: [tilps AT hotmail DOT com] From: "Gareth Pearce" To: "'Heiko Nardmann'" , "'ML CygWIN'" Subject: RE: mixing MSVC++ and gcc C++ libs/dlls ? Date: Fri, 24 Oct 2003 07:20:41 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-reply-to: <200310231521.35953.h.nardmann@secunet.de> Message-ID: X-OriginalArrivalTime: 23 Oct 2003 21:20:43.0002 (UTC) FILETIME=[840715A0:01C399AB] > Hi! > > The FAQ tells me that only C object files can be mixed. > > Is this true for MS .NET and gcc 3.x since I expect both to be conform to > the > ABI standard ? > Gcc 3.0 attempted to conform to the c++ abi - it was wrong - so they fixed lots of things and 3.2 has a different abi. However, it was still wrong, and so 3.4 they are going to fix things and there will be a different abi again. If MS .NET actually manage to get conformance with the c++ abi correct (for some reason I doubt this) - then you may find increased luck mixing c++ object files. However you'd have to do said mixing without mixing std c++ libraries, most likely, since they would probably conflict. Name mangling is part of the c++ abi so that wont be an issue. Therefore I predict in about 2 years time when g++ 3.6 is out and MS .Net version 2 is out - life may have improved in this reguards ;) If it works before then, yay for it. Gareth -- 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/