Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cam Hutchison <camh@xdna.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 5 v2] Makefile.package.in: add utility functions find*clauses and notfirstword
Date: Sat, 19 Nov 2011 07:13:34 -0000	[thread overview]
Message-ID: <172e.4ec7571e.5a6e@getafix.xdna.net> (raw)
In-Reply-To: b6579582d02dd802adca.1321557990@devws108

Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> writes:

Apologies if you have seen this, but I haven't seen my response to this
come through (probably a gmane stuffup).

>+# finddirclauses: creates "-wholename 'basedir/dirX' -o -wholename 'basedir/dirY'"
>+# [1:basedir, 2:namelist]
>+finddirclauses=-wholename '$(firstword $(2))' $(patsubst %,-o -wholename '$(1)/%',$(call notfirstword,$(2)))

I think the first -wholename argument is meant to be
  '$(1)/$(firstword $(2))'

according to the comment above it.

Also, my man page for find(1) says this about -wholename:
  See -path.    This alternative is less portable than -path.

Do you find -wholename to be more readable? It's not an option I've used
much, so I need to look up the man page anyway, but -path is easier to
look up because you do not get redirected to another option like you do
with -wholename.

  parent reply	other threads:[~2011-11-19  7:13 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
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 [this message]
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=172e.4ec7571e.5a6e@getafix.xdna.net \
    --to=camh@xdna.net \
    --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