mbed-cli does not find ARM compiler in linux (with ARM_PATH defined)

[teetak01]

Trying to compile with ARM compiler -- Getting this kind of failure:

Building project mbed-client-testapp (K64F, ARM)
ERROR: run_cmd: Command 'C:/Program Files/ARM/bin/armcc' can't be found
ERROR: run_cmd: Command 'C:/Program Files/ARM/bin/armcc' can't be found

I have specified as per README:

Product: ARM Compiler 5.06
Component: ARM Compiler 5.06 update 1 (build 61)
Tool: armcc [4d35ad]

teetak01@machine:~/dev/mbed-client-testapp (bootstrap)$ which armcc
/home/teetak01/ARM_Compiler_5.06u1/bin/armcc

teetak01@machine:~/dev/mbed-client-testapp (bootstrap)$ env | grep ARM_PATH
GCC_ARM_PATH=/usr/bin/arm-none-eabi-gcc
ARM_PATH=/home/teetak01/ARM_Compiler_5.06u1

Command-line code management tool for ARM mbed OS - http://www.mbed.com
version 0.7.3

[screamerbg]

Currently mbed CLI and the build tools do not take into account the GCC and ARM environment variables. Of course these could be extended.

[jupe]

this propably related to this one: ARMmbed/mbed-os#125 . but because latest mbed-os uses tools from mbedmicro/mbed correction probably belong to mbedmicro/mbed repository...

[jupe]

but still I think this is more like a bug than enhancement because its normal way to use env paths for this kind of cases.. hardcoded paths causes allmost always an problems...

[screamerbg]

@teetak01 have you completed the following step from the README https://github.com/ARMmbed/mbed-cli#toolchain-selection ?

[teetak01]

@screamerbg I did not initially do the first part, bacause I presumed that specifying an en enviromental variable would override any hard-coded definitions. It should be globally configurable parameters, instead of repository-specific place. Currently I have to edit a file manually for each repo to get the ARM_PATH working correctly.

[teetak01]

@screamerbg The current implementation also stays in infinite loop printing the ERROR.

[teetak01]

@screamerbg tested with mbed cli 0.7.13, both issues still remain. Not sure was either supposed to be fixed.

[screamerbg]

PR filed at ARMmbed/mbed-os#2005 that enables the functionality in mbed OS tools

[screamerbg]

When the above PR is accepted and the mbed OS is updated one can do

mbed config --global ARM_PATH "C:\Program Files\ARM"

Also per program config is supported for when specific version of ARMCC, GCC or IAR is need, e.g.

mbed config ARM_PATH "C:\Program Files\ARM"           # local/current program config

[jupe]

why it doesn't use existing environment variables:
ARMROOT=/usr/local/ARM_Compiler_5
GCC_ARM_PATH=...
PATH=...iar/
it's quite pointless to create new environment variables if there is already... also I think there is no need to mbed specific command to set these environment variables, instead users could use just normal way, like set -command..

[screamerbg]

It was discussed that toolchain related environment variables should be separate and should use the MBED_ prefix.
cc @bridadan @sg-

[bridadan]

@jupe mbed-cli isn't necessary to set these variables, it's just a contained way within the mbed command. You can still use set or export to set the MBED_* variables and the tools will pick that up.