Revisions to Installing a cross-toolchain to build ARM binaries on Debian

Corrected a line that was not belonging

edited Dec 10, 2014 at 18:01

11
2

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file should look something like this:

export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH} export CROSS_COMPILE=< TOOLCHAIN PREFIX` i.e "arm-none-gnueabi-" (the last "-" is important) export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

A link that might help: http://en.wikipedia.org/wiki/Master_boot_record

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file should look something like this:

export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH} export CROSS_COMPILE=< TOOLCHAIN PREFIX` i.e "arm-none-gnueabi-" (the last "-" is important) export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

A link that might help: http://en.wikipedia.org/wiki/Master_boot_record

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file should look something like this:

export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH} export CROSS_COMPILE=< TOOLCHAIN PREFIX` i.e "arm-none-gnueabi-" (the last "-" is important) export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

deleted 51 characters in body

Source Link

edited Dec 10, 2014 at 15:56

tshepang

67.7k
94
226
297

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file you should look aboutsomething like this:
export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH}
export CROSS_COMPILE=< TOOLCHAIN PREFIX i.e "arm-none-gnueabi-" (the last "-" is important)
export ARCH=< ARCHITECTURE>

export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH} export CROSS_COMPILE=< TOOLCHAIN PREFIX` i.e "arm-none-gnueabi-" (the last "-" is important) export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

A

A link that might help:
MBR on Wikipediahttp://en.wikipedia.org/wiki/Master_boot_record

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file you should look about like this:
export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH}
export CROSS_COMPILE=< TOOLCHAIN PREFIX i.e "arm-none-gnueabi-" (the last "-" is important)
export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

A link that might help:
MBR on Wikipedia

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file should look something like this:

export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH} export CROSS_COMPILE=< TOOLCHAIN PREFIX` i.e "arm-none-gnueabi-" (the last "-" is important) export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

A link that might help: http://en.wikipedia.org/wiki/Master_boot_record

added 6 characters in body

Source Link

edited Dec 10, 2014 at 13:42

Anthon

81.4k
42
174
228

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file you should look about like this:
export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH}export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH}
export CROSS_COMPILE=< TOOLCHAIN PREFIXexport CROSS_COMPILE=< TOOLCHAIN PREFIX i.e "arm-none-gnueabi-" (the last "-" is important)
export ARCH=< ARCHITECTURE>export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

A link that might help:
MBR on Wikipedia

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file you should look about like this:
export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH}
export CROSS_COMPILE=< TOOLCHAIN PREFIX i.e "arm-none-gnueabi-" (the last "-" is important)
export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

A link that might help:
MBR on Wikipedia

I would suggest to do things in the "Linux way", which means for me, as less automatic configuration as possible. I would download the required toolchain from the distributor’s site, and set a .CC file in your project's working dir. Your CC file you should look about like this:
export PATH=< PATH-TO-TOOLCHAIN-BIN-FOLDER>:${PATH}
export CROSS_COMPILE=< TOOLCHAIN PREFIX i.e "arm-none-gnueabi-" (the last "-" is important)
export ARCH=< ARCHITECTURE>

After doing that, before running any compilation, issue "source .CC", and then compile as you do normally, i.e "gcc/g++/ld... ...". The compilation will automatically use the toolchain (you will see it in the output of the compilation, that the toolchain is being used)

A link that might help:
MBR on Wikipedia