From 47fb722475940917114a6447ae2cc13d768970e4 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 17 Apr 2013 10:09:10 -0700 Subject: ref-manual: Edits to clear up the SRC_URI variable description. I found it confusing due to not specifically accounting for .bb and .bbappend files. I added some wording to clearly specify use given the two types of "recipes". Specifically, if you are going to use a SRC_URI statment from an append file, the user really should be aware that they will need to extend the FILESPATH variable by also using FILESEXTRAPATHS from within that append file. (From yocto-docs rev: 8fd0047bd5c4598532afc6f0803f6ae23fa213b2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 57 ++++++++++++++++++++---------- 1 file changed, 39 insertions(+), 18 deletions(-) (limited to 'documentation') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index e4bcb56aed..1a751a9758 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -3368,36 +3368,57 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" SRC_URI The list of source files - local or remote. - This variable tells the OpenEmbedded build system which bits to pull - in for the build and how to pull them in. - For example, if the recipe only needs to fetch a tarball from the - Internet, the recipe uses a single SRC_URI entry. - On the other hand, if the recipe needs to fetch a tarball, apply - two patches, and include a custom file, the recipe would include four + This variable tells the OpenEmbedded build system which bits + to pull in for the build and how to pull them in. + For example, if the recipe or append file only needs to + fetch a tarball from the Internet, the recipe or + append file uses a single SRC_URI + entry. + On the other hand, if the recipe or append file needs to + fetch a tarball, apply two patches, and include a custom + file, the recipe or append file would include four instances of the variable. The following list explains the available URI protocols: - file:// - Fetches files, which is usually - a file shipped with the + file:// - + Fetches files, which are usually files shipped with + the Metadata, from the local machine. The path is relative to the FILESPATH variable. - Thus, the build system searches, in order, from the following directories, - which are assumed to be a subdirectories of the directory in which the - recipe file resides: + Thus, the build system searches, in order, from the + following directories, which are assumed to be a + subdirectories of the directory in which the + recipe file (.bb) or + append file (.bbappend) + resides: + + If you want the build system to pick up files + specified through a + SRC_URI + statement from your append file, you need to be + sure to extend the + FILESPATH + variable by also using the + FILESEXTRAPATHS + variable from within your append file. + - ${BPN} - The - base recipe name without any special suffix or version numbers. + ${BPN} - + The base recipe name without any special + suffix or version numbers. ${BP} - ${BPN}-${PV}. - The base recipe name and version but without any special - package name suffix. - files - Files within a - directory, which is named files - and is also alongside the recipe. + The base recipe name and version but without + any special package name suffix. + + files - + Files within a directory, which is named + files and is also + alongside the recipe or append file. bzr:// - Fetches files from a -- cgit v1.2.3-54-g00ecf