Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm 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: <9912081846.AA01808@mlx.com> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) From: MarketLogix Date: Wed, 8 Dec 99 10:46:05 -0800 To: Mumit Khan Subject: Re: Cygwin v1.0 windows headers and ObjC Cc: cygwin AT sourceware DOT cygnus DOT com Reply-To: mlx AT san DOT rr DOT com References: <199912081825 DOT MAA08202 AT mercury DOT xraylith DOT wisc DOT edu> Begin forwarded message: To: mlx AT san DOT rr DOT com cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Cygwin v1.0 windows headers and ObjC In-Reply-To: Your message of "Wed, 08 Dec 1999 04:38:27 PST." <9912081239 DOT AA01562 AT mlx DOT com> Date: Wed, 08 Dec 1999 12:25:45 -0600 From: Mumit Khan > I believe most of these have been fixed in the w32api headers for a > while (I'm talking about development version, which is not what comes > with Cygwin net or commercial releases). > Can you send me a testcase that shows this problem so I can see if it's >fixed or not? I'm sorry, I didn't mean to imply that the tools are out of whack. That is not the case. Once the 2 previously mentioned adjustments are made to the headers: basetyps.h & windows.h everything preprocesses just fine (from an ObjC point of view). Its really just a matter of those 2 preprocessor directives. So if it's already been dealt with for the next release, mission accomplished. Thanks, Steve B. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com