From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4 of 7] uclibc: only add kconfig targets if uclibc is enabled
Date: Thu, 24 Jul 2014 19:49:31 +0200 [thread overview]
Message-ID: <80c907c0dfca068ee3b1.1406224171@localhost> (raw)
In-Reply-To: <patchbomb.1406224167@localhost>
In analogy of linux.mk, only enable the kconfig targets (menuconfig,
update-config, ...) when the uclibc package is actually enabled.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
package/uclibc/uclibc.mk | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff -r ec98df5449b0 -r 80c907c0dfca package/uclibc/uclibc.mk
--- a/package/uclibc/uclibc.mk Tue Jul 22 20:35:36 2014 +0200
+++ b/package/uclibc/uclibc.mk Wed Jul 23 20:12:32 2014 +0200
@@ -533,6 +533,8 @@
$(eval $(generic-package))
+ifeq ($(BR2_TOOLCHAIN_BUILDROOT_UCLIBC),y)
+
UCLIBC_KCONFIG_FILE = $(UCLIBC_CONFIG_FILE)
UCLIBC_KCONFIG_OPT = \
$(UCLIBC_MAKE_FLAGS) \
@@ -542,5 +544,7 @@
$(eval $(kconfig-package))
+endif
+
# Before uClibc is built, we must have the second stage cross-compiler
$(UCLIBC_TARGET_BUILD): | host-gcc-intermediate
next prev parent reply other threads:[~2014-07-24 17:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 17:49 [Buildroot] [PATCH 0 of 7] Introduction of kconfig-package infrastructure Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 1 of 7] infra: introduce a " Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 2 of 7] uclibc: use $(MAKE) iso $(MAKE1) for menuconfig target Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 3 of 7] uclibc: convert to kconfig-package infrastructure Thomas De Schampheleire
2014-07-24 17:49 ` Thomas De Schampheleire [this message]
2014-07-24 17:49 ` [Buildroot] [PATCH 5 of 7] busybox: " Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 6 of 7] busybox: only add kconfig targets if uclibc is enabled Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 7 of 7] linux: remove support of linux26-* targets Thomas De Schampheleire
2014-07-29 21:52 ` [Buildroot] [PATCH 0 of 7] Introduction of kconfig-package infrastructure Thomas Petazzoni
2014-07-30 17:58 ` Thomas De Schampheleire
2014-07-30 19:23 ` Thomas Petazzoni
2014-07-30 20:01 ` Thomas De Schampheleire
2014-07-31 6:57 ` Jeremy Rosen
2014-07-31 8:03 ` Thomas De Schampheleire
2014-07-31 8:20 ` Jeremy Rosen
2014-07-31 12:54 ` Matthew Weber
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=80c907c0dfca068ee3b1.1406224171@localhost \
--to=patrickdepinguin@gmail.com \
--cc=buildroot@busybox.net \
/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