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 found in the directory in which you
installed the cross-toolchain.
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 to update your project and
rebuild it using the appropriate cross-toolchain tools:
$ ./configure --host=armv5te-poky-linux-gnueabi \
--with-libtool-sysroot=sysroot_dir
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 run the script again:
$ libtoolize --automake
$ aclocal -I ${OECORE_TARGET_SYSROOT}/usr/share/aclocal [-I dir_containing_your_project-specific_m4_macros
]
$ autoconf
$ autoheader
$ automake -a