linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Samuel Bronson <naesten@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 4/4] Have Makefile import config.mak if it exists.
Date: Tue, 2 Jun 2009 13:30:48 -0700	[thread overview]
Message-ID: <70318cbf0906021330n7d0df47y5010dd158f731966@mail.gmail.com> (raw)
In-Reply-To: <1243881445-30069-4-git-send-email-naesten@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 338 bytes --]

On Mon, Jun 1, 2009 at 11:37 AM, Samuel Bronson <naesten@gmail.com> wrote:
> This will allow users to override build settings without dirtying their
> trees, making life with `git stash' a bit easier.
>
I modify the patch to use "local.mk" and add it in .gitignore.

If that works for you, I am going to apply it as yours.

Thanks

Chris

[-- Attachment #2: 4-4-Have-Makefile-import-config.mak-if-it-exists..patch --]
[-- Type: application/octet-stream, Size: 1582 bytes --]

From patchwork Mon Jun  1 18:37:25 2009
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [4/4] Have Makefile import config.mak if it exists.
Date: Mon, 01 Jun 2009 18:37:25 -0000
From: Samuel Bronson <naesten@gmail.com>
X-Patchwork-Id: 27264

This will allow users to override build settings without dirtying their
trees, making life with `git stash' a bit easier.

Signed-off-by: Samuel Bronson <naesten@gmail.com>

---
Makefile |   10 ++++++++--
 1 files changed, 8 insertions(+), 2 deletions(-)

Index: sparse.chrisl/Makefile
===================================================================
--- sparse.chrisl.orig/Makefile
+++ sparse.chrisl/Makefile
@@ -10,9 +10,10 @@ LDFLAGS += -g
 AR = ar
 
 #
-# For debugging, uncomment the next one
+# For debugging, put this in local.mk:
+#
+#     CFLAGS += -O0 -DDEBUG -g3 -gdwarf-2
 #
-#CFLAGS += -O0 -DDEBUG -g3 -gdwarf-2
 
 HAVE_LIBXML=$(shell pkg-config --exists libxml-2.0 && echo 'yes')
 HAVE_GCC_DEP=$(shell touch .gcc-test.c && 				\
@@ -89,6 +90,11 @@ SED_PC_CMD = 's|@version@|$(VERSION)|g;	
 	      s|@includedir@|$(INCLUDEDIR)|g'
 
 
+
+# Allow users to override build settings without dirtying their trees
+-include local.mk
+
+
 all: $(PROGRAMS) sparse.pc
 
 install: $(INST_PROGRAMS) $(LIBS) $(LIB_H) sparse.pc
Index: sparse.chrisl/.gitignore
===================================================================
--- sparse.chrisl.orig/.gitignore
+++ sparse.chrisl/.gitignore
@@ -33,3 +33,7 @@ patches-*
 # quilt's files
 patches
 series
+
+# local makefile
+local.mk
+

  reply	other threads:[~2009-06-02 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1243881445-30069-1-git-send-email-naesten@gmail.com>
2009-06-01 18:37 ` [PATCH-v2 2/4] Replace SYM_ and MOD_ #defines with enums in symbol.h Samuel Bronson
     [not found]   ` <1243881445-30069-3-git-send-email-naesten@gmail.com>
2009-06-01 18:37     ` [PATCH 4/4] Have Makefile import config.mak if it exists Samuel Bronson
2009-06-02 20:30       ` Christopher Li [this message]
2009-06-03  0:37         ` Samuel Bronson
2009-06-02 20:44   ` [PATCH-v2 2/4] Replace SYM_ and MOD_ #defines with enums in symbol.h Christopher Li
2009-06-03  3:43     ` Samuel Bronson

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=70318cbf0906021330n7d0df47y5010dd158f731966@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=naesten@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).