first, we need a cross compiler, which you can download from the source or somewhere.
second, when we use gcc to build stuff, actually we are implicitly linking to the stdlib of c, if we are cross compiling programs for another platform, then we need another platform's filesystem to be accessible to us. However, we only need the target's /usr directory, because that's where the header files lives in.
we place target's header files in a directory called sysroot, and gcc supports the argument
| options | explaination | | -------- | ------------------------------------------------ | | --build | the machine which you build on | | --host | the machine which your binary will be running on | | --target | the machine that GCC will produce code for | | --build | --host | --target | result | | ------- | ------ | -------- | ------------- | | - | - | - | native | | - | - | x | cross complie |
LDFLAGS="$LDFLAGS -m32 ?
--target makes sense only when building compiler (e.g. GCC).
Let's assume you have a directory called ~/x-compile
You have your tool-chain installed, that it is the correct tool-chain and the PATH environment variable is correctly set, so that the cross-compiler and all other cross-tools binaries can be called from any folder.
You have the sysroot installed in ~/x-compile/sysroot
Your code depends on a library for which you have the source code in ~/x-compile/depsrc/
You have the source code to be cross-compiled in ~/x-compile/src
compile you dependency lib, if your dependency lib don't need stdlib
./configure CC=arm-linux-gnueabihf-gcc --prefix=~/x-compile/deps --host=arm-linux-gnueabihf make make install
if your dependency needs system libs, then you need
--sysroot as below
http://www.fabriziodini.eu/posts/cross_compile_tutorial/ https://landley.net/writing/docs/cross-compiling.html http://stackoverflow.com/questions/5139403/whats-the-difference-of-configure-option-build-host-and-target
very confusing, the second answer is better