From: Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 2 v4-resend] Add find utility functions / exclude files from strip
Date: Wed, 14 Mar 2012 17:45:05 +0100 [thread overview]
Message-ID: <patchbomb.1331743505@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.
Thanks to input from Arnout, the find functions are now much simpler and
should be clearly understandable by everyone.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
v4: simplify find functions even further; whitespace changes
v3: update based on review comments, remove Python changes for now
v2: simplify find functions
Config.in | 19 +++++++++++++++++++
Makefile | 10 ++++++++--
package/Makefile.package.in | 10 ++++++++++
3 files changed, 37 insertions(+), 2 deletions(-)
next reply other threads:[~2012-03-14 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 16:45 Thomas De Schampheleire [this message]
2012-03-14 16:45 ` [Buildroot] [PATCH 1 of 2 v4-resend] Makefile.package.in: add utility functions find*clauses and notfirstword Thomas De Schampheleire
2012-03-23 14:53 ` Thomas De Schampheleire
2012-05-04 19:17 ` Thomas De Schampheleire
2012-05-04 20:27 ` Arnout Vandecappelle
2012-05-05 7:11 ` Thomas De Schampheleire
2012-03-14 16:45 ` [Buildroot] [PATCH 2 of 2 v4-resend] build: add option to exclude executables/dirs from being stripped Thomas De Schampheleire
2012-03-23 14:53 ` Thomas De Schampheleire
2012-05-04 19:16 ` Thomas De Schampheleire
2012-03-23 14:53 ` [Buildroot] [PATCH 0 of 2 v4-resend] Add find utility functions / exclude files from strip Thomas De Schampheleire
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.1331743505@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