All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mierswa <impulze@impulze.org>
To: linux-media@vger.kernel.org
Subject: [RFC PATCH] prevent building/installation of various utilities
Date: Tue, 01 Feb 2011 07:02:49 +0100	[thread overview]
Message-ID: <4D47A209.4060805@impulze.org> (raw)

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

Heya, I wanted to provide a patch to have the ability to _not_ build
and install various tools even if the requirements are met.

-- 
Mierswa, Daniel

If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
               --- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22

[-- Attachment #2: 0001-make-compilation-installation-of-some-utils-configur.patch --]
[-- Type: text/plain, Size: 981 bytes --]

>From 9e0771185011dedd3969dd084f0e2b9a2b23da27 Mon Sep 17 00:00:00 2001
From: Daniel Mierswa <impulze@impulze.org>
Date: Tue, 1 Feb 2011 05:38:55 +0100
Subject: [PATCH] make compilation/installation of some utils configurable

---
 utils/Makefile |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/utils/Makefile b/utils/Makefile
index bcce0fe..25ff7c3 100644
--- a/utils/Makefile
+++ b/utils/Makefile
@@ -5,11 +5,14 @@ all install:
 		$(MAKE) -C $$i $@ || exit 1; \
 	done
 
+ifneq ($(USE_SYSFS_PATH),no)
 	# Test if libsysfs is installed
 	@-if [ -f /usr/include/sysfs/libsysfs.h ]; then \
 		$(MAKE) -C v4l2-sysfs-path $@; \
 	fi
+endif
 
+ifneq ($(USE_QV4L2),no)
 	# Test whether qmake is installed, and whether it is for qt4.
 	@if which qmake-qt4 >/dev/null 2>&1; then \
 		QMAKE=qmake-qt4; \
@@ -24,6 +27,7 @@ all install:
 			$(MAKE) -C qv4l2 -f Makefile.install $@; \
 		fi \
 	fi
+endif
 
 sync-with-kernel:
 	$(MAKE) -C keytable $@
-- 
1.7.3.5


             reply	other threads:[~2011-02-01  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  6:02 Daniel Mierswa [this message]
2011-02-06 15:02 ` [RFC PATCH] prevent building/installation of various utilities Daniel Mierswa

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=4D47A209.4060805@impulze.org \
    --to=impulze@impulze.org \
    --cc=linux-media@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.