Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199906090507.AAA26010@mercury.xraylith.wisc.edu>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	COM/C++ update
Date:	Wed, 09 Jun 1999 00:07:18 -0500
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

In addition to all the "Can I do COM with egcs/gcc C++" in the mailing
list, quite a few of you have sent me private mail regarding the topic, 
so I'll just send a heads-up to the list instead of each individually.

Good news: Starting from the next release of egcs/gcc, gcc-2.95,
you'll be able to do COM interfaces in C++. Thanks to the work of 
Antonio M. O. Neto (the initial COM patches), Jason Merrill (he
took Antonio's work and did a great job with it!) and Anders Norlander 
(new headers and import libraries essential for COM).

I've only tested simple examples, courtesy of Jason Craig, with both
Cygwin and Mingw. We'll flush out the bugs over time, and I'm sure 
there are *many* of those just waiting to be discovered. I've tested 
mix-and-match MSVC and GCC which seems to work for my testcases.

Bad news: You'll have to use -fvtable-thunks which is not the default
for x86-win32 as is on ix86-linux. This also means that you may have
to recompile C++ libraries with -fvtable-thunks to be usable with your
COM interfaces. If you're using Cygwin, you'll also need to use the 
horrid hack __cygwin_noncygwin_dll_entry AT 12 entry point.

I'll probably upload a "stable" pre-2.95 version that folks can play 
with sometime next week, along with an example or two.

In the meantime, if you have working COM examples that don't require
DirectDraw and other "extra" features, please feel free to send it
to me.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -