summaryrefslogtreecommitdiffstats
path: root/documentation/getting-started/eclipse/html/getting-started/overall-architecture.html
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2018-01-30 11:31:29 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-02-14 15:25:30 +0000
commitf9db48724f4800e7810daad34e4a55551f29fb1c (patch)
treee6bfe1c4a37e01571eabf36f9e95b2cf70edeeb7 /documentation/getting-started/eclipse/html/getting-started/overall-architecture.html
parent52b871825f9446b162cd871c829b7458e34878d7 (diff)
downloadpoky-f9db48724f4800e7810daad34e4a55551f29fb1c.tar.gz
getting-started: Removed accidental tracked files
I accidentally pushed a commit after building out the new getting-started manual before applying some key files to the .gitignore file. So, the HTML, TGZ, and eclipse/* stuff got tracked in Git. I don't want that. So I had to use the 'git rm' command to untrack those files. (From yocto-docs rev: 217f6db7f741cee266885a845b2b0e7faf96e537) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/getting-started/eclipse/html/getting-started/overall-architecture.html')
-rw-r--r--documentation/getting-started/eclipse/html/getting-started/overall-architecture.html40
1 files changed, 0 insertions, 40 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/overall-architecture.html b/documentation/getting-started/eclipse/html/getting-started/overall-architecture.html
deleted file mode 100644
index 974b05792a..0000000000
--- a/documentation/getting-started/eclipse/html/getting-started/overall-architecture.html
+++ /dev/null
@@ -1,40 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.3.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="Getting Started With Yocto Project">
8<link rel="up" href="shared-state-cache.html" title="3.3. Shared State Cache">
9<link rel="prev" href="shared-state-cache.html" title="3.3. Shared State Cache">
10<link rel="next" href="overview-checksums.html" title="3.3.2. Checksums (Signatures)">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.3.1. Overall Architecture">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="overall-architecture"></a>3.3.1. Overall Architecture</h3></div></div></div>
15<p>
16 When determining what parts of the system need to be built,
17 BitBake works on a per-task basis rather than a per-recipe
18 basis.
19 You might wonder why using a per-task basis is preferred over
20 a per-recipe basis.
21 To help explain, consider having the IPK packaging backend
22 enabled and then switching to DEB.
23 In this case, the
24 <a class="link" href="../ref-manual/ref-tasks-install.html" target="_self"><code class="filename">do_install</code></a>
25 and
26 <a class="link" href="../ref-manual/ref-tasks-package.html" target="_self"><code class="filename">do_package</code></a>
27 task outputs are still valid.
28 However, with a per-recipe approach, the build would not
29 include the <code class="filename">.deb</code> files.
30 Consequently, you would have to invalidate the whole build and
31 rerun it.
32 Rerunning everything is not the best solution.
33 Also, in this case, the core must be "taught" much about
34 specific tasks.
35 This methodology does not scale well and does not allow users
36 to easily add new tasks in layers or as external recipes
37 without touching the packaged-staging core.
38 </p>
39</div></body>
40</html>