Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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-Authentication-Warning:	eos.vss.fsi.com: ford owned process doing -bs
Date:	Thu, 29 Jan 2004 17:43:23 -0600 (CST)
From:	Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender:	ford AT eos
To:	cygwin AT cygwin DOT com
Subject:	C COM objects?
Message-ID:	<Pine.GSO.4.58.0401291731420.11773@eos>
MIME-Version:	1.0
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

I admit to know almost nothing about COM objects, but I have been tasked
to find out if they can be built from code that uses cygwin1.dll services.

Searching for Cygwin and COM on the web, and in the archives, is difficult
for the obvious .com reason.

What I think I do know is that C++ COM objects are probably out because of
name mangling and vtable issues.  I am still unclear about whether the
libs that implement COM use msvcrt*.dll.  I assume if that is true, then
all COM objects are out because of the newlib conflict.

Any pointers to C COM object examples or information about using Cygwin
based code in them would be *greatly* appreciated.  If you feel this
subject is too far OT, then please feel free to ignore my Reply-To header
and send me personal email.  Thanks.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/

- Raw text -