From 281c4728d6d5b5eb02d2e08783b8ca1a090ea730 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 19 Jan 2015 10:14:16 -0800 Subject: [PATCH] dev-manual: Edits to add more detail to where patch files are Updated some text to indicate that you should put patch files in $BP, $BPN, or "files." Also, added more on how the patch files suffix is (i.e. accounting for compressed suffix names like diff.bz). Reported-by: Robert P. J. Day (From yocto-docs rev: d9e23da24e9d86ec5e2b9d4067667478f3e56ba1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 2319be1d84..4696dd5d76 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1935,7 +1935,9 @@ fetched. Any files mentioned in SRC_URI whose names end in .patch or - .diff are treated as patches. + .diff or compressed versions of these + suffixes (e.g. diff.gz are treated as + patches. The do_patch task automatically applies these patches. @@ -1959,7 +1961,9 @@ using file://, you should place patch files in a directory next to the recipe either named the same as the base name of the recipe - (BPN), + (BP + and + BPN) or "files".