diff options
| -rw-r--r-- | documentation/kernel-dev/kernel-dev-advanced.xml | 29 |
1 files changed, 14 insertions, 15 deletions
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml index 18238c75c2..87819903bb 100644 --- a/documentation/kernel-dev/kernel-dev-advanced.xml +++ b/documentation/kernel-dev/kernel-dev-advanced.xml | |||
| @@ -344,22 +344,24 @@ described in the following sections applies equally. | |||
| 344 | <title>Recipe-Space Metadata</title> | 344 | <title>Recipe-Space Metadata</title> |
| 345 | 345 | ||
| 346 | <para> | 346 | <para> |
| 347 | When stored in recipe-space, the metadata files reside in a | 347 | When stored in recipe-space, the kernel Metadata files reside in a |
| 348 | directory hierarchy below | 348 | directory hierarchy below |
| 349 | <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESEXTRAPATHS'><filename>FILESEXTRAPATHS</filename></ulink>, | 349 | <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESEXTRAPATHS'><filename>FILESEXTRAPATHS</filename></ulink>. |
| 350 | which is typically set to | 350 | For a linux-yocto recipe or for a Linux kernel recipe derived |
| 351 | <filename>${THISDIR}/${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink><filename>}</filename> | 351 | by copying and modifying |
| 352 | for a linux-yocto or linux-yocto-custom derived Linux kernel | 352 | <filename>oe-core/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb</filename> |
| 353 | recipe. | 353 | to a recipe in your layer, <filename>FILESEXTRAPATHS</filename> |
| 354 | is typically set to | ||
| 355 | <filename>${THISDIR}/${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink><filename>}</filename>. | ||
| 354 | See the "<link linkend='modifying-an-existing-recipe'>Modifying an Existing Recipe</link>" | 356 | See the "<link linkend='modifying-an-existing-recipe'>Modifying an Existing Recipe</link>" |
| 355 | section for more information. | 357 | section for more information. |
| 356 | </para> | 358 | </para> |
| 357 | 359 | ||
| 358 | <para> | 360 | <para> |
| 359 | By way of example, a trivial tree of metadata stored in | 361 | Here is an example that shows a trivial tree of kernel Metadata |
| 360 | recipe-space within a BSP layer might look like the following: | 362 | stored in recipe-space within a BSP layer: |
| 361 | <literallayout class='monospaced'> | 363 | <literallayout class='monospaced'> |
| 362 | meta/ | 364 | meta-my_bsp_layer/ |
| 363 | `-- recipes-kernel | 365 | `-- recipes-kernel |
| 364 | `-- linux | 366 | `-- linux |
| 365 | `-- linux-yocto | 367 | `-- linux-yocto |
| @@ -370,12 +372,9 @@ described in the following sections applies equally. | |||
| 370 | </para> | 372 | </para> |
| 371 | 373 | ||
| 372 | <para> | 374 | <para> |
| 373 | When the metadata is stored in recipe-space, you must take | 375 | When the Metadata is stored in recipe-space, you must take |
| 374 | steps to ensure BitBake has the necessary information to decide | 376 | steps to ensure BitBake has the necessary information to decide |
| 375 | which files to fetch and when they need to be fetched again. | 377 | what files to fetch and when they need to be fetched again. |
| 376 | </para> | ||
| 377 | |||
| 378 | <para> | ||
| 379 | It is only necessary to specify the <filename>.scc</filename> | 378 | It is only necessary to specify the <filename>.scc</filename> |
| 380 | files on the | 379 | files on the |
| 381 | <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>. | 380 | <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>. |
| @@ -385,7 +384,7 @@ described in the following sections applies equally. | |||
| 385 | Because of this, it is necessary to bump the recipe | 384 | Because of this, it is necessary to bump the recipe |
| 386 | <ulink url='&YOCTO_DOCS_REF_URL;#var-PR'><filename>PR</filename></ulink> | 385 | <ulink url='&YOCTO_DOCS_REF_URL;#var-PR'><filename>PR</filename></ulink> |
| 387 | value when changing the content of files not explicitly listed | 386 | value when changing the content of files not explicitly listed |
| 388 | in the SRC_URI. | 387 | in the <filename>SRC_URI</filename>. |
| 389 | </para> | 388 | </para> |
| 390 | 389 | ||
| 391 | <para> | 390 | <para> |
