diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-12-11 12:07:58 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-01-07 14:43:25 +0000 |
| commit | ed0a240e1632682ec4c33341f3e24ad71773cdfc (patch) | |
| tree | 201557f498b77b9f51fad7e12a6009f74aca4c65 /documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html | |
| parent | af19d889ef320f9625aae42eed6688b5cc739793 (diff) | |
| download | poky-ed0a240e1632682ec4c33341f3e24ad71773cdfc.tar.gz | |
documentation: Rename of poky-ref-manual folder to ref-manual.
Changing the folder that holds the YP Reference Manual to be
"ref-manual". This will help with confustion over the manual's
intended purpose.
(From yocto-docs rev: 1106442964b5080cb0b6b3bd3af32e9407c0f7c1)
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/build-overview.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html | 61 |
1 files changed, 61 insertions, 0 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html new file mode 100644 index 0000000000..4ee4185ba9 --- /dev/null +++ b/documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html | |||
| @@ -0,0 +1,61 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>2.1.1. Build Overview</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="usingpoky-build.html" title="2.1. Running a Build"> | ||
| 9 | <link rel="prev" href="usingpoky-build.html" title="2.1. Running a Build"> | ||
| 10 | <link rel="next" href="building-an-image-using-gpl-components.html" title="2.1.2. Building an Image Using GPL Components"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1.1. Build Overview"> | ||
| 13 | <div class="titlepage"><div><div><h3 class="title"> | ||
| 14 | <a name="build-overview"></a>2.1.1. Build Overview</h3></div></div></div> | ||
| 15 | <p> | ||
| 16 | The first thing you need to do is set up the OpenEmbedded build environment by sourcing | ||
| 17 | the <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">environment setup script</a> as follows: | ||
| 18 | </p> | ||
| 19 | <pre class="literallayout"> | ||
| 20 | $ source oe-init-build-env [build_dir] | ||
| 21 | </pre> | ||
| 22 | <p> | ||
| 23 | </p> | ||
| 24 | <p> | ||
| 25 | The <code class="filename">build_dir</code> is optional and specifies the directory the | ||
| 26 | OpenEmbedded build system uses for the build - | ||
| 27 | the <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>. | ||
| 28 | If you do not specify a Build Directory it defaults to <code class="filename">build</code> | ||
| 29 | in your current working directory. | ||
| 30 | A common practice is to use a different Build Directory for different targets. | ||
| 31 | For example, <code class="filename">~/build/x86</code> for a <code class="filename">qemux86</code> | ||
| 32 | target, and <code class="filename">~/build/arm</code> for a <code class="filename">qemuarm</code> target. | ||
| 33 | See <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">oe-init-build-env</a> | ||
| 34 | for more information on this script. | ||
| 35 | </p> | ||
| 36 | <p> | ||
| 37 | Once the build environment is set up, you can build a target using: | ||
| 38 | </p> | ||
| 39 | <pre class="literallayout"> | ||
| 40 | $ bitbake <target> | ||
| 41 | </pre> | ||
| 42 | <p> | ||
| 43 | </p> | ||
| 44 | <p> | ||
| 45 | The <code class="filename">target</code> is the name of the recipe you want to build. | ||
| 46 | Common targets are the images in <code class="filename">meta/recipes-core/images</code>, | ||
| 47 | <code class="filename">/meta/recipes-sato/images</code>, etc. all found in the | ||
| 48 | <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>. | ||
| 49 | Or, the target can be the name of a recipe for a specific piece of software such as | ||
| 50 | <span class="application">busybox</span>. | ||
| 51 | For more details about the images the OpenEmbedded build system supports, see the | ||
| 52 | "<a class="link" href="ref-images.html" title="Chapter 8. Images">Images</a>" chapter. | ||
| 53 | </p> | ||
| 54 | <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> | ||
| 55 | <h3 class="title">Note</h3> | ||
| 56 | Building an image without GNU General Public License Version 3 (GPLv3) components | ||
| 57 | is only supported for minimal and base images. | ||
| 58 | See the "<a class="link" href="ref-images.html" title="Chapter 8. Images">Images</a>" chapter for more information. | ||
| 59 | </div> | ||
| 60 | </div></body> | ||
| 61 | </html> | ||