Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 27 Apr 2001 16:57:57 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Any resolution to win32.h problem? Message-ID: <20010427165757.A11707@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4.3.1.2.20010427152731.024e7a60@pop.ma.ultranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <4.3.1.2.20010427152731.024e7a60@pop.ma.ultranet.com>; from lhall@rfk.com on Fri, Apr 27, 2001 at 03:32:29PM -0400 On Fri, Apr 27, 2001 at 03:32:29PM -0400, Larry Hall (RFK Partners, Inc) wrote: >Seems to me the solution proposed was the #ifdef mentioned below. Did you >try that? Its not at all clear to me that win32.h and windows.h from the >w32api package are supposed to be the same thing (as your symlink suggestion >implies). I'm definitely left with the impression that these are two >completely different files so I don't see that the symlink would be a >reasonable solution in that case. > >What FAQ entry suggests that Cygwin includes win32.h? FWIW, I have never heard of a win32.h file. I think it is a perl thing. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple