diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml
index 4000c924c3..d010aad591 100644
--- a/documentation/adt-manual/adt-command.xml
+++ b/documentation/adt-manual/adt-command.xml
@@ -29,39 +29,168 @@
Autotools-Based Projects
- 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
- cross-toolchain tarball.
- For example, the host option for an ARM-based target that uses the GNU EABI
- is armv5te-poky-linux-gnueabi.
- Note that the name of the script is
- environment-setup-armv5te-poky-linux-gnueabi.
- Thus, the following command works:
-
+ 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
+ to set up, compile, and run the project.
+
+
+
+
+
+ Passing Host Options
+
+
+ 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
+ cross-toolchain tarball.
+ 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
+ environment-setup-armv5te-poky-linux-gnueabi.
+ Thus, the following command works:
+
$ configure --host=armv5te-poky-linux-gnueabi \
--with-libtool-sysroot=<sysroot-dir>
-
-
-
- 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
- re-running the script:
-
+
+
+
+
+ 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
+ re-running the script:
+
$ libtoolize --automake
$ aclocal -I ${OECORE_NATIVE_SYSROOT}/usr/share/aclocal \
[-I <dir_containing_your_project-specific_m4_macros>]
$ autoconf
$ autoheader
$ automake -a
-
-
+
+
+
+
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 3fd231c6a0..040618482f 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -18,7 +18,7 @@
The following list describes installation methods that set up varying degrees of tool
- availabiltiy on your system.
+ availability on your system.
Regardless of the installation method you choose,
you must source the cross-toolchain
environment setup script before you use a toolchain.
@@ -258,9 +258,17 @@
bitbake meta-toolchain.
Use the appropriate bitbake command only after you have
sourced the &OE_INIT_PATH; script located in the Source
- Directory.
- When the bitbake command completes, the toolchain installer will
- be in tmp/deploy/sdk in the Build Directory.
+ Directory and you have made sure your conf/local.conf
+ variables are correct.
+ In particular, you need to be sure the
+ MACHINE
+ variable matches the architecture for which you are building and that the
+ SDKMACHINE variable is correctly set if you are building
+ a toolchain for an architecture that differs from your current
+ development host machine.
+ When the bitbake command completes, the
+ toolchain installer will be in tmp/deploy/sdk in the
+ Build Directory.
Once you have the installer, run it to install the toolchain.