On Monday 28 April 2008, Dave Bender wrote: > That is currently the solution I use for x86. The drawbacks are > slower compilation performance (cross compilers running on 64 bit > empirically seem faster) and other overhead caused by chrooting. The > approach also does not extend to other architectures like ARM. > Essentially this approach is a lightweight emulation; taken to its > fullest extent you would be running QEMU to build for these other > architectures.
you could distcc with the host system. i dont know about "other overhead caused by chrooting" though ... being in a chroot really adds no overhead at all. while you can argue the non-native point if you were targeting something non-native, Matthijs point is pretty clear: since you can easily do native, you probably should as over all it will be a much smoother development cycle. -mike
signature.asc
Description: This is a digitally signed message part.
