From 222a9cfa34811fdba7f00fa0c59b12adfd103d68 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 24 Jun 2013 18:35:15 +0300 Subject: ref-manual, adt-manual: Added links to SDKMACHINE variable. Now that a glossary entry for SDKMACHINE exists, I needed to create some links to it where referenced in the ref-manual and the adt-manual. (From yocto-docs rev: 6efe13bcda22276e5ef71ebafff6f91961b34679) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-prepare.xml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'documentation/adt-manual') diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index e2eb2afe97..a2a439d01e 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -91,8 +91,8 @@ If you use BitBake to generate the ADT Installer tarball, you must source the environment setup script - (&OE_INIT_FILE;) - located in the Source Directory before running the + (&OE_INIT_FILE;) + located in the Source Directory before running the BitBake command that creates the tarball. @@ -289,10 +289,12 @@ In particular, you need to be sure the MACHINE variable matches the architecture for which you are - building and that the SDKMACHINE + building and that the + SDKMACHINE variable is correctly set if you are building - a toolchain for an architecture that differs from your - current development host machine. + a toolchain designed to run on an architecture that + differs from your current development host machine + (i.e. the build machine). When the BitBake command completes, the toolchain installer will be in tmp/deploy/sdk in the Build -- cgit v1.2.3-54-g00ecf