From bc821a2ab59f15afa03fd238ea8cc614f8279ff4 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 20 Jan 2012 10:00:47 -0600 Subject: [PATCH] documentation/adt-manual/adt-command.xml: Corrected wording for setup Bad wording fixed to describe the changes to PATH when the setup script is run. (From yocto-docs rev: 95c6049995e8b51a46ba7fba57fcc240b6baeaaf) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-command.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml index a4197075e1..a916a03c85 100644 --- a/documentation/adt-manual/adt-command.xml +++ b/documentation/adt-manual/adt-command.xml @@ -12,9 +12,9 @@ Toolchain Tarball)". And, that sourcing your architecture-specific environment setup script initializes a suitable cross-toolchain development environment. - This setup occurs by adding the compiler, QEMU scripts, QEMU binary, + During the setup, locations for the compiler, QEMU scripts, QEMU binary, a special version of pkgconfig and other useful - utilities to the PATH variable. + utilities are added to the PATH variable. Variables to assist pkgconfig and autotools are also defined so that, for example, configure.sh can find pre-generated