From a41a805500cab281fba15bd8e5d3e60b88d0d4be Mon Sep 17 00:00:00 2001 From: Timo Mueller Date: Fri, 8 Feb 2013 09:16:33 -0600 Subject: 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 Signed-off-by: Richard Purdie --- .../html/poky-ref-manual/build-overview.html | 61 ---------------------- 1 file changed, 61 deletions(-) delete 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 deleted file mode 100644 index 4ee4185ba9..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html +++ /dev/null @@ -1,61 +0,0 @@ - - - -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