[Playerstage-developers] change to cross-compiling setup

[brian g. <bg...@po...>]

hi all,

Now that we have a couple of iPAQs in the lab to play with, I've tweaked
Player's cross-compiling support.

configure now takes the following two flags:

  --with-server-arch=<arch>
  --with-clients-arch=<arch>

which will, respectively, cross-build the server and the clients (including
tests and examples) for the given architecture.

At present, exactly one architecture is supported: 'arm-linux'.

If you give one or both of these flags, then configure will check for
'arm-linux-g++' in your PATH and bail if it's not found.

I've just tested a little, and pretty much everything cross-builds (I'm using
gcc-2.95.3 configured as a x86-linux -> arm-linux cross).  However, not
everything builds; in particular:

  - stage driver (some strange error, but who cares? nobody will cross-compile
      Stage anyway)

  - fixedtones driver (presumably you need to build librfftw as a cross first)

  - playerv (presumably you need to build RTK and GTK as a cross first. i'll
      bet that's not very pleasant.)

So, I recommend the following flags for the full cross-build experience:

  $ ./configure --with-server-arch=arm-linux --with-clients-arch=arm-linux \
                --without-stage --without-fixedtones --without-rtk

Of course, you may want to add/substract other drivers, and you only have to
substract fixedtones explicitly if you happen to have librfftw installed
native (and you probably don't).

John, hope I haven't broken the cross build for you.   Does it still work?

        brian.