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 Message-ID: <3877D389.286FA9A4@vinschen.de> Date: Sun, 09 Jan 2000 01:17:13 +0100 From: Corinna Vinschen X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: de,en MIME-Version: 1.0 To: Chris Faylor CC: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: winsup reorg completed References: <20000107174543 DOT A25797 AT cygnus DOT com> <3877CB07 DOT E43F0026 AT vinschen DOT de> <20000108185451 DOT A14679 AT cygnus DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Chris Faylor wrote: > > 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 Really, yesterday I _found_ the make output obscure until I realized how it works! > 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. No, I haven't seen it. Pretty good! I have used preprocess output very seldom in the winsup dir. It bothers me to copy/paste the complete rat tail of compile options and hopefully without errors... ;-) Corinna