From 3bcdba62b186c554033357bb50de0b20d115a54d Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 7 Dec 2012 17:19:36 -0600 Subject: documentation: adt-manual - Removed all trailing whitespace. (From yocto-docs rev: c1c271c0404dff9ed49597a4582a56def8237dd7) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-command.xml | 88 ++++++++++++++++---------------- 1 file changed, 44 insertions(+), 44 deletions(-) (limited to 'documentation/adt-manual/adt-command.xml') diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml index c6609193d1..e5b2cdb420 100644 --- a/documentation/adt-manual/adt-command.xml +++ b/documentation/adt-manual/adt-command.xml @@ -6,22 +6,22 @@ Using the Command Line - Recall that earlier the manual discussed how to use an existing toolchain - tarball that had been installed into /opt/poky, - which is outside of the + Recall that earlier the manual discussed how to use an existing toolchain + tarball that had been installed into /opt/poky, + which is outside of the Build Directory - (see the section "Using a Cross-Toolchain Tarball)". - And, that sourcing your architecture-specific environment setup script - initializes a suitable cross-toolchain development environment. - During the setup, locations for the compiler, QEMU scripts, QEMU binary, - a special version of pkgconfig and other useful + (see the section "Using a Cross-Toolchain Tarball)". + And, that sourcing your architecture-specific environment setup script + initializes a suitable cross-toolchain development environment. + During the setup, locations for the compiler, QEMU scripts, QEMU binary, + a special version of pkgconfig and other useful 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 - test results for tests that need target hardware on which to run. - These conditions allow you to easily use the toolchain outside of the - OpenEmbedded build environment on both autotools-based projects and + 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 + OpenEmbedded build environment on both autotools-based projects and Makefile-based projects. @@ -29,9 +29,9 @@ Autotools-Based Projects - Once you have a suitable cross-toolchain installed, it is very easy to + Once you have a suitable cross-toolchain installed, it is very easy to develop a project outside of the OpenEmbedded build system. - This section presents a simple "Helloworld" example that shows how + This section presents a simple "Helloworld" example that shows how to set up, compile, and run the project. @@ -42,7 +42,7 @@ Follow these steps to create a simple autotools-based project: Create your directory: - Create a clean directory for your project and then make + Create a clean directory for your project and then make that directory your working location: $ mkdir $HOME/helloworld @@ -78,25 +78,25 @@ AC_OUTPUT(Makefile) - Source the cross-toolchain + Source the cross-toolchain environment setup file: Installation of the cross-toolchain creates a cross-toolchain environment setup script in /opt/poky/<release>. - Before you can use the tools to develop your project, you must + Before you can use the tools to develop your project, you must source this setup script. The script begins with the string "environment-setup" and contains - the machine architecture, which is followed by the string + the machine architecture, which is followed by the string "poky-linux". - Here is an example for an environment setup using the - 32-bit Intel x86 Architecture and using the + Here is an example for an environment setup using the + 32-bit Intel x86 Architecture and using the &DISTRO_NAME; Yocto Project release: $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux Generate the local aclocal.m4 files and create the configure script: - The following GNU Autotools generate the local - aclocal.m4 files and create the + The following GNU Autotools generate the local + aclocal.m4 files and create the configure script: $ aclocal @@ -104,8 +104,8 @@ Generate files needed by GNU coding standards: - GNU coding standards require certain files in order for the - project to be compliant. + GNU coding standards require certain files in order for the + project to be compliant. This command creates those files: $ touch NEWS README AUTHORS ChangeLog @@ -122,7 +122,7 @@ $ ./configure ${CONFIGURE_FLAGS} Make and install the project: - These two commands generate and install the project into the + These two commands generate and install the project into the destination directory: $ make @@ -130,16 +130,16 @@ Verify the installation: This command is a simple way to verify the installation - of your project. - Running the command prints the architecture on which + of your project. + Running the command prints the architecture on which the binary file can run. - This architecture should be the same architecture that + This architecture should be the same architecture that the installed cross-toolchain supports. $ file ./tmp/usr/local/bin/hello Execute your project: - To execute the project in the shell, simply enter the name. + To execute the project in the shell, simply enter the name. You could also copy the binary to the actual target hardware and run the project there as well: @@ -155,14 +155,14 @@ Passing Host Options - For an Autotools-based project, you can use the cross-toolchain by just + For an Autotools-based project, you can use the cross-toolchain by just passing the appropriate host option to configure.sh. - The host option you use is derived from the name of the environment setup - script in /opt/poky resulting from installation of the + The host option you use is derived from the name of the environment setup + script in /opt/poky resulting from installation of the cross-toolchain tarball. - For example, the host option for an ARM-based target that uses the GNU EABI + For example, the host option for an ARM-based target that uses the GNU EABI is armv5te-poky-linux-gnueabi. - You will notice that the name of the script is + You will notice that the name of the script is environment-setup-armv5te-poky-linux-gnueabi. Thus, the following command works: @@ -172,12 +172,12 @@ - This single command updates your project and rebuilds it using the appropriate + This single command updates your project and rebuilds it using the appropriate cross-toolchain tools. - If configure script results in problems recognizing the - --with-libtool-sysroot=<sysroot-dir> option, - regenerate the script to enable the support by doing the following and then + If configure script results in problems recognizing the + --with-libtool-sysroot=<sysroot-dir> option, + regenerate the script to enable the support by doing the following and then re-running the script: $ libtoolize --automake @@ -187,17 +187,17 @@ $ autoheader $ automake -a - + - +
Makefile-Based Projects - For a Makefile-based project, you use the cross-toolchain by making sure - the tools are used. + For a Makefile-based project, you use the cross-toolchain by making sure + the tools are used. You can do this as follows: CC=arm-poky-linux-gnueabi-gcc -- cgit v1.2.3-54-g00ecf