Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 19 Mar 2003 20:45:11 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [dpaun AT rogers DOT com: [RFC] windres' -I option] Message-ID: <20030320014511.GG32580@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030319202047 DOT GD27723 AT redhat DOT com> <3E7905B6 DOT 8070702 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E7905B6.8070702@ece.gatech.edu> User-Agent: Mutt/1.5.1i On Wed, Mar 19, 2003 at 07:05:10PM -0500, Charles Wilson wrote: > > >Christopher Faylor wrote: >>Anyone have any problems with this? I agree that it makes sense to make >>-I behave consistently. Are there scripts which would be fatally impacted >>if we made this switch? > >Okay by me, but you'll need to change winsup/w32api/lib/Makefile.in >eventually. I don't see a -I there. Isn't it just using --include-dir, which shouldn't be changing if I read the patch correctly? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/