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 Message-ID: <41B0132F.1000304@x-ray.at> Date: Fri, 03 Dec 2004 08:18:07 +0100 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a4) Gecko/20040927 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: MSVC-dll under cygwin References: <000a01c4d883$eb5024f0$0200a8c0 AT mindcooler> <20041202153745 DOT GA29883 AT trixie DOT casa DOT cgf DOT cx> <001901c4d887$c873bfb0$0200a8c0 AT mindcooler> <002701c4d88f$3e12d100$0200a8c0 AT mindcooler> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Shankar Unni schrieb: > Mikael Åsberg wrote: > You cannot mix Visual C++ ("real" C++, I mean, not C) and Gnu C++ > modules in any way whatsoever. The two have completely different class > and virtual-table layout algorithms. You can actually. g++ emulates the msvc vtable layout. But you should not because of different underlying runtime libraries. new/delete mainly, but a lot of other dependencies clash also. > If you need to link a Gcc-compiled object to a VC++-compiled object, you > can only use 'extern "C"' APIs (and C structures) to cross between the two. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ -- 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/