diff options
Diffstat (limited to 'documentation/ref-manual/tasks.rst')
-rw-r--r-- | documentation/ref-manual/tasks.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/ref-manual/tasks.rst b/documentation/ref-manual/tasks.rst index 8cffbb16c8..f47a30e467 100644 --- a/documentation/ref-manual/tasks.rst +++ b/documentation/ref-manual/tasks.rst | |||
@@ -81,7 +81,7 @@ Recipes implementing this task should inherit the | |||
81 | :ref:`deploy <ref-classes-deploy>` class and should write the output | 81 | :ref:`deploy <ref-classes-deploy>` class and should write the output |
82 | to ``${``\ :term:`DEPLOYDIR`\ ``}``, which is not to be | 82 | to ``${``\ :term:`DEPLOYDIR`\ ``}``, which is not to be |
83 | confused with ``${DEPLOY_DIR}``. The :ref:`deploy <ref-classes-deploy>` class sets up | 83 | confused with ``${DEPLOY_DIR}``. The :ref:`deploy <ref-classes-deploy>` class sets up |
84 | ``do_deploy`` as a shared state (sstate) task that can be accelerated | 84 | :ref:`ref-tasks-deploy` as a shared state (sstate) task that can be accelerated |
85 | through sstate use. The sstate mechanism takes care of copying the | 85 | through sstate use. The sstate mechanism takes care of copying the |
86 | output from ``${DEPLOYDIR}`` to ``${DEPLOY_DIR_IMAGE}``. | 86 | output from ``${DEPLOYDIR}`` to ``${DEPLOY_DIR_IMAGE}``. |
87 | 87 | ||
@@ -90,14 +90,14 @@ output from ``${DEPLOYDIR}`` to ``${DEPLOY_DIR_IMAGE}``. | |||
90 | Do not write the output directly to ``${DEPLOY_DIR_IMAGE}``, as this causes | 90 | Do not write the output directly to ``${DEPLOY_DIR_IMAGE}``, as this causes |
91 | the sstate mechanism to malfunction. | 91 | the sstate mechanism to malfunction. |
92 | 92 | ||
93 | The ``do_deploy`` task is not added as a task by default and | 93 | The :ref:`ref-tasks-deploy` task is not added as a task by default and |
94 | consequently needs to be added manually. If you want the task to run | 94 | consequently needs to be added manually. If you want the task to run |
95 | after :ref:`ref-tasks-compile`, you can add it by doing | 95 | after :ref:`ref-tasks-compile`, you can add it by doing |
96 | the following:: | 96 | the following:: |
97 | 97 | ||
98 | addtask deploy after do_compile | 98 | addtask deploy after do_compile |
99 | 99 | ||
100 | Adding ``do_deploy`` after other tasks works the same way. | 100 | Adding :ref:`ref-tasks-deploy` after other tasks works the same way. |
101 | 101 | ||
102 | .. note:: | 102 | .. note:: |
103 | 103 | ||
@@ -110,7 +110,7 @@ Adding ``do_deploy`` after other tasks works the same way. | |||
110 | See the ":ref:`bitbake-user-manual/bitbake-user-manual-execution:dependencies`" | 110 | See the ":ref:`bitbake-user-manual/bitbake-user-manual-execution:dependencies`" |
111 | section in the BitBake User Manual for more information. | 111 | section in the BitBake User Manual for more information. |
112 | 112 | ||
113 | If the ``do_deploy`` task re-executes, any previous output is removed | 113 | If the :ref:`ref-tasks-deploy` task re-executes, any previous output is removed |
114 | (i.e. "cleaned"). | 114 | (i.e. "cleaned"). |
115 | 115 | ||
116 | .. _ref-tasks-fetch: | 116 | .. _ref-tasks-fetch: |