From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: what exactly is the proper way to use FILESEXTRAPATHS?
Date: Thu, 06 Dec 2012 23:15:35 +0000 [thread overview]
Message-ID: <1354835735.12928.15.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1212061522350.31684@oneiric>
On Thu, 2012-12-06 at 15:27 -0500, Robert P. J. Day wrote:
> continuing my trek through coding pedantry and was wondering about
> the exact purpose of the common line in .bbappend files:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>
> or some slight variation thereof.
>
> i *thought* i knew what it did, so i did a small experiment with the
> meta-ti layer and netbase (since i was already messing around with
> it), and i replaced the contents of the netbase .bbappend file with
> the single line:
>
> FILESEXTRAPATHS_prepend := "rday"
>
> and checked the environment for the value of FILESPATH for the netbase
> recipe and, after formatting to read it clearly, what i saw was:
>
> FILESPATH="rday/linux-gnueabi
> rday/arm
> rday/build-linux
> rday/pn-netbase
> rday/beagleboard
> rday/omap3
> rday/armv7a
> rday/
> rday/class-target
> rday/forcevariable
> rday/libc-glibc
> rday/
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/linux-gnueabi
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/arm
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/build-linux
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/pn-netbase
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/beagleboard
> /home/rpjday/OE/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/omap3
> ... snip ...
>
> what the heck? if that's what FILESEXTRAPATHS is supposed to do,
> that is definitely *not* how it's being used in many, many bbappend
> files.
>
> is there an explanation somewhere as to what the above is supposed
> to represent?
What is puzzling about the above? Its doing what it was designed to do.
The idea is to add the directory listed to the set of directories that
get "autogenerated" from OVERRIDES as search locations. What did you
expect it to do?
FWIW there is no need to use := with FILESEXTRAPATHS, or prepend for
that matter, just use +=/=+.
Cheers,
Richard
next prev parent reply other threads:[~2012-12-06 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 20:27 what exactly is the proper way to use FILESEXTRAPATHS? Robert P. J. Day
2012-12-06 23:15 ` Richard Purdie [this message]
2012-12-06 23:20 ` Robert P. J. Day
2012-12-07 16:11 ` Richard Purdie
2012-12-07 16:16 ` Robert P. J. Day
2012-12-07 17:09 ` Robert P. J. Day
2012-12-07 23:58 ` Rifenbark, Scott M
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=1354835735.12928.15.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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