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 <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
aa72ed0b23
commit
bc821a2ab5
|
@ -12,9 +12,9 @@
|
||||||
Toolchain Tarball)</link>".
|
Toolchain Tarball)</link>".
|
||||||
And, that sourcing your architecture-specific environment setup script
|
And, that sourcing your architecture-specific environment setup script
|
||||||
initializes a suitable cross-toolchain development environment.
|
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 <filename>pkgconfig</filename> and other useful
|
a special version of <filename>pkgconfig</filename> and other useful
|
||||||
utilities to the <filename>PATH</filename> variable.
|
utilities are added to the <filename>PATH</filename> variable.
|
||||||
Variables to assist <filename>pkgconfig</filename> and <filename>autotools</filename>
|
Variables to assist <filename>pkgconfig</filename> and <filename>autotools</filename>
|
||||||
are also defined so that,
|
are also defined so that,
|
||||||
for example, <filename>configure.sh</filename> can find pre-generated
|
for example, <filename>configure.sh</filename> can find pre-generated
|
||||||
|
|
Loading…
Reference in New Issue