From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 5 v2] Makefile.package.in: add utility functions find*clauses and notfirstword
Date: Thu, 17 Nov 2011 20:50:10 +0100 [thread overview]
Message-ID: <20111117205010.60a99ee3@skate> (raw)
In-Reply-To: <b6579582d02dd802adca.1321557990@devws108>
Le Thu, 17 Nov 2011 20:41:48 +0100,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> Functions finddirclauses and findfileclauses help in building a find
> command that skips a set of directories and performs operations on a
> set of files. This pattern can for example be used to keep certain
> files or directories from being stripped, or to remove certain files
> from a package installation.
I must say I am not a big fan of this. Those macros are horribly
complicated to understand and they make the code really cryptic. I
think I would really prefer to see the implementation of these "do not
strip this file/directory" option to be done without those cryptic
macros.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-11-17 19:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 19:41 [Buildroot] [PATCH 0 of 5 v2] Add find utility functions / exclude files from strip / reduce python Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 1 of 5 v2] Makefile.package.in: add utility functions find*clauses and notfirstword Thomas De Schampheleire
2011-11-17 19:50 ` Thomas Petazzoni [this message]
2011-11-17 20:19 ` Thomas De Schampheleire
2011-11-18 0:10 ` Arnout Vandecappelle
2011-11-18 9:41 ` Thomas De Schampheleire
2011-11-19 7:13 ` Cam Hutchison
2011-11-21 8:42 ` Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 2 of 5 v2] stripping: use findfileclauses utility function Thomas De Schampheleire
2011-11-18 0:06 ` Arnout Vandecappelle
2011-11-18 1:46 ` Cam Hutchison
2011-11-18 6:21 ` Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 3 of 5 v2] build: add option to exclude executables/dirs from being stripped Thomas De Schampheleire
2011-11-17 19:42 ` [Buildroot] [PATCH 4 of 5 v2] python config: move configuration into menu Thomas De Schampheleire
2011-11-17 19:42 ` [Buildroot] [PATCH 5 of 5 v2] python: allow reduced installation Thomas De Schampheleire
2011-11-17 19:55 ` Thomas Petazzoni
2011-11-18 0:24 ` Arnout Vandecappelle
2011-11-18 7:59 ` 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=20111117205010.60a99ee3@skate \
--to=thomas.petazzoni@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