From 7b4eb14c541bb41655c4340f6fbf190db1c346ed Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 23 Jun 2011 13:52:07 -0700 Subject: [PATCH] documentation/adt-manual/adt-command.xml: Small edits for terminology (From yocto-docs rev: b32290b381a6ed2cbfe3e01b748c794ef6bc876b) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-command.xml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml index e57c15a983..28501b677d 100644 --- a/documentation/adt-manual/adt-command.xml +++ b/documentation/adt-manual/adt-command.xml @@ -6,19 +6,20 @@ Recall that earlier we talked about how to use an existing toolchain tarball that had been installed into /opt/poky, - which is outside of the Poky build environment + which is outside of the Yocto Project build tree (see “Using an Existing Toolchain Tarball”). And, that sourcing your architecture-specific environment setup script - initializes a suitable development environment. + initializes a suitable cross-toolchain development environment. This setup occurs by adding the compiler, QEMU scripts, QEMU binary, a special version of pkgconfig and other useful utilities to the PATH variable. - Variables to assist pkgconfig and autotools are also defined so that, + Variables to assist pkgconfig and autotools + are also defined so that, for example, configure.sh can find pre-generated test results for tests that need target hardware on which to run. These conditions allow you to easily use the toolchain outside of the - Poky build environment on both autotools-based projects and + Yocto Project build environment on both autotools-based projects and makefile-based projects.