diff options
Diffstat (limited to 'documentation/adt-manual/adt-command.xml')
| -rw-r--r-- | documentation/adt-manual/adt-command.xml | 66 |
1 files changed, 0 insertions, 66 deletions
diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml deleted file mode 100644 index e57c15a983..0000000000 --- a/documentation/adt-manual/adt-command.xml +++ /dev/null @@ -1,66 +0,0 @@ -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" -"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> - -<chapter id='using-the-command-line'> -<title>Using the Command Line</title> - <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 - (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. - 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, - 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 - makefile-based projects. - </para> - -<section id='autotools-based-projects'> -<title>Autotools-Based Projects</title> - <para> - For an autotools-based project you can use the cross-toolchain by just - passing the appropriate host option to <filename>configure.sh</filename>. - The host option you use is derived from the name of the environment setup - script in <filename>/opt/poky</filename> resulting from unpacking the - cross-toolchain tarball. - For example, the host option for an ARM-based target that uses the GNU EABI - is <filename>armv5te-poky-linux-gnueabi</filename>. - Note that the name of the script is - <filename>environment-setup-armv5te-poky-linux-gnueabi</filename>. - Thus, the following command works: - <literallayout class='monospaced'> - $ configure ‐‐host-armv5te-poky-linux-gnueabi ‐‐with-libtool-sysroot=<sysroot-dir> - </literallayout> - </para> - <para> - This single command updates your project and rebuilds it using the appropriate - cross-toolchain tools. - </para> -</section> - -<section id='makefile-based-projects'> -<title>Makefile-Based Projects</title> - <para> - For a makefile-based project you use the cross-toolchain by making sure - the tools are used. - You can do this as follows: - <literallayout class='monospaced'> - CC=arm-poky-linux-gnueabi-gcc - LD=arm-poky-linux-gnueabi-ld - CFLAGS=”${CFLAGS} ‐‐sysroot=<sysroot-dir>” - CXXFLAGS=”${CXXFLAGS} ‐‐sysroot=<sysroot-dir>” - </literallayout> - </para> -</section> - -</chapter> -<!-- -vim: expandtab tw=80 ts=4 ---> |