Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Mon, 12 Mar 2001 09:45:06 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: -mwin32 again Message-ID: <20010312094506.D19396@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20010311203629 DOT A17992 AT redhat DOT com> <3AACCAD7 DOT 7769B4E8 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3AACCAD7.7769B4E8@yahoo.com>; from earnie_boyd@yahoo.com on Mon, Mar 12, 2001 at 08:10:47AM -0500 On Mon, Mar 12, 2001 at 08:10:47AM -0500, Earnie Boyd wrote: >I believe this to be the best you can do. It's unfortunate that so many >are intertwined with the w32api. Is there any possibility for just >removing the w32api dependency in any of the applications to reduce the >number that require it? One thing we could do is change every include in w32api to be something like: #include Then you could just do something like: #include or I could make a top-level windows.h which included w32api/windows.h. I hate doing that to every header, though. I'm not sure how this would impact the mingw gcc release. cgf