From c4a923bcb0194c05b14d40be7ad4ecd193eb7a69 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 13 Sep 2012 14:01:58 -0700 Subject: documentation: Toolchain corrections from tarball to .sh file For 1.3 there is not longer a toolchain tarball. Instead, there is a wrapper script that lets you install the tarball. This fundamental usage model change caused several ripples throughout the documentation set. I have changed wordings and examples to reflect the new paradigm. (From yocto-docs rev: afb2069daa91e04c0f78ba425a6b184cb820d888) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-start.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'documentation/dev-manual/dev-manual-start.xml') diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 3209cb29b7..6e204d85e0 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -313,9 +313,9 @@ Regardless of the type of image you are using, you need to download the pre-built kernel that you will boot in the QEMU emulator and then download and extract the target root filesystem for your target machine’s architecture. - You can get architecture-specific binaries and filesystem from + You can get architecture-specific binaries and filesystems from machines. - You can get stand-alone toolchains from + You can get installation scripts for stand-alone toolchains from toolchains. Once you have all your files, you set up the environment to emulate the hardware by sourcing an environment setup script. -- cgit v1.2.3-54-g00ecf