From: Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 2 v3-resend] Add find utility functions / exclude files from strip
Date: Thu, 09 Feb 2012 21:09:28 +0100 [thread overview]
Message-ID: <patchbomb.1328818168@beantl019720> (raw)
This patch series adds a few utility functions to Makefile.package.in that
help in composing find commands, and uses these functions to exclude
user-configured files and directories from being stripped in target-finalize.
The previous version of this series also modified the Python configuration to
allow for a 'reduced Python'. These patches were left out for now, as Thomas
Petazzoni raised some objections regarding the two-faced configuration. I hope
we can continue the discussion about this topic in that thread.
Thomas, you also had comments on the complexity of the find*clauses functions.
If you have alternative suggestions, please let me know. Thanks.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
v3: update based on review comments, remove Python changes for now
v2: simplify find utilities
Config.in | 19 +++++++++++++++++++
Makefile | 9 +++++++--
package/Makefile.package.in | 11 +++++++++++
3 files changed, 37 insertions(+), 2 deletions(-)
next reply other threads:[~2012-02-09 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 20:09 Thomas De Schampheleire [this message]
2012-02-09 20:09 ` [Buildroot] [PATCH 1 of 2 v3-resend] Makefile.package.in: add utility functions find*clauses and notfirstword Thomas De Schampheleire
2012-02-11 16:57 ` Arnout Vandecappelle
2012-02-15 8:10 ` Thomas De Schampheleire
2012-02-09 20:09 ` [Buildroot] [PATCH 2 of 2 v3-resend] build: add option to exclude executables/dirs from being stripped Thomas De Schampheleire
2012-02-11 17:05 ` 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=patchbomb.1328818168@beantl019720 \
--to=patrickdepinguin+buildroot@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