Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] kmod: add option to install module utilities
Date: Thu, 22 Mar 2012 16:17:03 +0100	[thread overview]
Message-ID: <4F6B426F.1000509@free-electrons.com> (raw)
In-Reply-To: <20120322150326.7CEA39693E@busybox.osuosl.org>

Hi Peter,

Maybe we should also deprecate modules-init-tools, since Jon Masters
announced some time ago that it was no longer maintained and people
should go to kmod utils ?

Le 22/03/2012 16:03, Peter Korsgaard a ?crit :
> commit: http://git.buildroot.net/buildroot/commit/?id=78f5ac2908b30aa6f67583a355e058d6703755ac
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> 
> And ensure optional zlib+xz dependencies gets picked up.
> 
> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
> ---
>  package/kmod/Config.in |    6 ++++++
>  package/kmod/kmod.mk   |   26 ++++++++++++++++++++++++++
>  2 files changed, 32 insertions(+), 0 deletions(-)
> 
> diff --git a/package/kmod/Config.in b/package/kmod/Config.in
> index c5e8ca8..6fdd92c 100644
> --- a/package/kmod/Config.in
> +++ b/package/kmod/Config.in
> @@ -4,3 +4,9 @@ config BR2_PACKAGE_KMOD
>  	  handle kernel modules
>  
>  	  http://git.kernel.org/?p=utils/kernel/kmod/kmod.git
> +
> +config BR2_PACKAGE_KMOD_TOOLS
> +	bool "kmod utilities"
> +	help
> +	  Install kmod module utilities (depmod, insmod, lsmod,
> +	  modinfo, modprobe, rmmod).
> diff --git a/package/kmod/kmod.mk b/package/kmod/kmod.mk
> index f71087c..55cbdbb 100644
> --- a/package/kmod/kmod.mk
> +++ b/package/kmod/kmod.mk
> @@ -4,4 +4,30 @@ KMOD_SITE = $(BR2_KERNEL_MIRROR)/linux/utils/kernel/kmod/
>  KMOD_INSTALL_STAGING = YES
>  KMOD_DEPENDENCIES = host-pkg-config
>  
> +ifeq ($(BR2_PACKAGE_ZLIB),y)
> +KMOD_DEPENDENCIES += zlib
> +KMOD_CONF_OPT += --with-zlib
> +endif
> +
> +ifeq ($(BR2_PACKAGE_XZ),y)
> +KMOD_DEPENDENCIES += xz
> +KMOD_CONF_OPT += --with-xz
> +endif
> +
> +ifeq ($(BR2_PACKAGE_KMOD_TOOLS),y)
> +# take precedence over busybox / module-init-tools implementations
> +KMOD_DEPENDENCIES += \
> +	$(if $(BR2_PACKAGE_BUSYBOX),busybox) \
> +	$(if $(BR2_PACKAGE_MODULE_INIT_TOOLS),module-init-tools)
> +
> +define KMOD_INSTALL_TOOLS
> +	for i in depmod insmod lsmod modinfo modprobe rmmod; \
> +	do ln -sf ../usr/bin/kmod $(TARGET_DIR)/sbin/$$i; done
> +endef
> +
> +KMOD_POST_INSTALL_TARGET_HOOKS += KMOD_INSTALL_TOOLS
> +else
> +KMOD_CONF_OPT += --disable-tools
> +endif
> +
>  $(eval $(call AUTOTARGETS))
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


-- 
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-03-22 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 15:03 [Buildroot] [git commit] kmod: add option to install module utilities Peter Korsgaard
2012-03-22 15:17 ` Maxime Ripard [this message]
2012-03-22 15:39   ` Peter Korsgaard
2012-03-22 15:47     ` Thomas Petazzoni
2012-03-22 21:37 ` Arnout Vandecappelle
2012-03-22 21:48   ` Peter Korsgaard
2012-03-22 22:15     ` Arnout Vandecappelle

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=4F6B426F.1000509@free-electrons.com \
    --to=maxime.ripard@free-electrons.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