Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: HOWTO build debug version of the cygwin dll with no optimisation?
Date: Thu, 15 Jul 2004 16:14:05 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20040715143741.GD9941@trixie.casa.cgf.cx>
Message-ID: <NUTMEG7WE9UMGs1YZYp000008ca@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 15 Jul 2004 15:14:05.0468 (UTC) FILETIME=[5E5B45C0:01C46A7E]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Christopher Faylor
> Sent: 15 July 2004 15:38

> On Thu, Jul 15, 2004 at 03:32:14PM +0100, Dave Korn wrote:
> >> -----Original Message-----
> >> From: cygwin-owner On Behalf Of Christopher Faylor
> >> Sent: 15 July 2004 02:00
> >
> >> >> "CFLAGS_FOR_BUILD=" 	"CFLAGS_FOR_TARGET=-O2 -g -O0" 	
> >> "LDFLAGS="
> >> >                         ^^^^^^^^^^^^^^^^^
> >> >                         That's it :-)
> >> >
> >> >Try `make CFLAGS=-g CFLAGS_FOR_TARGET=-g'.  That will 
> >> compile everything
> >> >w/o optimization
> >> 
> >>Or, once you've gotten supporting libraries built, just build in the
> >>winsup/cygwin directory with CFLAGS=-g.  It's a lot faster to just
> >>build cygwin from the cygwin subdirectory.
> >
> >Good point.  I tend to do "make all-bfd all-target-winsup" at the
> >top-level, but that of course still drags in all the cygserver and
> >utils stuff that I don't need.
> 
> Wow.  The first response to my observation was a "good point"?

  I call 'em like I see 'em!

> That is surprising.  I fully expected to get a "Oh, I tried that once
> and it didn't work for me" from somebody.

  Well, I haven't actually tried it myself.  Is setting just CFLAGS enough
when you're in the lower-level directory?  I might have thought you had to
override the CXX and LD flags as well.  But I'd want to try it before
committing myself to an opinion... :)

> Anyway, FWIW, the only time I build cygwin from the top level is when
> I'm generating snapshots.  Otherwise, I live in the cygwin 
> (and occasionally the newlib) directory.

  Matter of fact, I knew it already, or rather had all the clues I
needed.... I used to (a few years back) very regularly be in the habit of
cd'ing into the gcc subdir and doing "make all" there for gcc builds; when
all you want is a cross-compiler, you might as well save the time of
building cross- and host- libiberty et al.  Then I got a faster computer,
and fell out of the habit!  But, yeh, this is a general principle with all
the software that shares top-level autoconf; once you've configured it you
can just cd into the relevant lower-level dir and do a "make all", to just
get the particular thing you want built.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/