summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-tasks.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/ref-tasks.rst')
-rw-r--r--documentation/ref-manual/ref-tasks.rst192
1 files changed, 110 insertions, 82 deletions
diff --git a/documentation/ref-manual/ref-tasks.rst b/documentation/ref-manual/ref-tasks.rst
index 5b0711586f..44463f2236 100644
--- a/documentation/ref-manual/ref-tasks.rst
+++ b/documentation/ref-manual/ref-tasks.rst
@@ -109,7 +109,7 @@ after other tasks works the same way.
109 :: 109 ::
110 110
111 do_build[recrdeptask] += "do_deploy" 111 do_build[recrdeptask] += "do_deploy"
112 112
113 113
114 See the " 114 See the "
115 Dependencies 115 Dependencies
@@ -143,8 +143,7 @@ The ``do_image`` task performs pre-processing on the image through the
143:term:`IMAGE_PREPROCESS_COMMAND` and 143:term:`IMAGE_PREPROCESS_COMMAND` and
144dynamically generates supporting ``do_image_*`` tasks as needed. 144dynamically generates supporting ``do_image_*`` tasks as needed.
145 145
146For more information on image creation, see the "`Image 146For more information on image creation, see the ":ref:`image-generation-dev-environment`"
147Generation <&YOCTO_DOCS_OM_URL;#image-generation-dev-environment>`__"
148section in the Yocto Project Overview and Concepts Manual. 147section in the Yocto Project Overview and Concepts Manual.
149 148
150.. _ref-tasks-image-complete: 149.. _ref-tasks-image-complete:
@@ -162,8 +161,8 @@ The ``do_image_complete`` task performs post-processing on the image
162through the 161through the
163:term:`IMAGE_POSTPROCESS_COMMAND`. 162:term:`IMAGE_POSTPROCESS_COMMAND`.
164 163
165For more information on image creation, see the "`Image 164For more information on image creation, see the
166Generation <&YOCTO_DOCS_OM_URL;#image-generation-dev-environment>`__" 165":ref:`image-generation-dev-environment`"
167section in the Yocto Project Overview and Concepts Manual. 166section in the Yocto Project Overview and Concepts Manual.
168 167
169.. _ref-tasks-install: 168.. _ref-tasks-install:
@@ -176,10 +175,9 @@ Copies files that are to be packaged into the holding area
176working directory set to ``${``\ :term:`B`\ ``}``, which is the 175working directory set to ``${``\ :term:`B`\ ``}``, which is the
177compilation directory. The ``do_install`` task, as well as other tasks 176compilation directory. The ``do_install`` task, as well as other tasks
178that either directly or indirectly depend on the installed files (e.g. 177that either directly or indirectly depend on the installed files (e.g.
179:ref:`ref-tasks-package`, 178:ref:`ref-tasks-package`, ``do_package_write_*``, and
180```do_package_write_*`` <#ref-tasks-package_write_deb>`__, and
181:ref:`ref-tasks-rootfs`), run under 179:ref:`ref-tasks-rootfs`), run under
182`fakeroot <&YOCTO_DOCS_OM_URL;#fakeroot-and-pseudo>`__. 180:ref:`fakeroot <overview-manual/overview-manual-concepts:fakeroot and pseudo>`.
183 181
184.. note:: 182.. note::
185 183
@@ -187,9 +185,8 @@ that either directly or indirectly depend on the installed files (e.g.
187 of the installed files to unintended values. Some methods of copying 185 of the installed files to unintended values. Some methods of copying
188 files, notably when using the recursive ``cp`` command, can preserve 186 files, notably when using the recursive ``cp`` command, can preserve
189 the UID and/or GID of the original file, which is usually not what 187 the UID and/or GID of the original file, which is usually not what
190 you want. The 188 you want. The ``host-user-contaminated`` QA check checks for files
191 ```host-user-contaminated`` <#insane-host-user-contaminated>`__ QA 189 that probably have the wrong ownership.
192 check checks for files that probably have the wrong ownership.
193 190
194 Safe methods for installing files include the following: 191 Safe methods for installing files include the following:
195 192
@@ -223,9 +220,8 @@ variables.
223The ``do_package`` task, in conjunction with the 220The ``do_package`` task, in conjunction with the
224:ref:`ref-tasks-packagedata` task, also saves some 221:ref:`ref-tasks-packagedata` task, also saves some
225important package metadata. For additional information, see the 222important package metadata. For additional information, see the
226:term:`PKGDESTWORK` variable and the "`Automatically 223:term:`PKGDESTWORK` variable and the
227Added Runtime 224":ref:`overview-manual/overview-manual-concepts:automatically added runtime dependencies`"
228Dependencies <&YOCTO_DOCS_OM_URL;#automatically-added-runtime-dependencies>`__"
229section in the Yocto Project Overview and Concepts Manual. 225section in the Yocto Project Overview and Concepts Manual.
230 226
231.. _ref-tasks-package_qa: 227.. _ref-tasks-package_qa:
@@ -243,8 +239,8 @@ see the :ref:`insane <ref-classes-insane>` class.
243 239
244Creates Debian packages (i.e. ``*.deb`` files) and places them in the 240Creates Debian packages (i.e. ``*.deb`` files) and places them in the
245``${``\ :term:`DEPLOY_DIR_DEB`\ ``}`` directory in 241``${``\ :term:`DEPLOY_DIR_DEB`\ ``}`` directory in
246the package feeds area. For more information, see the "`Package 242the package feeds area. For more information, see the
247Feeds <&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment>`__" section in 243":ref:`package-feeds-dev-environment`" section in
248the Yocto Project Overview and Concepts Manual. 244the Yocto Project Overview and Concepts Manual.
249 245
250.. _ref-tasks-package_write_ipk: 246.. _ref-tasks-package_write_ipk:
@@ -254,8 +250,8 @@ the Yocto Project Overview and Concepts Manual.
254 250
255Creates IPK packages (i.e. ``*.ipk`` files) and places them in the 251Creates IPK packages (i.e. ``*.ipk`` files) and places them in the
256``${``\ :term:`DEPLOY_DIR_IPK`\ ``}`` directory in 252``${``\ :term:`DEPLOY_DIR_IPK`\ ``}`` directory in
257the package feeds area. For more information, see the "`Package 253the package feeds area. For more information, see the
258Feeds <&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment>`__" section in 254":ref:`package-feeds-dev-environment`" section in
259the Yocto Project Overview and Concepts Manual. 255the Yocto Project Overview and Concepts Manual.
260 256
261.. _ref-tasks-package_write_rpm: 257.. _ref-tasks-package_write_rpm:
@@ -265,8 +261,8 @@ the Yocto Project Overview and Concepts Manual.
265 261
266Creates RPM packages (i.e. ``*.rpm`` files) and places them in the 262Creates RPM packages (i.e. ``*.rpm`` files) and places them in the
267``${``\ :term:`DEPLOY_DIR_RPM`\ ``}`` directory in 263``${``\ :term:`DEPLOY_DIR_RPM`\ ``}`` directory in
268the package feeds area. For more information, see the "`Package 264the package feeds area. For more information, see the
269Feeds <&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment>`__" section in 265":ref:`package-feeds-dev-environment`" section in
270the Yocto Project Overview and Concepts Manual. 266the Yocto Project Overview and Concepts Manual.
271 267
272.. _ref-tasks-package_write_tar: 268.. _ref-tasks-package_write_tar:
@@ -276,8 +272,8 @@ the Yocto Project Overview and Concepts Manual.
276 272
277Creates tarballs and places them in the 273Creates tarballs and places them in the
278``${``\ :term:`DEPLOY_DIR_TAR`\ ``}`` directory in 274``${``\ :term:`DEPLOY_DIR_TAR`\ ``}`` directory in
279the package feeds area. For more information, see the "`Package 275the package feeds area. For more information, see the
280Feeds <&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment>`__" section in 276":ref:`package-feeds-dev-environment`" section in
281the Yocto Project Overview and Concepts Manual. 277the Yocto Project Overview and Concepts Manual.
282 278
283.. _ref-tasks-packagedata: 279.. _ref-tasks-packagedata:
@@ -312,8 +308,14 @@ and kept in a subdirectory of the directory holding the recipe file. For
312example, consider the 308example, consider the
313:yocto_git:`bluez5 </cgit/cgit.cgi/poky/tree/meta/recipes-connectivity/bluez5>` 309:yocto_git:`bluez5 </cgit/cgit.cgi/poky/tree/meta/recipes-connectivity/bluez5>`
314recipe from the OE-Core layer (i.e. ``poky/meta``): 310recipe from the OE-Core layer (i.e. ``poky/meta``):
315poky/meta/recipes-connectivity/bluez5 This recipe has two patch files 311::
316located here: poky/meta/recipes-connectivity/bluez5/bluez5 312
313 poky/meta/recipes-connectivity/bluez5
314
315This recipe has two patch files located here:
316::
317
318 poky/meta/recipes-connectivity/bluez5/bluez5
317 319
318In the ``bluez5`` recipe, the ``SRC_URI`` statements point to the source 320In the ``bluez5`` recipe, the ``SRC_URI`` statements point to the source
319and patch files needed to build the package. 321and patch files needed to build the package.
@@ -331,23 +333,35 @@ and patch files needed to build the package.
331As mentioned earlier, the build system treats files whose file types are 333As mentioned earlier, the build system treats files whose file types are
332``.patch`` and ``.diff`` as patch files. However, you can use the 334``.patch`` and ``.diff`` as patch files. However, you can use the
333"apply=yes" parameter with the ``SRC_URI`` statement to indicate any 335"apply=yes" parameter with the ``SRC_URI`` statement to indicate any
334file as a patch file: SRC_URI = " \\ git://path_to_repo/some_package \\ 336file as a patch file:
335file://file;apply=yes \\ " 337::
338
339 SRC_URI = " \\
340 git://path_to_repo/some_package \\
341 file://file;apply=yes \\
342 "
336 343
337Conversely, if you have a directory full of patch files and you want to 344Conversely, if you have a directory full of patch files and you want to
338exclude some so that the ``do_patch`` task does not apply them during 345exclude some so that the ``do_patch`` task does not apply them during
339the patch phase, you can use the "apply=no" parameter with the 346the patch phase, you can use the "apply=no" parameter with the
340``SRC_URI`` statement: SRC_URI = " \\ git://path_to_repo/some_package \\ 347``SRC_URI`` statement:
341file://path_to_lots_of_patch_files \\ 348::
342file://path_to_lots_of_patch_files/patch_file5;apply=no \\ " In the 349
350 SRC_URI = " \
351 git://path_to_repo/some_package \
352 file://path_to_lots_of_patch_files \
353 file://path_to_lots_of_patch_files/patch_file5;apply=no \
354 "
355
356In the
343previous example, assuming all the files in the directory holding the 357previous example, assuming all the files in the directory holding the
344patch files end with either ``.patch`` or ``.diff``, every file would be 358patch files end with either ``.patch`` or ``.diff``, every file would be
345applied as a patch by default except for the patch_file5 patch. 359applied as a patch by default except for the patch_file5 patch.
346 360
347You can find out more about the patching process in the 361You can find out more about the patching process in the
348"`Patching <&YOCTO_DOCS_OM_URL;#patching-dev-environment>`__" section in 362":ref:`patching-dev-environment`" section in
349the Yocto Project Overview and Concepts Manual and the "`Patching 363the Yocto Project Overview and Concepts Manual and the
350Code <&YOCTO_DOCS_DEV_URL;#new-recipe-patching-code>`__" section in the 364":ref:`new-recipe-patching-code`" section in the
351Yocto Project Development Tasks Manual. 365Yocto Project Development Tasks Manual.
352 366
353.. _ref-tasks-populate_lic: 367.. _ref-tasks-populate_lic:
@@ -364,8 +378,7 @@ the image is constructed.
364------------------- 378-------------------
365 379
366Creates the file and directory structure for an installable SDK. See the 380Creates the file and directory structure for an installable SDK. See the
367"`SDK 381":ref:`sdk-generation-dev-environment`"
368Generation <&YOCTO_DOCS_OM_URL;#sdk-generation-dev-environment>`__"
369section in the Yocto Project Overview and Concepts Manual for more 382section in the Yocto Project Overview and Concepts Manual for more
370information. 383information.
371 384
@@ -420,8 +433,7 @@ Unpacks the source code into a working directory pointed to by
420``${``\ :term:`WORKDIR`\ ``}``. The :term:`S` 433``${``\ :term:`WORKDIR`\ ``}``. The :term:`S`
421variable also plays a role in where unpacked source files ultimately 434variable also plays a role in where unpacked source files ultimately
422reside. For more information on how source files are unpacked, see the 435reside. For more information on how source files are unpacked, see the
423"`Source 436":ref:`source-fetching-dev-environment`"
424Fetching <&YOCTO_DOCS_OM_URL;#source-fetching-dev-environment>`__"
425section in the Yocto Project Overview and Concepts Manual and also see 437section in the Yocto Project Overview and Concepts Manual and also see
426the ``WORKDIR`` and ``S`` variable descriptions. 438the ``WORKDIR`` and ``S`` variable descriptions.
427 439
@@ -442,16 +454,24 @@ of the recipe exists upstream and a status of not updated, updated, or
442unknown. 454unknown.
443 455
444To check the upstream version and status of a recipe, use the following 456To check the upstream version and status of a recipe, use the following
445devtool commands: $ devtool latest-version $ devtool 457devtool commands:
446check-upgrade-status See the "```devtool`` Quick 458::
447Reference <#ref-devtool-reference>`__" chapter for more information on 459
448``devtool``. See the "`Checking on the Upgrade Status of a 460 $ devtool latest-version
449Recipe <&YOCTO_DOCS_REF_URL;#devtool-checking-on-the-upgrade-status-of-a-recipe>`__" 461 $ devtool check-upgrade-status
462
463See the ":ref:`ref-manual/ref-devtool-reference:\`\`devtool\`\` quick reference`"
464chapter for more information on
465``devtool``. See the ":ref:`devtool-checking-on-the-upgrade-status-of-a-recipe`"
450section for information on checking the upgrade status of a recipe. 466section for information on checking the upgrade status of a recipe.
451 467
452To build the ``checkpkg`` task, use the ``bitbake`` command with the 468To build the ``checkpkg`` task, use the ``bitbake`` command with the
453"-c" option and task name: $ bitbake core-image-minimal -c checkpkg By 469"-c" option and task name:
454default, the results are stored in :term:`$LOG_DIR <LOG_DIR>` (e.g. 470::
471
472 $ bitbake core-image-minimal -c checkpkg
473
474By default, the results are stored in :term:`$LOG_DIR <LOG_DIR>` (e.g.
455``$BUILD_DIR/tmp/log``). 475``$BUILD_DIR/tmp/log``).
456 476
457.. _ref-tasks-checkuri: 477.. _ref-tasks-checkuri:
@@ -473,11 +493,13 @@ Removes all output files for a target from the
473:ref:`ref-tasks-install`, and 493:ref:`ref-tasks-install`, and
474:ref:`ref-tasks-package`). 494:ref:`ref-tasks-package`).
475 495
476You can run this task using BitBake as follows: $ bitbake -c clean 496You can run this task using BitBake as follows:
477recipe 497::
498
499 $ bitbake -c clean recipe
478 500
479Running this task does not remove the 501Running this task does not remove the
480`sstate <&YOCTO_DOCS_OM_URL;#shared-state-cache>`__ cache files. 502:ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>` cache files.
481Consequently, if no changes have been made and the recipe is rebuilt 503Consequently, if no changes have been made and the recipe is rebuilt
482after cleaning, output files are simply restored from the sstate cache. 504after cleaning, output files are simply restored from the sstate cache.
483If you want to remove the sstate cache files for the recipe, you need to 505If you want to remove the sstate cache files for the recipe, you need to
@@ -490,14 +512,16 @@ use the :ref:`ref-tasks-cleansstate` task instead
490--------------- 512---------------
491 513
492Removes all output files, shared state 514Removes all output files, shared state
493(`sstate <&YOCTO_DOCS_OM_URL;#shared-state-cache>`__) cache, and 515(:ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>`) cache, and
494downloaded source files for a target (i.e. the contents of 516downloaded source files for a target (i.e. the contents of
495:term:`DL_DIR`). Essentially, the ``do_cleanall`` task is 517:term:`DL_DIR`). Essentially, the ``do_cleanall`` task is
496identical to the :ref:`ref-tasks-cleansstate` task 518identical to the :ref:`ref-tasks-cleansstate` task
497with the added removal of downloaded source files. 519with the added removal of downloaded source files.
498 520
499You can run this task using BitBake as follows: $ bitbake -c cleanall 521You can run this task using BitBake as follows:
500recipe 522::
523
524 $ bitbake -c cleanall recipe
501 525
502Typically, you would not normally use the ``cleanall`` task. Do so only 526Typically, you would not normally use the ``cleanall`` task. Do so only
503if you want to start fresh with the :ref:`ref-tasks-fetch` 527if you want to start fresh with the :ref:`ref-tasks-fetch`
@@ -509,14 +533,16 @@ task.
509------------------ 533------------------
510 534
511Removes all output files and shared state 535Removes all output files and shared state
512(`sstate <&YOCTO_DOCS_OM_URL;#shared-state-cache>`__) cache for a 536(:ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>`) cache for a
513target. Essentially, the ``do_cleansstate`` task is identical to the 537target. Essentially, the ``do_cleansstate`` task is identical to the
514:ref:`ref-tasks-clean` task with the added removal of 538:ref:`ref-tasks-clean` task with the added removal of
515shared state (`sstate <&YOCTO_DOCS_OM_URL;#shared-state-cache>`__) 539shared state (`:ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>`)
516cache. 540cache.
517 541
518You can run this task using BitBake as follows: $ bitbake -c cleansstate 542You can run this task using BitBake as follows:
519recipe 543::
544
545 $ bitbake -c cleansstate recipe
520 546
521When you run the ``do_cleansstate`` task, the OpenEmbedded build system 547When you run the ``do_cleansstate`` task, the OpenEmbedded build system
522no longer uses any sstate. Consequently, building the recipe from 548no longer uses any sstate. Consequently, building the recipe from
@@ -531,8 +557,8 @@ scratch is guaranteed.
531 as follows: 557 as follows:
532 :: 558 ::
533 559
534 $ bitbake -f -c do_cleansstate target 560 $ bitbake -f -c do_cleansstate target
535 561
536 562
537.. _ref-tasks-devpyshell: 563.. _ref-tasks-devpyshell:
538 564
@@ -542,9 +568,7 @@ scratch is guaranteed.
542Starts a shell in which an interactive Python interpreter allows you to 568Starts a shell in which an interactive Python interpreter allows you to
543interact with the BitBake build environment. From within this shell, you 569interact with the BitBake build environment. From within this shell, you
544can directly examine and set bits from the data store and execute 570can directly examine and set bits from the data store and execute
545functions as if within the BitBake environment. See the "`Using a 571functions as if within the BitBake environment. See the ":ref:`platdev-appdev-devpyshell`" section in
546Development Python
547Shell <&YOCTO_DOCS_DEV_URL;#platdev-appdev-devpyshell>`__" section in
548the Yocto Project Development Tasks Manual for more information about 572the Yocto Project Development Tasks Manual for more information about
549using ``devpyshell``. 573using ``devpyshell``.
550 574
@@ -554,8 +578,7 @@ using ``devpyshell``.
554--------------- 578---------------
555 579
556Starts a shell whose environment is set up for development, debugging, 580Starts a shell whose environment is set up for development, debugging,
557or both. See the "`Using a Development 581or both. See the ":ref:`platdev-appdev-devshell`" section in the
558Shell <&YOCTO_DOCS_DEV_URL;#platdev-appdev-devshell>`__" section in the
559Yocto Project Development Tasks Manual for more information about using 582Yocto Project Development Tasks Manual for more information about using
560``devshell``. 583``devshell``.
561 584
@@ -571,8 +594,7 @@ Lists all defined tasks for a target.
571``do_package_index`` 594``do_package_index``
572-------------------- 595--------------------
573 596
574Creates or updates the index in the `Package 597Creates or updates the index in the `:ref:`package-feeds-dev-environment` area.
575Feeds <&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment>`__ area.
576 598
577.. note:: 599.. note::
578 600
@@ -615,8 +637,7 @@ has some more information about these types of images.
615------------- 637-------------
616 638
617Creates the root filesystem (file and directory structure) for an image. 639Creates the root filesystem (file and directory structure) for an image.
618See the "`Image 640See the ":ref:`image-generation-dev-environment`"
619Generation <&YOCTO_DOCS_OM_URL;#image-generation-dev-environment>`__"
620section in the Yocto Project Overview and Concepts Manual for more 641section in the Yocto Project Overview and Concepts Manual for more
621information on how the root filesystem is created. 642information on how the root filesystem is created.
622 643
@@ -626,9 +647,8 @@ information on how the root filesystem is created.
626---------------- 647----------------
627 648
628Boots an image and performs runtime tests within the image. For 649Boots an image and performs runtime tests within the image. For
629information on automatically testing images, see the "`Performing 650information on automatically testing images, see the
630Automated Runtime 651":ref:`dev-manual/dev-manual-common-tasks:performing automated runtime testing`"
631Testing <&YOCTO_DOCS_DEV_URL;#performing-automated-runtime-testing>`__"
632section in the Yocto Project Development Tasks Manual. 652section in the Yocto Project Development Tasks Manual.
633 653
634.. _ref-tasks-testimage_auto: 654.. _ref-tasks-testimage_auto:
@@ -640,9 +660,8 @@ Boots an image and performs runtime tests within the image immediately
640after it has been built. This task is enabled when you set 660after it has been built. This task is enabled when you set
641:term:`TESTIMAGE_AUTO` equal to "1". 661:term:`TESTIMAGE_AUTO` equal to "1".
642 662
643For information on automatically testing images, see the "`Performing 663For information on automatically testing images, see the
644Automated Runtime 664":ref:`dev-manual/dev-manual-common-tasks:performing automated runtime testing`"
645Testing <&YOCTO_DOCS_DEV_URL;#performing-automated-runtime-testing>`__"
646section in the Yocto Project Development Tasks Manual. 665section in the Yocto Project Development Tasks Manual.
647 666
648Kernel-Related Tasks 667Kernel-Related Tasks
@@ -674,9 +693,13 @@ changes made by the user with other methods (i.e. using
674(:ref:`ref-tasks-kernel_menuconfig`). Once the 693(:ref:`ref-tasks-kernel_menuconfig`). Once the
675file of differences is created, it can be used to create a config 694file of differences is created, it can be used to create a config
676fragment that only contains the differences. You can invoke this task 695fragment that only contains the differences. You can invoke this task
677from the command line as follows: $ bitbake linux-yocto -c diffconfig 696from the command line as follows:
678For more information, see the "`Creating Configuration 697::
679Fragments <&YOCTO_DOCS_KERNEL_DEV_URL;#creating-config-fragments>`__" 698
699 $ bitbake linux-yocto -c diffconfig
700
701For more information, see the
702":ref:`kernel-dev/kernel-dev-common:creating configuration fragments`"
680section in the Yocto Project Linux Kernel Development Manual. 703section in the Yocto Project Linux Kernel Development Manual.
681 704
682.. _ref-tasks-kernel_checkout: 705.. _ref-tasks-kernel_checkout:
@@ -701,9 +724,13 @@ Validates the configuration produced by the
701configuration does not appear in the final ``.config`` file or when you 724configuration does not appear in the final ``.config`` file or when you
702override a policy configuration in a hardware configuration fragment. 725override a policy configuration in a hardware configuration fragment.
703You can run this task explicitly and view the output by using the 726You can run this task explicitly and view the output by using the
704following command: $ bitbake linux-yocto -c kernel_configcheck -f For 727following command:
705more information, see the "`Validating 728::
706Configuration <&YOCTO_DOCS_KERNEL_DEV_URL;#validating-configuration>`__" 729
730 $ bitbake linux-yocto -c kernel_configcheck -f
731
732For more information, see the
733":ref:`kernel-dev/kernel-dev-common:validating configuration`"
707section in the Yocto Project Linux Kernel Development Manual. 734section in the Yocto Project Linux Kernel Development Manual.
708 735
709.. _ref-tasks-kernel_configme: 736.. _ref-tasks-kernel_configme:
@@ -733,10 +760,9 @@ tool, which you then use to modify the kernel configuration.
733 :: 760 ::
734 761
735 $ bitbake linux-yocto -c menuconfig 762 $ bitbake linux-yocto -c menuconfig
736
737 763
738See the "`Using 764
739``menuconfig`` <&YOCTO_DOCS_KERNEL_DEV_URL;#using-menuconfig>`__" 765See the ":ref:`kernel-dev/kernel-dev-common:using \`\`menuconfig\`\``"
740section in the Yocto Project Linux Kernel Development Manual for more 766section in the Yocto Project Linux Kernel Development Manual for more
741information on this configuration tool. 767information on this configuration tool.
742 768
@@ -760,7 +786,7 @@ which can then be applied by subsequent tasks such as
760 786
761Runs ``make menuconfig`` for the kernel. For information on 787Runs ``make menuconfig`` for the kernel. For information on
762``menuconfig``, see the 788``menuconfig``, see the
763"`Using  ``menuconfig`` <&YOCTO_DOCS_KERNEL_DEV_URL;#using-menuconfig>`__" 789":ref:`kernel-dev/kernel-dev-common:using \`\`menuconfig\`\``"
764section in the Yocto Project Linux Kernel Development Manual. 790section in the Yocto Project Linux Kernel Development Manual.
765 791
766.. _ref-tasks-savedefconfig: 792.. _ref-tasks-savedefconfig:
@@ -773,8 +799,10 @@ instead of the default defconfig. The saved defconfig contains the
773differences between the default defconfig and the changes made by the 799differences between the default defconfig and the changes made by the
774user using other methods (i.e. the 800user using other methods (i.e. the
775:ref:`ref-tasks-kernel_menuconfig` task. You 801:ref:`ref-tasks-kernel_menuconfig` task. You
776can invoke the task using the following command: $ bitbake linux-yocto 802can invoke the task using the following command:
777-c savedefconfig 803::
804
805 $ bitbake linux-yocto -c savedefconfig
778 806
779.. _ref-tasks-shared_workdir: 807.. _ref-tasks-shared_workdir:
780 808