delorie.com/archives/browse.cgi | search |
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 |
X-Authentication-Warning: | modi.xraylith.wisc.edu: khan owned process doing -bs |
Date: | Fri, 16 Apr 1999 09:21:09 -0500 (CDT) |
From: | Mumit Khan <khan AT xraylith DOT wisc DOT edu> |
To: | Richard Ashwell <richval AT hotmail DOT com> |
cc: | cygwin AT sourceware DOT cygnus DOT com |
Subject: | Re: DirectX and COM objects |
In-Reply-To: | <19990416084707.67943.qmail@hotmail.com> |
Message-ID: | <Pine.SUN.3.93.990416091941.5315C-100000@modi.xraylith.wisc.edu> |
MIME-Version: | 1.0 |
On Fri, 16 Apr 1999, Richard Ashwell wrote: > Didn't this issue get resolved by using the COM stuff from LCC-Win > headers. TRUST ME :) I don't know any details. I just remember > reading in a DirectX 5.0 Library port to gnuwin32 that the COM stuff > had to be borrowed from the LCC-Win32 Compiler. We're talking about two different things. LCC-Win32 is a C compiler, and the initial "borrowing" (no longer needed thanks to Anders' great work on w32api headers) was just the header definitions, and then only using C syntax. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |