Cross Compiler Article Index for
Cross 		Website Links For
Cross 		 

Information About

Cross Compiler
  CATEGORIES ABOUT CROSS COMPILER
   
cross-compilers
   
APPAREL
BABY
BEAUTY
BOOKS
CAR TOYS
CELL PHONES
DVD'S
ELECTRONICS
GOURMET FOOD
GROCERIES
HEALTH & PERSONAL
HOME & GARDEN
JEWELRY
MUSIC
MUSIC INSTRUMENTS
OFFICE PRODUCTS
SOFTWARE
SPORTING GOODS
TOOLS & HARDWARE
TOYS
VIDEO GAMES
SHOPPING HOME
MORE SHOPPING...




USES OF CROSS COMPILERS


The fundamental use of a cross compiler is to separate the build environment from the target environment. This is useful in a number of situations:
  • Embedded Computers where a device has extremely limited resources. For example, a microwave oven will have an extremely small computer to read its touchpad and door sensor, provide output to a digital display and speaker, and to control the machinery for cooking food. This computer will not be powerful enough to run a compiler, a file system, or a development environment.

  • Compiling for multiple machines. For example, a company may wish to support several different versions of an operating system or to support several different operating systems. By using a cross compiler, a single build environment can be maintained that would build for each of these targets.

  • Compiling on a Server Farm . Similar to compiling for multiple machines, a complicated build that involves many compile operations can be executed across any machine that is free regardless of its brand or current version of an operating system.

  • Bootstrapping to a new platform. When developing software for a new platform, or the emulator of a future platform, one uses a cross compiler to compile necessary tools such as the operating system and a native compiler.


Use of Virtual Machine s (such as Java's JVM ) ameliorate some of the problems for which cross compilers were developed. The virtual machine method allows the same compiler output to be by both the host and the target system.


THE GCC CROSS COMPILER

Gcc is a free cross compiler that supports dozens of platforms and a handful of languages. However, due to limited volunteer time and the huge amount of work it takes to maintain working cross compilers, in many releases some of the cross compilers are broken.

gcc relies upon the Binaries of Binutils for the targeted platform to be available. Especially important is the GNU Assembler . Therefore, binutils first has to be compiled correctly with the switch --target=some-target sent to the Configure Script . gcc also has to be configured with the same --target option. Then gcc can be compiled as normal provided that the tools binutils creates are available in the Path . On Unix-like Operating System s with Bash , that can be accomplished with the following:

PATH=/path/to/binutils/bin: make

Cross compiling gcc requires that a portion of the C Standard Library is available for the targeted platform on the host platform. At least the Crt0 , ... components of the library has to be available in some way. You can choose to compile the full C library, but that can be too large for many platforms. The alternative is to use Newlib , which is a small C Library containing only the most essential components required to get C source code compiled. To configure gcc with newlib, use the switch --with-newlib to the configure script.


CANADIAN CROSS


This is a technique for building cross compilers for other machines. That is, use machine A to build a cross compiler that runs on machine B to create executables for machine C. When using the Canadian Cross with gcc, there may be four compilers involved.

On Machine A:
  • Use the ''proprietary native Compiler for machine A (1)'' to build ''gcc native compiler for machine A (2)''.

  • Use the ''gcc native compiler for machine A (2)'' to build ''gcc cross compiler from machine A to machine B (3)''

  • Use the ''gcc cross compiler from machine A to machine B (3)'' to build ''gcc cross compiler from machine B to machine C (4)''


Note that you will not be able to execute the resulting compiler on your build machine A. You would use ''gcc cross compiler from machine B to machine C (4)'' on machine B to compile an application into executable code that would then be copied to machine C and executed on machine C.


EXTERNAL LINKS

  • http://www.kegel.com/crosstool/

  • http://www.airs.com/ian/configure/configure_5.html

  • http://gcc.gnu.org/wiki/Building%20Cross%20Toolchains%20with%20gcc