If you want to use a program, currently not contained in the OpenWrt repository, you probably won't find a binary compiled for your CPU. Provided that it is released as open source, you can download the code and compile it using the OpenWrt Buildroot.
Note that not every code is compilable for every CPU architecture. Also performance on embedded systems is limited compared to ordinary computers.
- Follow the build instructions outlined in OpenWrt Buildroot – Usage
- Locate the toolchain binaries in the
- Add that directory to the
PATH=$PATH:(your toolchain/bin directory here)
- Set the
STAGING_DIRenvironment variable to the above toolchain dir and export it:
STAGING_DIR=(your toolchain directory here)
- Download and unpack the code to be compiled, change into the unpacked directory
- Pass the host and build to the build system of the package to trigger cross-compile
- For GNU configure, use
--build=architecture-unkown-linux-gny --host=architecture-openwrt-linux-uclibc(for example:
./configure --build=x86_64-unkown-linux-gnu –host=mips-openwrt-linux-uclibc)
./config.guessto get the
- Check the output and ensure that
'checking whether we are cross compiling… yes' is yes.
- For GNU make, override the
LDenvironment variables (usually not needed if GNU configure was used)
- The compiled program will be somewhere inside the folder your run ./configure and make from, try doing
find -iname *program*
file programto confirm cross-compiling was successful.
- If compilation aborts due to missing header files or shared objects, you might need to override
LDFLAGSto point to the
- Debugging requires gdb in the toolchain. Default config does not include it. Include using
make menuconfig. [Advanced configuration options→Toolchain Options→Build gdb]
- Remote debugging can be done using script
When compilation is finished, copy the resulting binary and related libraries to the target device to test it. It might be necessary to set
LD_LIBRARY_PATH on the target to point the binary to libraries in non-standard locations.
If the program works well enough, you maybe want to build a real package for the opkg package manager and make it easily accessible for everyone out there. See Creating your own packages and Using Dependencies for further information on that.
doc/devel/crosscompile.txt · Last modified: 2014/07/21 10:35 by nijn