diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index cdb799d915..f59fae35c2 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -1448,45 +1448,57 @@ directory. Workflow Using Stand-alone Cross-development Toolchains - If you want to develop an application without prior installation of the ADT, you - still can employ the cross-development toolchain, the QEMU emulator, and a number of supported - target image files. + If you want to develop an application without prior installation + of the ADT, you still can employ the + Cross Development Toolchain, + the QEMU emulator, and a number of supported target image files. You just need to follow these general steps: - Install the cross-development toolchain for your target hardware: + Install the cross-development + toolchain for your target hardware: For information on how to install the toolchain, see the "Using a Cross-Toolchain Tarball" - section - in the Yocto Project Application Developer's Guide. - Download the Target Image: The Yocto Project supports - several target architectures and has many pre-built kernel images and root filesystem + section in the Yocto Project Application Developer's + Guide. + Download the Target Image: + The Yocto Project supports several target architectures + and has many pre-built kernel images and root filesystem images. - If you are going to develop your application on hardware, go to the + If you are going to develop your application on + hardware, go to the machines download area and choose a target machine area from which to download the kernel image and root filesystem. - This download area could have several files in it that support development using - actual hardware. - For example, the area might contain .hddimg files that combine the + This download area could have several files in it that + support development using actual hardware. + For example, the area might contain + .hddimg files that combine the kernel image with the filesystem, boot loaders, etc. - Be sure to get the files you need for your particular development process. - If you are going to develop your application and then run and test it using the QEMU - emulator, go to the + Be sure to get the files you need for your particular + development process. + If you are going to develop your application and + then run and test it using the QEMU emulator, go to the machines/qemu download area. - From this area, go down into the directory for your target architecture - (e.g. qemux86_64 for an - Intel-based 64-bit architecture). - Download kernel, root filesystem, and any other files you need for your process. - In order to use the root filesystem in QEMU, you need to extract it. + From this area, go down into the directory for your + target architecture (e.g. qemux86_64 + for an Intel-based + 64-bit architecture). + Download kernel, root filesystem, and any other files you + need for your process. + In order to use the root filesystem in QEMU, you + need to extract it. See the "Extracting the Root Filesystem" - section for information on how to extract the root filesystem. - Develop and Test your Application: At this point, - you have the tools to develop your application. - If you need to separately install and use the QEMU emulator, you can go to - QEMU Home Page to download and learn about the - emulator. + section for information on how to extract the root + filesystem. + Develop and Test your + Application: At this point, you have the tools + to develop your application. + If you need to separately install and use the QEMU + emulator, you can go to + QEMU Home Page + to download and learn about the emulator. diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index 169f3072ef..7c21379b99 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml @@ -311,17 +311,61 @@ variables for the Texas Instruments ARM Cortex-A8 development board). Configuration files end with a .conf filename extension. - Cross-Development Toolchain: + + Cross-Development Toolchain: A collection of software development - tools and utilities that allow you to develop software for targeted architectures. - This toolchain contains cross-compilers, linkers, and debuggers that are specific to - an architecture. - You can use the OpenEmbedded build system to build a cross-development toolchain - installer that when run installs the toolchain that contains the development tools you + tools and utilities that allow you to develop software for + targeted architectures. + This toolchain contains cross-compilers, linkers, and debuggers + that are specific to an architecture. + You can use the OpenEmbedded build system to build a + cross-development toolchain installer that, when run, installs + the toolchain that contains the development tools you need to cross-compile and test your software. The Yocto Project ships with images that contain installers for toolchains for supported architectures as well. - Sometimes this toolchain is referred to as the meta-toolchain. + Sometimes this toolchain is referred to as the + meta-toolchain. + Following is a list of toolchain recipes with brief + descriptions of each: + + gcc-cross-initial: + The initial compiler needed to bootstrap the toolchain + that runs on the host and is used to build software + for the target. + This tool is a 'native' package. + gcc-cross-intermediate: + The second stage of the bootstrap process that runs + on the host and builds software for the target. + This tool is a 'native' package. + gcc-cross: + The the final stage of the bootstrap process that + results in the cross compiler that runs on the host + and builds software for the target. + If you are replacing the cross compiler toolchain + with a custom version, this is what you must replace. + This tool is a 'native' package. + gcc-runtime: + Runtime libraries from the toolchain bootstrapping + process. + This tool produces a binary for the target. + + gcc-crosssdk-initial/intermediate: + Stage 1 and 2 of the a cross compiler that runs on the + host and builds for the SDK. + Often the SDK is not the same target as the host. + This tool is a 'native' binary. + gcc-crosssdk: + The final stage of the SDK compiler. + This tool is a 'native' binary. + The tool runs on the host and builds for the SDK. + + gcc-cross-canadian: + The compiler that runs on the SDK machine and is + included with the SDK that builds software for the + target. + This tool is a 'nativesdk' package. + Image: An image is the result produced when BitBake processes a given collection of recipes and related metadata. Images are the binary output that run on specific hardware or QEMU