From ed0a240e1632682ec4c33341f3e24ad71773cdfc Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 11 Dec 2012 12:07:58 -0600 Subject: 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 Signed-off-by: Richard Purdie --- .../html/poky-ref-manual/build-overview.html | 61 ++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html') 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 @@ + + + +2.1.1. Build Overview + + + + + + + +
+

+2.1.1. Build Overview

+

+ The first thing you need to do is set up the OpenEmbedded build environment by sourcing + the environment setup script as follows: +

+
+     $ source oe-init-build-env [build_dir]
+            
+

+

+

+ The build_dir is optional and specifies the directory the + OpenEmbedded build system uses for the build - + the Build Directory. + If you do not specify a Build Directory it defaults to build + in your current working directory. + A common practice is to use a different Build Directory for different targets. + For example, ~/build/x86 for a qemux86 + target, and ~/build/arm for a qemuarm target. + See oe-init-build-env + for more information on this script. +

+

+ Once the build environment is set up, you can build a target using: +

+
+     $ bitbake <target>
+            
+

+

+

+ The target is the name of the recipe you want to build. + Common targets are the images in meta/recipes-core/images, + /meta/recipes-sato/images, etc. all found in the + Source Directory. + Or, the target can be the name of a recipe for a specific piece of software such as + busybox. + For more details about the images the OpenEmbedded build system supports, see the + "Images" chapter. +

+
+

Note

+ Building an image without GNU General Public License Version 3 (GPLv3) components + is only supported for minimal and base images. + See the "Images" chapter for more information. +
+
+ -- cgit v1.2.3-54-g00ecf