diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml
index 9aa25fad40..164b1efbff 100644
--- a/documentation/adt-manual/adt-command.xml
+++ b/documentation/adt-manual/adt-command.xml
@@ -177,7 +177,7 @@
Thus, the following command works:
$ ./configure --host=armv5te-poky-linux-gnueabi \
- --with-libtool-sysroot=<sysroot-dir>
+ --with-libtool-sysroot=sysroot-dir
@@ -186,13 +186,13 @@
cross-toolchain tools.
If the configure script results in problems recognizing the
- --with-libtool-sysroot=<sysroot-dir> option,
+ --with-libtool-sysroot=sysroot-dir option,
regenerate the script to enable the support by doing the following and then
run the script again:
$ libtoolize --automake
$ aclocal -I ${OECORE_NATIVE_SYSROOT}/usr/share/aclocal \
- [-I <dir_containing_your_project-specific_m4_macros>]
+ [-I dir_containing_your_project-specific_m4_macros]
$ autoconf
$ autoheader
$ automake -a
diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml
index da032eee5b..5c3196ea91 100644
--- a/documentation/adt-manual/adt-package.xml
+++ b/documentation/adt-manual/adt-package.xml
@@ -80,17 +80,17 @@
Next, source the environment setup script found in the
Source Directory.
Follow that by setting up the installation destination to point to your
- sysroot as <sysroot_dir>.
- Finally, have an OPKG configuration file <conf_file>
+ sysroot as sysroot_dir.
+ Finally, have an OPKG configuration file conf_file
that corresponds to the opkg repository you have just created.
The following command forms should now work:
- $ opkg-cl –f <conf_file> -o <sysroot_dir> update
- $ opkg-cl –f <cconf_file> -o <sysroot_dir> \
+ $ opkg-cl –f conf_file -o sysroot_dir update
+ $ opkg-cl –f cconf_file -o sysroot_dir \
--force-overwrite install libglade
- $ opkg-cl –f <cconf_file> -o <sysroot_dir> \
+ $ opkg-cl –f cconf_file -o sysroot_dir \
--force-overwrite install libglade-dbg
- $ opkg-cl –f <conf_file> -o <sysroot_dir> \
+ $ opkg-cl –f conf_file> -o sysroot_dir> \
--force-overwrite install libglade-dev
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 89ef09fb24..7faf39b9e2 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -183,20 +183,20 @@
Please make sure you understand the security implications of doing this.
You might also have to modify your firewall settings to allow
NFS booting to work.
- YOCTOADT_ROOTFS_<arch>: The root
+ YOCTOADT_ROOTFS_arch: The root
filesystem images you want to download from the
YOCTOADT_IPKG_REPO repository.
- YOCTOADT_TARGET_SYSROOT_IMAGE_<arch>: The
+ YOCTOADT_TARGET_SYSROOT_IMAGE_arch: The
particular root filesystem used to extract and create the target sysroot.
The value of this variable must have been specified with
- YOCTOADT_ROOTFS_<arch>.
+ YOCTOADT_ROOTFS_arch.
For example, if you downloaded both minimal and
sato-sdk images by setting
- YOCTOADT_ROOTFS_<arch>
- to "minimal sato-sdk", then YOCTOADT_ROOTFS_<arch>
+ YOCTOADT_ROOTFS_arch
+ to "minimal sato-sdk", then YOCTOADT_ROOTFS_arch
must be set to either "minimal" or "sato-sdk".
- YOCTOADT_TARGET_SYSROOT_LOC_<arch>: The
+ YOCTOADT_TARGET_SYSROOT_LOC_arch: The
location on the development host where the target sysroot is created.
@@ -212,7 +212,7 @@
Once the installer begins to run, you are asked to enter the
location for cross-toolchain installation.
The default location is
- /opt/poky/<release>.
+ /opt/poky/release.
After either accepting the default location or selecting your
own location, you are prompted to run the installation script
interactively or in silent mode.
@@ -230,7 +230,7 @@
adt-installer directory according to your
installer configurations, and the target sysroot located
according to the
- YOCTOADT_TARGET_SYSROOT_LOC_<arch>
+ YOCTOADT_TARGET_SYSROOT_LOC_arch
variable also in your configuration file.
@@ -593,7 +593,7 @@
section.
- Use bitbake <image> -c populate_sdk.
+ Use bitbake image -c populate_sdk.
This method has significant advantages over the previous method
because it results in a toolchain installer that contains the
sysroot that matches your target root filesystem.