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