diff options
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html | 31 |
1 files changed, 0 insertions, 31 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html deleted file mode 100644 index 89a6979603..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html +++ /dev/null | |||
| @@ -1,31 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>3.2.1. Overall Architecture</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="shared-state-cache.html" title="3.2. Shared State Cache"> | ||
| 9 | <link rel="prev" href="shared-state-cache.html" title="3.2. Shared State Cache"> | ||
| 10 | <link rel="next" href="checksums.html" title="3.2.2. Checksums (Signatures)"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.1. Overall Architecture"> | ||
| 13 | <div class="titlepage"><div><div><h3 class="title"> | ||
| 14 | <a name="overall-architecture"></a>3.2.1. Overall Architecture</h3></div></div></div> | ||
| 15 | <p> | ||
| 16 | When determining what parts of the system need to be built, BitBake | ||
| 17 | uses a per-task basis and does not use a per-recipe basis. | ||
| 18 | You might wonder why using a per-task basis is preferred over a per-recipe basis. | ||
| 19 | To help explain, consider having the IPK packaging backend enabled and then switching to DEB. | ||
| 20 | In this case, <code class="filename">do_install</code> and <code class="filename">do_package</code> | ||
| 21 | output are still valid. | ||
| 22 | However, with a per-recipe approach, the build would not include the | ||
| 23 | <code class="filename">.deb</code> files. | ||
| 24 | Consequently, you would have to invalidate the whole build and rerun it. | ||
| 25 | Rerunning everything is not the best situation. | ||
| 26 | Also in this case, the core must be "taught" much about specific tasks. | ||
| 27 | This methodology does not scale well and does not allow users to easily add new tasks | ||
| 28 | in layers or as external recipes without touching the packaged-staging core. | ||
| 29 | </p> | ||
| 30 | </div></body> | ||
| 31 | </html> | ||