Cross compilation
Posted Nov 11, 2005 22:08 UTC (Fri) by
oak (subscriber, #2786)
In reply to:
Cross compilation by ringerc
Parent article:
Cell Broadband Engine Software Development Kit Version 1.0
> will wince whenever you say "is that a target binary, a host binary, or
both?"
>
> Cross compilation is in my limited experience a serious pain
You haven't tried Scratchbox from www.scratchbox.org?
With that you can run on your desktop both target and host binaries,
target binaries are automatically run either in an emulator (currently
Qemu) or if there's not good enough emulation, transparently over the
network on a target system with NFS exported development environment.
For latter, you only need to enable NFS in the target kernel and have a
small daemon running on it. After you've done your development & testing,
you just reboot the target machine with your devel env as it's NFS root
and proceed with system testing (startup etc)...
> If you have the misfortune to need to cross compile software that hasn't
> been cross-compiled from the beginning, it seems to be remarkably
> unpleasant much of the time.
Scratchbox has been developed to handle that kind of a stuff and to even
cross-compile whole distributions. All the autoconf crap works just fine
without any modifications and even cross-building Debian is now possible.
(which is AFAIK impossible with any other tool because of the circular
dependencies in Debian base packages and other problems)
Only things which are a bit of a pain / not always handled automatically
are situations where program wants to compile the same library both as a
host and target binary (e.g. Mozilla), or where as a part of build
process, the target software wants to install a binary extension to a
scripting language (perl, python, m4) which is used also on the
cross-compilation environment as host tool (for speed reasons).
(
Log in to post comments)
