diff options
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html | 54 |
1 files changed, 0 insertions, 54 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html deleted file mode 100644 index fedbcca285..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html +++ /dev/null | |||
| @@ -1,54 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>6.4. The Task List</title> | ||
| 5 | <link rel="stylesheet" type="text/css" href="../book.css"> | ||
| 6 | <meta name="generator" content="DocBook XSL Stylesheets V1.76.1"> | ||
| 7 | <link rel="home" href="index.html" title="The Yocto Project Reference Manual"> | ||
| 8 | <link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake"> | ||
| 9 | <link rel="prev" href="ref-bitbake-dependencies.html" title="6.3. Dependencies"> | ||
| 10 | <link rel="next" href="ref-bitbake-runtask.html" title="6.5. Running a Task"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.4. The Task List"> | ||
| 13 | <div class="titlepage"><div><div><h2 class="title" style="clear: both"> | ||
| 14 | <a name="ref-bitbake-tasklist"></a>6.4. The Task List</h2></div></div></div> | ||
| 15 | <p> | ||
| 16 | Based on the generated list of providers and the dependency information, | ||
| 17 | BitBake can now calculate exactly what tasks it needs to run and in what | ||
| 18 | order it needs to run them. | ||
| 19 | The build now starts with BitBake forking off threads up to the limit set in the | ||
| 20 | <code class="filename"><a class="link" href="ref-variables-glos.html#var-BB_NUMBER_THREADS" title="BB_NUMBER_THREADS">BB_NUMBER_THREADS</a></code> variable. | ||
| 21 | BitBake continues to fork threads as long as there are tasks ready to run, | ||
| 22 | those tasks have all their dependencies met, and the thread threshold has not been | ||
| 23 | exceeded. | ||
| 24 | </p> | ||
| 25 | <p> | ||
| 26 | It is worth noting that you can greatly speed up the build time by properly setting | ||
| 27 | the <code class="filename">BB_NUMBER_THREADS</code> variable. | ||
| 28 | See the | ||
| 29 | "<a class="link" href="../yocto-project-qs/building-image.html" target="_self">Building an Image</a>" | ||
| 30 | section in the Yocto Project Quick Start for more information. | ||
| 31 | </p> | ||
| 32 | <p> | ||
| 33 | As each task completes, a timestamp is written to the directory specified by the | ||
| 34 | <code class="filename"><a class="link" href="ref-variables-glos.html#var-STAMP" title="STAMP">STAMP</a></code> variable (usually | ||
| 35 | <code class="filename">build/tmp/stamps/*/</code>). | ||
| 36 | On subsequent runs, BitBake looks at the <code class="filename">/build/tmp/stamps</code> | ||
| 37 | directory and does not rerun | ||
| 38 | tasks that are already completed unless a timestamp is found to be invalid. | ||
| 39 | Currently, invalid timestamps are only considered on a per | ||
| 40 | <code class="filename">.bb</code> file basis. | ||
| 41 | So, for example, if the configure stamp has a timestamp greater than the | ||
| 42 | compile timestamp for a given target, then the compile task would rerun. | ||
| 43 | Running the compile task again, however, has no effect on other providers | ||
| 44 | that depend on that target. | ||
| 45 | This behavior could change or become configurable in future versions of BitBake. | ||
| 46 | </p> | ||
| 47 | <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> | ||
| 48 | <h3 class="title">Note</h3> | ||
| 49 | Some tasks are marked as "nostamp" tasks. | ||
| 50 | No timestamp file is created when these tasks are run. | ||
| 51 | Consequently, "nostamp" tasks are always rerun. | ||
| 52 | </div> | ||
| 53 | </div></body> | ||
| 54 | </html> | ||