Originally Posted by twobob
Since you have your notebook out now ...
For handwritten, off-the-wall, makefiles - -
Nothing replaces reading the author's work and if they don't use the commonly accepted build variables in commonly accepted ways, trying to "get inside their head" to cross-compile their work.
For autotools based sources (./configure, make, make install) you will need sb2 to cross-compile, or any of the various "native mode" tools because configure will insist on creating the output files based on what it finds on the host rather than the target.
Cmake based sources - I don't have a lot of experience with those, from what I read they **should** cross-compile but rarely do.
And then you run into things like: http://www.creytiv.com/baresip.html
Two library sets, a demo program and a client program.
Lots of good things in those library sets (A/V codecs, low level bit and byte bashing, etc.) which might be of use to various projects here.
Step one of cross-compiling anything: read the Makefile (with capital M). Your next move will be based on what you find there.
First impression - cross-compiling other than from mingw32 to linux will be a lot of fun.
It might be quicker to do this one as an "emulated native" build under Aboriginal Linux http://landley.net/aboriginal/about.html
See the following post for a quick tour of building a static application using Rob Landley's Aboriginal Linux.