Cross Compiling
Cross Compilers are needed to reduce the computational load on embedded machines, and also significantly reduce packages required to build for those machines. For an in-depth explanation on cross compiling, please check out the Wikipedia articles on cross-compilation and cross-compilers.
Modus Operandi for Escher Developers
By far the easiest thing to do is use a crosscompiler which we have built on a local Berkeley machine, and use it to build your sources. There are several possibilities for this:
ransom.eecs.berkeley.eduThis is a dual processor Pentium Xeon machine with all of the drivespace and processor space you could want. It is running Microsoft Windows Terminal Server, and can handle arbitrarily many concurrent logins through Remote Desktop (a.k.a. Microsoft Terminal Server Client, mstsc.exe). You must be a member of the permitted users list to use this machine, e-mail sprinkle@EECS in order to gain access.On this machine are located several crosscompilers. Use the following steps to select a crosscompiler on that machine, after logging in and starting up a cygwin shell:
[sprinkle@ransom ~]
$ cd /usr/local/escher/crosscompile
[sprinkle@ransom /usr/local/escher/crosscompile]
$ source select_crosscompiler
$ cd /usr/local/escher/crosscompile
[sprinkle@ransom /usr/local/escher/crosscompile]
$ source select_crosscompiler
- See the crosscompiler setup page for more information.
dgc3.eecs.berkeley.edu(description of dgc3...)
My code block
[sprinkle@bruce ~]$ cd /usr/local/escher/crosscompiler
[sprinkle@bruce /usr/local/escher/crosscompile]
$ source select_crosscompiler