From 5756282dde08673fb380223e6463060494dfef7e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 2 Aug 2011 09:36:07 -0700 Subject: documentation/dev-manual/dev-manual-model.xml: removed image description list. I moved the image description list to the Yocto Project Reference manual where it really belonged. Appropriate references were added. (From yocto-docs rev: fc74439c09d1f45cdfbc24d972045e574ffa91ec) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 104 +++----------------------- 1 file changed, 12 insertions(+), 92 deletions(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 016a0f104f..eeb792b370 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -158,56 +158,15 @@ Building an Image section of the Yocto Project Quick Start. You might want to reference this information. Build the image: The Yocto Project uses the BitBake - tool to build images based on the type of image - you want to create. + tool to build images based on the type of image you want to create. You can find more information on BitBake here. The build process supports several types of images to satisfy different needs. - When you issue the BitBake command you provide a “top-level” recipe that essentially - starts the process off of building the type of image you want. - [WRITER'S NOTE: Consider moving this to the Poky Reference Manual.] - You can find these recipes in the meta/recipes-core/images and - meta/recipes-sato/images directories of your local Yocto Project - file structure (Git repository or extracted release tarball). - Although the recipe names are somewhat explanatory, here is a list that describes them: - - Base – A foundational basic image without support - for X that can be reasonably used for customization. - Core – A foundational basic image with support for - X that can be reasonably used for customization. - Direct Disk – An image that you can copy directory to - the disk of the target device. - Live – An image you can run from a USB device or from - a CD without having to first install something. - Minimal – A small image without a GUI. - This image is not much more than a kernel with a shell. - Minimal Development – A Minimal image suitable for - development work. - Minimal Direct Disk – A Minimal Direct - Disk image. - Minimal RAM-based Initial Root Filesystem – - A minimal image - that has the initramfs as part of the kernel, which allows the - system to find the first “init” program more efficiently. - Minimal Live – A Minimal Live image. - Minimal MTD Utilities – A minimal image that has support - for the MTD utilities, which let the user interact with the MTD subsystem in - the kernel to perform operations on flash devices. - Sato – An image with Sato support, a mobile environment - and visual style that works well with mobile devices. - Sato Development – A Sato image suitable for - development work. - Sato Direct Disk – A Sato Direct - Disk image. - Sato Live – A Sato Live image. - Sato SDK – A Sato image that includes the Yocto Project - toolchain and development libraries. - Sato SDK Direct Disk – A Sato SDK Direct - Disk image. - Sato SDK Live – A Sato SDK Live - image. - - + See + + Reference: Images in the + + Yocto Project Reference Manualfor information on supported images. @@ -387,51 +346,12 @@ You can find more information on BitBake here. The build process supports several types of images to satisfy different needs. - When you issue the BitBake command you provide a “top-level” recipe that essentially - starts the process off of building the type of image you want. - [WRITER'S NOTE: Consider moving this to the Poky Reference Manual.] - You can find these recipes in the meta/recipes-core/images and - meta/recipes-sato/images directories of your local Yocto Project - file structure (Git repository or extracted release tarball). - Although the recipe names are somewhat explanatory, here is a list that describes them: - - Base – A foundational basic image without support - for X that can be reasonably used for customization. - Core – A foundational basic image with support for - X that can be reasonably used for customization. - Direct Disk – An image that you can copy directory to - the disk of the target device. - Live – An image you can run from a USB device or from - a CD without having to first install something. - Minimal – A small image without a GUI. - This image is not much more than a kernel with a shell. - Minimal Development – A Minimal image suitable for - development work. - Minimal Direct Disk – A Minimal Direct - Disk image. - Minimal RAM-based Initial Root Filesystem – - A minimal image - that has the initramfs as part of the kernel, which allows the - system to find the first “init” program more efficiently. - Minimal Live – A Minimal Live image. - Minimal MTD Utilities – A minimal image that has support - for the MTD utilities, which let the user interact with the MTD subsystem in - the kernel to perform operations on flash devices. - Sato – An image with Sato support, a mobile environment - and visual style that works well with mobile devices. - Sato Development – A Sato image suitable for - development work. - Sato Direct Disk – A Sato Direct - Disk image. - Sato Live – A Sato Live image. - Sato SDK – A Sato image that includes the Yocto Project - toolchain and development libraries. - Sato SDK Direct Disk – A Sato SDK Direct - Disk image. - Sato SDK Live – A Sato SDK Live - image. - - + See + + Reference: Images in the + + Yocto Project Reference Manual for information on supported + images. Make your configuration changes available in the kernel layer: Up to this point all the configuration changes to the kernel have been done and tested iteratively. -- cgit v1.2.3-54-g00ecf