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 Date: Thu, 30 Sep 1999 09:21:22 -0500 (CDT) From: "M. R. Brown" To: "Araujo, Isaque G." cc: cygwin AT sourceware DOT cygnus DOT com Subject: RE: Programming COM interfaces with C++ In-Reply-To: <7F756A7F899DD11187BF0000C07018E5019F46D1@soaspw1.soa.alcoa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I wouldn't know if the COM examples were written specifically for mingw32 (which it looks like you're using) or meant to be compiled under cygwin. When I compiled them under cygwin, I got no errors. Like I said, I haven't had time to play with them, so someone else want to field this? COM on Win32 in particular is A Big Thing, and the fact that it's now supported (via patches) in gcc 2.95 is intringuing in itself. Does anyone know if this would work under COM that was ported to other another architecture (my mind escapes me as to non-Win32's that support COM, but I know there are some out there. Marcus On Thu, 30 Sep 1999, Araujo, Isaque G. wrote: > Well, I downloaded the files from this site, but when I try to compile, it > gives: > C:\GCC-2.95\src\comexample2>make > c++ -c -Id:/src/w32api/include -g -fvtable-thunks cmpnt.cpp -o cmpnt.o > ld: warning: cannot find entry symbol __cygwin_noncygwin_dll_entry AT 12; > defaultin > g to 6e381000 > c++ -o client.exe client.o guids.o -Ld:/src/w32api/lib -lole32 -luuid > > C:\GCC-2.95\src\comexample2> > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com