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/structure-core-script.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/structure-core-script.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html | 53 |
1 files changed, 0 insertions, 53 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html deleted file mode 100644 index 64266a9482..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html +++ /dev/null | |||
| @@ -1,53 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>5.1.10. oe-init-build-env</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="structure-core.html" title="5.1. Top level core components"> | ||
| 9 | <link rel="prev" href="structure-core-scripts.html" title="5.1.9. scripts/"> | ||
| 10 | <link rel="next" href="structure-basic-top-level.html" title="5.1.11. LICENSE, README, and README.hardware"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.10. oe-init-build-env"> | ||
| 13 | <div class="titlepage"><div><div><h3 class="title"> | ||
| 14 | <a name="structure-core-script"></a>5.1.10. <code class="filename">oe-init-build-env</code> | ||
| 15 | </h3></div></div></div> | ||
| 16 | <p> | ||
| 17 | This script sets up the OpenEmbedded build environment. | ||
| 18 | Running this script with the <code class="filename">source</code> command in | ||
| 19 | a shell makes changes to <code class="filename">PATH</code> and sets other core BitBake variables based on the | ||
| 20 | current working directory. | ||
| 21 | You need to run this script before running BitBake commands. | ||
| 22 | The script uses other scripts within the <code class="filename">scripts</code> directory to do | ||
| 23 | the bulk of the work. | ||
| 24 | </p> | ||
| 25 | <p> | ||
| 26 | By default, running this script without a Build Directory argument creates the | ||
| 27 | <code class="filename">build</code> directory. | ||
| 28 | If you provide a Build Directory argument when you <code class="filename">source</code> | ||
| 29 | the script, you direct OpenEmbedded build system to create a | ||
| 30 | <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a> of your choice. | ||
| 31 | For example, the following command creates a Build Directory named | ||
| 32 | <code class="filename">mybuilds</code> that is outside of the | ||
| 33 | <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>: | ||
| 34 | </p> | ||
| 35 | <pre class="literallayout"> | ||
| 36 | $ source oe-init-build-env ~/mybuilds | ||
| 37 | </pre> | ||
| 38 | <p> | ||
| 39 | </p> | ||
| 40 | <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> | ||
| 41 | <h3 class="title">Note</h3> | ||
| 42 | The OpenEmbedded build system does not support file or directory names that | ||
| 43 | contain spaces. | ||
| 44 | If you attempt to run the <code class="filename">oe-init-build-env</code> script | ||
| 45 | from a Source Directory that contains spaces in either the filenames | ||
| 46 | or directory names, the script returns an error indicating no such | ||
| 47 | file or directory. | ||
| 48 | Be sure to use a Source Directory free of names containing spaces. | ||
| 49 | </div> | ||
| 50 | <p> | ||
| 51 | </p> | ||
| 52 | </div></body> | ||
| 53 | </html> | ||