GNU Arm Embedded Toolchain

Tools installation path

Asked by kjell eirik andersen

Hi !

My company maintains a large number og projects for our EFM32 Cortex-M parts.
For each "GNU ARM Embedded" release a zillion makefiles must be updated with a new path i.e.
c:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2013q1\bin

Why not keep the installation path fixed/generic ?
Like for example as in :
c:\Program Files (x86)\CodeSourcery\Sourcery_CodeBench_Lite_for_ARM_EABI\bin

Best Regards,
Kjell Eirik Andersen

Question information

Language:
English Edit question
Status:
Answered
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Terry Guo (terry.guo) said : 		#1

I think some people will install more than one tools like 4.6 2012Q4, 4.7 2013Q1. So different installation pathes can distinguish them. For your case, I think you can use environment path to make it easier rather than the hard-coded tool chain path.

For Linux platform, I would just specify CC=arm-none-eabi-gcc in my Makefile. Then run:
export PATH=/NEW-TOOLCHAIN-PATH/bin:$PATH
right before call my Makefile.

You can also put tool chain path into a variable.

Can you help with this problem?

Provide an answer of your own, or ask kjell eirik andersen for more information if necessary.

To post a message you must log in.