Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Fri, 16 Jun 2000 17:27:58 -0400
To: cygwin@sourceware.cygnus.com
Subject: Re: New GCC available for testing (TRY 4) -- fixes include path problem
Message-ID: <20000616172758.D10421@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: cygwin@sourceware.cygnus.com
References: <20000615014501.A14168@cygnus.com> <20000615235922.A22415@cygnus.com> <20000616131828.A17545@cygnus.com> <394A69F7.AD03B52A@carlthompson.net> <20000616151231.A8096@cygnus.com> <394A89A0.2564D870@carlthompson.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <394A89A0.2564D870@carlthompson.net>; from cet@carlthompson.net on Fri, Jun 16, 2000 at 01:10:08PM -0700

On Fri, Jun 16, 2000 at 01:10:08PM -0700, Carl Thompson wrote:
>Wouldn't it be better (and probably save you a lot of mailing list headaches
>in the future) to just duplicate the Windows headers in the MinGW directory
>and not search the POSIX directory?  Or better yet to have a separate
>Windows header directory that is used by both?  I can easily see someone
>accidentally including a POSIX header for a normal Windows program then
>complaining to you that Cygwin is broken.

I am not changing the directory structure.

>I just took another quick look at the way things are now and I noticed
>another problem.  Some Windows headers are only in the POSIX include
>directory (such as "windows.h"), but some are only in the MinGW directory
>(such as "direct.h").  That means, with your latest snapshot, Cygwin
>programs can't use "direct.h" if they need to!

Did you look at the contents of direct.h?  It's mingw-specific.  POSIX
programs use dirent.h.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com