diff options
author | Timo Mueller <timo.mueller@bmw-carit.de> | 2013-02-08 09:16:33 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-02-14 17:25:35 +0000 |
commit | a41a805500cab281fba15bd8e5d3e60b88d0d4be (patch) | |
tree | 9973678912b57cfdef5b1f9676794a556b4d8966 /documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html | |
parent | 768152340898cbb9faed6e8865a4e35c69833230 (diff) | |
download | poky-a41a805500cab281fba15bd8e5d3e60b88d0d4be.tar.gz |
documentation: Part 1 of 2 updates to integrating docs to Eclipse help.
Hi,
the generation of eclipse help files has been merged from the timo
branch to the master. Since the creation of the timo branch there have
been some changes to the master branch (e.g. new documentation,
renamed documentation).
This patch set does some cleanup for the renamed documentation and
adds eclipse help generation support to the new documentation.
01: Removes the 'the' from the document titles
02..04: Cleanup obsolete artifacts resulting from the merge
05..08: Add eclipse help generation for ref-manual
09..13: Add eclipse help generation for kernel-dev
14..18: Add eclipse help generation for profile-manual
Best regards,
Timo
This patch set originally contained 18 patches. I (Scott Rifenbark)
had to push these changes as two parts. This is the first part.
It does not include creation of the three cusomization files.
(From yocto-docs rev: 9b1889f6e31ee70dae704fa08763fb9196616dad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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> | ||