diff options
-rw-r--r-- | documentation/overview-manual/overview-manual-concepts.xml | 37 |
1 files changed, 26 insertions, 11 deletions
diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml index 679d58ca9d..d3314cbfcc 100644 --- a/documentation/overview-manual/overview-manual-concepts.xml +++ b/documentation/overview-manual/overview-manual-concepts.xml | |||
@@ -1239,22 +1239,25 @@ | |||
1239 | </para> | 1239 | </para> |
1240 | 1240 | ||
1241 | <para> | 1241 | <para> |
1242 | The | 1242 | The <filename>do_patch</filename> task processes recipes by |
1243 | <ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-patch'><filename>do_patch</filename></ulink> | 1243 | using the |
1244 | task processes recipes by using the | ||
1245 | <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink> | 1244 | <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink> |
1246 | variable to locate applicable patch files, which by default | 1245 | variable to locate applicable patch files. |
1247 | are <filename>*.patch</filename> or | 1246 | Default processing for patch files assumes the files have |
1248 | <filename>*.diff</filename> files, or any file if | 1247 | either <filename>*.patch</filename> or |
1249 | "apply=yes" is specified for the file in | 1248 | <filename>*.diff</filename> endings. |
1250 | <filename>SRC_URI</filename>. | 1249 | You can use <filename>SRC_URI</filename> parameters to |
1250 | change the way the build system recognizes patch files. | ||
1251 | See the | ||
1252 | <ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-patch'><filename>do_patch</filename></ulink> | ||
1253 | task for more information. | ||
1251 | </para> | 1254 | </para> |
1252 | 1255 | ||
1253 | <para> | 1256 | <para> |
1254 | BitBake finds and applies multiple patches for a single | 1257 | BitBake finds and applies multiple patches for a single |
1255 | recipe in the order in which it finds the patches. | 1258 | recipe in the order in which it locates the patches. |
1256 | Patches are applied to the recipe's source files located | 1259 | Patches are applied to the recipe's source files, which |
1257 | in the | 1260 | are located in the |
1258 | <ulink url='&YOCTO_DOCS_REF_URL;#var-S'><filename>S</filename></ulink> | 1261 | <ulink url='&YOCTO_DOCS_REF_URL;#var-S'><filename>S</filename></ulink> |
1259 | directory. | 1262 | directory. |
1260 | </para> | 1263 | </para> |
@@ -1264,6 +1267,18 @@ | |||
1264 | created, see the | 1267 | created, see the |
1265 | "<link linkend='source-fetching-dev-environment'>Source Fetching</link>" | 1268 | "<link linkend='source-fetching-dev-environment'>Source Fetching</link>" |
1266 | section. | 1269 | section. |
1270 | For more information on how to create patches and how the | ||
1271 | build system processes patches, see the | ||
1272 | "<ulink url='&YOCTO_DOCS_DEV_URL;#new-recipe-patching-code'>Patching Code</ulink>" | ||
1273 | section in the Yocto Project Development Tasks Manual. | ||
1274 | You can also see the | ||
1275 | "<ulink url='&YOCTO_DOCS_SDK_URL;#sdk-devtool-use-devtool-modify-to-modify-the-source-of-an-existing-component'>Use <filename>devtool modify</filename> to Modify the Source of an Existing Component</ulink>" | ||
1276 | section in the Yocto Project Application Development and | ||
1277 | the Extensible Software Development Kit (SDK) manual and | ||
1278 | the | ||
1279 | "<ulink url='&YOCTO_DOCS_KERNEL_DEV_URL;#using-traditional-kernel-development-to-patch-the-kernel'>Using Traditional Kernel Development to Patch the Kernel</ulink>" | ||
1280 | section in the Yocto Project Linux Kernel Development | ||
1281 | Manual. | ||
1267 | </para> | 1282 | </para> |
1268 | </section> | 1283 | </section> |
1269 | 1284 | ||