diff options
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/adt-manual/adt-command.xml | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml index e57c15a..28501b6 100644 --- a/documentation/adt-manual/adt-command.xml +++ b/documentation/adt-manual/adt-command.xml @@ -6,19 +6,20 @@ <para> Recall that earlier we talked about how to use an existing toolchain tarball that had been installed into <filename>/opt/poky</filename>, - which is outside of the Poky build environment + which is outside of the Yocto Project build tree (see <xref linkend='using-an-existing-toolchain-tarball'> “Using an Existing Toolchain Tarball”)</xref>. 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 <filename>pkgconfig</filename> and other useful utilities to the <filename>PATH</filename> variable. - Variables to assist pkgconfig and autotools are also defined so that, + Variables to assist <filename>pkgconfig</filename> and <filename>autotools</filename> + are also defined so that, for example, <filename>configure.sh</filename> 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. </para> |
