Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Sat, 8 Jan 2000 18:54:51 -0500 From: Chris Faylor To: Corinna Vinschen Cc: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: winsup reorg completed Message-ID: <20000108185451.A14679@cygnus.com> Mail-Followup-To: Corinna Vinschen , cygwin-developers AT sourceware DOT cygnus DOT com References: <20000107174543 DOT A25797 AT cygnus DOT com> <3877CB07 DOT E43F0026 AT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3877CB07.E43F0026@vinschen.de>; from corinna@vinschen.de on Sun, Jan 09, 2000 at 12:40:55AM +0100 On Sun, Jan 09, 2000 at 12:40:55AM +0100, Corinna Vinschen wrote: >For the case it wasn't clear: > >Regardless of the initial problems I like the new structure of the >winsup build tree. > >I like especially the idea of the VERBOSE variable in the make files, >Chris. So you see the full babble only if you really want it. Thanks. I was afraid that people would find this obscure but I really hate seeing the line noise output, so I took a clue from the way perl does it, except it's not so easy with perl to figure out what the command-line arguments really are. Did you notice the PREPROCESS setting, too? It allows you to do a gcc -E -o foo.E foo.c . I find that I frequently need to do this. cgf