Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199911040632.AAA04274@mercury.xraylith.wisc.edu> To: Josh Pollak cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Problems with Mingw and DLL In-Reply-To: Your message of "Wed, 03 Nov 1999 22:02:10 EST." <4 DOT 2 DOT 0 DOT 58 DOT 19991103220205 DOT 009de960 AT postoffice5 DOT mail DOT cornell DOT edu> Date: Thu, 04 Nov 1999 00:32:40 -0600 From: Mumit Khan Josh Pollak writes: > Hello, > > As far as I can tell, this is the proper place to discuss this sort of > thing. I am trying to compile a DLL for Mingw (Without cygwin), that I can > already compile successfully in Visual C 6.0. I have heard from the author > of the sdk I am using that this will not work because: > > >Currently vtable referencing doesn't work with the EGCS GCC (Mingw) for > Windows. So > >you must make sure you use the C-Interface functions instead of the DMFC > class > >members. I don't know what this means, so could you please ask for a testcase and forward it to me. There are some obvious bugs in handling of imported classes with virtual functions (it has to do with creating vtables that need references to the function, and imported functions can't be constant addresses). Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com