From: Darren Hart <dvhart@linux.intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
Chris Larson <clarson@kergoth.com>,
"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Subject: Re: Documentation: Default FILESDIR
Date: Thu, 01 Mar 2012 11:17:28 -0800 [thread overview]
Message-ID: <4F4FCB48.4070200@linux.intel.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123793B741DAC@ORSMSX101.amr.corp.intel.com>
On 03/01/2012 07:36 AM, Rifenbark, Scott M wrote:
> Darren,
>
> Please look at
> http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#platdev-appdev-insitu
> in the YP Reference manual. This is the section you refer to in this
> mail. The link in this latest version correctly goes to the
> referenced Quilt section, which has significantly changed. The
> little paragraph you quote below is now basically part of the 9-step
> Quilt process in the YP Dev manual
> (http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#using-a-quilt-workflow).
OK, this does cover where to put the patch. However, someone looking to
write a recipe when they already have the patches they want may not
think to look for how to do this in a "Using a Quilt Workflow" section.
I think we should have a blurb about this in a section about writing
recipes:
"Add any additional files and patches referenced in the SRC_URI in the
same directory as the recipe so bitbake can find them."
>
> Can you look at these two sections now and then provide me with
> FILESPATH information so I can create a glossary entry for the item
> and possibly work the use of FILESPATH into the updated Quilt
> section?
I don't know that I'm the best person to define these... however, this
is my understanding, someone else should confirm:
FILESPATH: The ":" delimited set of paths that bitbake will search for
files referenced in the SRC_URI. Defaults to ".:files:${PN}".
FILESEXTRAPATHS: Appends a ":" delimited set of paths to FILESPATH. This
is intended for use in .bbappend files to include any additional files
provided in that layer. This is typically done as:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
As an aside, it might be nice to make this 'FILESEXTRAPATHS_prepend :=
"${THISDIR}/${PN}:"' the default for bbappend files. Although I imagine
there are good reasons for why it is the way it is.
--
Darren
>
> Thanks, Scott
>
> -----Original Message----- From: Darren Hart
> [mailto:dvhart@linux.intel.com] Sent: Wednesday, February 29, 2012
> 6:40 PM To: Chris Larson Cc: Yocto Project; Perez-Gonzalez, Inaky;
> Rifenbark, Scott M Subject: Re: [yocto] Documentation: Default
> FILESDIR
>
>
>
> On 02/29/2012 04:27 PM, Chris Larson wrote:
>> On Wed, Feb 29, 2012 at 5:11 PM, Darren Hart
>> <dvhart@linux.intel.com> wrote:
>>> When a new user goes to write a recipe and add a patch or other
>>> file, they need to understand FILESDIR and where to put these
>>> additional files. I scanned the reference manual and the dev
>>> manual and came up mostly empty handed. The one glipse of it is
>>> in section 5.1.4 of the Reference Manual:
>>>
>>> " It is useful when making changes directly to the work directory
>>> files to do so using the Quilt tool as detailed in the Modifying
>>> Package Source Code with Quilt section. Using Quilt, you can copy
>>> patches into the recipe directory and use the patches directly
>>> through use of the SRC_URI variable. "
>>>
>>> Unfortunately, this doesn't say where the recipe directory is and
>>> what it should be named.
>>>
>>> Is this documented somewhere that I missed? If not, Scott can you
>>> add this task to your list of doc gaps?
>>
>> FILESDIR hasn't actually been used (or, shouldn't have been) for
>> years. FILESPATH replaced it.
>
> Sorry, I should have said FILESPATH - that's what I get for not
> looking it up. The situation is unchanged though.
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-03-01 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 0:11 Documentation: Default FILESDIR Darren Hart
2012-03-01 0:27 ` Chris Larson
2012-03-01 0:39 ` Darren Hart
2012-03-01 15:36 ` Rifenbark, Scott M
2012-03-01 15:47 ` Paul Eggleton
2012-03-01 19:17 ` Darren Hart [this message]
2012-03-05 11:19 ` Joshua Immanuel
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=4F4FCB48.4070200@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=clarson@kergoth.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.