CROSS step migration tool chain

How to migrate to ARM tool chain cross platform?
Tool Chain: arm-2009q3.tar.bz2

1. First arm-2009q3.tar.bz2 placed under the shared directory
2. The crossover tool chain to create a new directory, and the permissions to
the sudo mkdir / usr / ARM
the sudo the chmod 777 / usr / ARM

3. In the arm-2009q3.tar.bz2 linux directly extracted to the installation path.
tar jxvf arm-2009q3.tar.bz2 -C / usr / arm

4. Which is the cross compiler?
/ usr / arm / arm-2009q3 / bin / arm-none-linux-gnueabi-gcc

Using a distinctive cross tool chain and local gcc compiler is?
1. Local compiler
gcc test.c -o test -> generate a test file.
file test -> see test file of this property.

test: ELF -> on behalf of the file is executed.
32-bit -> 32 Wei
LSB executable -> This file can be representative of the current execution.
Intel 80386 -> (x86 platform), indicating that the file can only be run on the x86 platform.

2. The cross compiler
/ usr / arm / arm-2009q3 / bin / arm-none-linux-gnueabi-gcc test.c -o test -> generates a test file.
file test -> see test file of this property.

test: ELF -> on behalf of the file is executed.
32-bit -> 32 Wei
LSB executable -> This file can be representative of the current execution.
ARM -> (ARM platform), indicating that the file can only be run on the ARM platform.

Generate a new file for the tool chain link.
gec @ ubuntu: / usr / arm / arm-2009q3 / bin $ sudo ln -s arm-none-linux-gnueabi-gcc arm-linux-gcc

 

How to use arm-linux-gcc in any path

Command line input gedit ~ / .bashrc script into the terminal

Was added in export PATH environment = $ PATH: / usr / arm / arm-2009q3 / bin to

Guess you like

Origin www.cnblogs.com/xdd-sdyp/p/11329314.html