diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2022-11-24 17:50:52 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-12-01 19:20:29 +0000 |
commit | 945c669138a76be18c6b4da4f8f907d2a5cfd83f (patch) | |
tree | cebff3cae5021d4fcceb5aa51fce1c2aead97ed2 /documentation/ref-manual/tasks.rst | |
parent | 6fe3143800925463279d0664fc7f3372b53c6c52 (diff) | |
download | poky-945c669138a76be18c6b4da4f8f907d2a5cfd83f.tar.gz |
manuals: split dev-manual/common-tasks.rst
A 500 KB source file is always harder to manage,
and can have section title conflicts.
So, the "Common Tasks" document is gone and all
its constituents are moved up one level.
You now have 40 chapters in the Development Tasks Manual.
(From yocto-docs rev: 8a45bc469411410020b8e688c137395fcaf3761b)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/tasks.rst')
-rw-r--r-- | documentation/ref-manual/tasks.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/ref-manual/tasks.rst b/documentation/ref-manual/tasks.rst index b17c09cdc4..e626095b20 100644 --- a/documentation/ref-manual/tasks.rst +++ b/documentation/ref-manual/tasks.rst | |||
@@ -343,7 +343,7 @@ while ``file2.patch`` would not be applied. | |||
343 | You can find out more about the patching process in the | 343 | You can find out more about the patching process in the |
344 | ":ref:`overview-manual/concepts:patching`" section in | 344 | ":ref:`overview-manual/concepts:patching`" section in |
345 | the Yocto Project Overview and Concepts Manual and the | 345 | the Yocto Project Overview and Concepts Manual and the |
346 | ":ref:`dev-manual/common-tasks:patching code`" section in the | 346 | ":ref:`dev-manual/new-recipe:patching code`" section in the |
347 | Yocto Project Development Tasks Manual. | 347 | Yocto Project Development Tasks Manual. |
348 | 348 | ||
349 | .. _ref-tasks-populate_lic: | 349 | .. _ref-tasks-populate_lic: |
@@ -522,7 +522,7 @@ scratch is guaranteed. | |||
522 | Starts a shell in which an interactive Python interpreter allows you to | 522 | Starts a shell in which an interactive Python interpreter allows you to |
523 | interact with the BitBake build environment. From within this shell, you | 523 | interact with the BitBake build environment. From within this shell, you |
524 | can directly examine and set bits from the data store and execute | 524 | can directly examine and set bits from the data store and execute |
525 | functions as if within the BitBake environment. See the ":ref:`dev-manual/common-tasks:using a Python development shell`" section in | 525 | functions as if within the BitBake environment. See the ":ref:`dev-manual/python-development-shell:using a Python development shell`" section in |
526 | the Yocto Project Development Tasks Manual for more information about | 526 | the Yocto Project Development Tasks Manual for more information about |
527 | using ``pydevshell``. | 527 | using ``pydevshell``. |
528 | 528 | ||
@@ -532,7 +532,7 @@ using ``pydevshell``. | |||
532 | --------------- | 532 | --------------- |
533 | 533 | ||
534 | Starts a shell whose environment is set up for development, debugging, | 534 | Starts a shell whose environment is set up for development, debugging, |
535 | or both. See the ":ref:`dev-manual/common-tasks:using a development shell`" section in the | 535 | or both. See the ":ref:`dev-manual/development-shell:using a development shell`" section in the |
536 | Yocto Project Development Tasks Manual for more information about using | 536 | Yocto Project Development Tasks Manual for more information about using |
537 | ``devshell``. | 537 | ``devshell``. |
538 | 538 | ||
@@ -595,7 +595,7 @@ information on how the root filesystem is created. | |||
595 | 595 | ||
596 | Boots an image and performs runtime tests within the image. For | 596 | Boots an image and performs runtime tests within the image. For |
597 | information on automatically testing images, see the | 597 | information on automatically testing images, see the |
598 | ":ref:`dev-manual/common-tasks:performing automated runtime testing`" | 598 | ":ref:`dev-manual/runtime-testing:performing automated runtime testing`" |
599 | section in the Yocto Project Development Tasks Manual. | 599 | section in the Yocto Project Development Tasks Manual. |
600 | 600 | ||
601 | .. _ref-tasks-testimage_auto: | 601 | .. _ref-tasks-testimage_auto: |
@@ -608,7 +608,7 @@ after it has been built. This task is enabled when you set | |||
608 | :term:`TESTIMAGE_AUTO` equal to "1". | 608 | :term:`TESTIMAGE_AUTO` equal to "1". |
609 | 609 | ||
610 | For information on automatically testing images, see the | 610 | For information on automatically testing images, see the |
611 | ":ref:`dev-manual/common-tasks:performing automated runtime testing`" | 611 | ":ref:`dev-manual/runtime-testing:performing automated runtime testing`" |
612 | section in the Yocto Project Development Tasks Manual. | 612 | section in the Yocto Project Development Tasks Manual. |
613 | 613 | ||
614 | Kernel-Related Tasks | 614 | Kernel-Related Tasks |