From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Makefile: do not optimize when DEBUG=1
Date: Wed, 07 Mar 2007 10:26:38 +0100 [thread overview]
Message-ID: <45EE854E.210EDAFF@eudaptics.com> (raw)
In-Reply-To: Pine.LNX.4.63.0703062249540.22628@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> You can do that now by removing just the object files containing the
> code you want to debug, and saying "make DEBUG=1".
> [...]
> -CFLAGS = -g -O2 -Wall
> +CFLAGS = -g -Wall
> +ifndef DEBUG
> + CFLAGS += -O2
> +endif
I think the shortcut to remove just the interesting object file does not
work because Makefile notices (the GIT-CFLAGS rule) that there are "new
flags or prefix", and so recompiles everything.
-- Hannes
next prev parent reply other threads:[~2007-03-07 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 21:50 [PATCH] Makefile: do not optimize when DEBUG=1 Johannes Schindelin
2007-03-07 9:26 ` Johannes Sixt [this message]
2007-03-07 12:37 ` Johannes Schindelin
2007-03-07 13:41 ` [PATCH] Avoid rebuilding everything if user changes CFLAGS on the make command line Johannes Sixt
2007-03-07 18:01 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45EE854E.210EDAFF@eudaptics.com \
--to=j.sixt@eudaptics.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox