Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] patch to allow selection of e2fsprogs tools to install
Date: Wed, 20 Feb 2008 07:28:55 +0100	[thread overview]
Message-ID: <007d01c8738a$903f7ca0$f4031a0a@atmel.com> (raw)
In-Reply-To: 20080220061811.GA8033@cloud.net.au


----- Original Message ----- 
From: "Hamish Moffatt" <hamish@cloud.net.au>
To: <buildroot@uclibc.org>
Sent: Wednesday, February 20, 2008 7:18 AM
Subject: [Buildroot] patch to allow selection of e2fsprogs tools to install


> Any objection to the following patch, which allows choice of which
> e2fsprogs tools to install (a la package/mtd and others)?
> 
> I wish there were a better way to write the makefile other than a ton of
> ifneq/endif lines. I suspect some sort of macro and $(call ..) could do
> it.
> 
> I only omit tools at install time, not build time. This allows you to
> build multiple projects with different tool selections if you wanted.
> Plus, e2fsprogs does not support disabling most tools at build time.
> 
> Hamish
>

Something similar to:

EF2FS_RM-$(strip $(BR2_PACKAGE_E2FSPROGS_BADBLOCKS)) += ${TARGET_DIR}/sbin/badblocks

for all configs should create a list of files to remove and another list of files to keep.

The "rm -rf" all files in the list 

Best Regards
Ulf Samuelsson

  reply	other threads:[~2008-02-20  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20  6:18 [Buildroot] patch to allow selection of e2fsprogs tools to install Hamish Moffatt
2008-02-20  6:28 ` Ulf Samuelsson [this message]
2008-02-21  1:38   ` Hamish Moffatt
2008-02-21  4:36     ` [Buildroot] patch to allow selection of e2fsprogs tools toinstall Ulf Samuelsson
2008-02-21  5:20       ` Hamish Moffatt

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='007d01c8738a$903f7ca0$f4031a0a@atmel.com' \
    --to=ulf@atmel.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