From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: "${bindir}" versus "${bindir}/*" ??
Date: Sat, 24 Mar 2012 09:45:59 +0000 [thread overview]
Message-ID: <1332582359.9740.489.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1203240436510.20052@oneiric>
On Sat, 2012-03-24 at 04:40 -0400, Robert P. J. Day wrote:
> in bitbake.conf, numerous variables like "FILES_${PN}" are
> initialized with a combination of directory variables, with two
> different forms:
>
> * ${bindir}
> * ${bindir}/*
>
> is there a functional difference between those two? my wildly
> speculative guess is that if "*" works as it does in the shell, it
> would simply skip any hidden objects. is that the difference? since
> i don't see that clarified anywhere.
The former is recursive and the latter is not and will just match files
in the directory (unhidden ones at that).
Cheers,
Richard
next prev parent reply other threads:[~2012-03-24 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 8:40 "${bindir}" versus "${bindir}/*" ?? Robert P. J. Day
2012-03-24 9:45 ` Richard Purdie [this message]
2012-03-24 10:01 ` Robert P. J. Day
2012-03-24 11:26 ` Richard Purdie
2012-03-24 12:37 ` Robert P. J. Day
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=1332582359.9740.489.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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