linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@gmail.com>
To: Linux-Sparse <linux-sparse@vger.kernel.org>
Cc: "Diego Elio Pettenò" <flameeyes@gmail.com>
Subject: [PATCH 2/3] build: add an all-installable target that builds the targets to install.
Date: Wed, 13 Apr 2011 13:06:05 +0200	[thread overview]
Message-ID: <1302692766-30217-2-git-send-email-flameeyes@gmail.com> (raw)
In-Reply-To: <1302692766-30217-1-git-send-email-flameeyes@gmail.com>

This is useful for distributions that don't want to build content that
won't be installed.
---
 Makefile |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/Makefile b/Makefile
index e08143a..ffb513f 100644
--- a/Makefile
+++ b/Makefile
@@ -118,7 +118,9 @@ SED_PC_CMD = 's|@version@|$(VERSION)|g;		\
 
 all: $(PROGRAMS) sparse.pc
 
-install: $(INST_PROGRAMS) $(LIBS) $(LIB_H) sparse.pc
+all-installable: $(INST_PROGRAMS) $(LIBS) $(LIB_H) sparse.pc
+
+install: all-installable
 	$(Q)install -d $(DESTDIR)$(BINDIR)
 	$(Q)install -d $(DESTDIR)$(LIBDIR)
 	$(Q)install -d $(DESTDIR)$(MAN1DIR)
-- 
1.7.5.rc1


  reply	other threads:[~2011-04-13 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 11:06 [PATCH 1/3] build: allow easy override of GCC_BASE Diego Elio Pettenò
2011-04-13 11:06 ` Diego Elio Pettenò [this message]
2011-04-13 18:34   ` [PATCH 2/3] build: add an all-installable target that builds the targets to install Josh Triplett
2011-04-13 18:35     ` Diego Elio Pettenò
2011-04-13 11:06 ` [PATCH 3/3] Fix build with GCC 4.6 series Diego Elio Pettenò
2011-04-14  9:58   ` Christopher Li
2011-04-14  9:59 ` [PATCH 1/3] build: allow easy override of GCC_BASE Christopher Li

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=1302692766-30217-2-git-send-email-flameeyes@gmail.com \
    --to=flameeyes@gmail.com \
    --cc=linux-sparse@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;
as well as URLs for NNTP newsgroup(s).