From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Subject: Makefile: COPTS vs CFLAGS
Date: Fri, 29 Jul 2005 15:40:11 +0200 [thread overview]
Message-ID: <20050729134011.GD21909@pasky.ji.cz> (raw)
Hello,
one more thing - should we keep the $COPTS variable? Most projects
(including Cogito) have the C flags controlled by the $CFLAGS variable.
What I would propose:
-COPTS=-g -O2
-CFLAGS=$(COPTS) -Wall
+CFLAGS?=-g -O2
+CFLAGS+=-Wall
That is, if user does not specify custom $CFLAGS, default to "-g -O2",
and always append -Wall (and more after I'll send my Makefile patches).
Opinions?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
next reply other threads:[~2005-07-29 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 13:40 Petr Baudis [this message]
2005-07-29 14:03 ` Makefile: COPTS vs CFLAGS Timo Hirvonen
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=20050729134011.GD21909@pasky.ji.cz \
--to=pasky@suse.cz \
--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