#55 Can't find tools when using Sourcery ARM GNU/Linux toolchain

Version 0.5.4
closed-fixed
None
5
2013-10-18
2013-07-01
Trevor Robinson
No

Plugin: 0.5.4.201202210114
Eclipse: 4.3.0.v20130605-2000
OS: Windows 7 Pro 64-bit SP1
Toolchain: Sourcery CodeBench Lite 2013.05-24

I'm trying to use the Sourcery ARM GNU/Linux toolchain (https://sourcery.mentor.com/GNUToolchain/release2450) rather than the bare-metal ARM EABI toolchain (https://sourcery.mentor.com/GNUToolchain/release2449). It has executables prefixed with "arm-none-linux-gnueabi-" rather than "arm-none-eabi-". Even after updating the commands in Project > C/C++ Build > Settings > Tool Settings (all configurations), I still get the error 'Program "arm-none-eabi-g++" not found in PATH'. If I install the EABI toolchain and put it in my PATH, discovery succeeds. Is there a way to use the Linux toolchain for discovery?

Discussion

  • Is there a way to use the Linux toolchain for discovery?

    yes, update the discovery commands too.

    Liviu

     
  • I tried changing Preferences > C/C++ / Build / Settings / Discovery / CDT GCC Build Output Parser / Compiler command pattern to "arm-none-linux-gnueabi-(gcc|g++)". I still got the same error about "arm-none-eabi-g++" not found in PATH. Is this the right place to update?

     
  • nope, in my configuration it appears as C/C++ Build -> Discovery Options -> Compiler invocation command

     
  • Maybe this is an Eclipse version issue? I'm using 4.3 Kepler.

     
  • oops! they changed it again? I'm still on Juno...

     
  • Heh, I was on Juno, but upgraded from a fresh zip file because the "install new software" feature kept complaining about inaccessible dependency repositories.

    However, I'd like to find a more user-friendly way to get this working so I can point others to it. Even if discovery were working, there's still all the tool commands that would have to be changed in each project. I guess I'll try creating a separate toolchain definition (based on Sourcery) that looks for things in the right places.

     
  • On Kepler the command used to get compiler specs is configurable in

    Project Properties -> C/C++ General -> Preprocessor Include Path -> Providers -> CDT GCC Built-in Compiler Settings

    just change $(COMMAND) to gcc/g++

    Liviu

     
    • status: open --> closed-fixed
    • assigned_to: Liviu Ionescu (ilg)
     
  • Sourcery Lite Linux (arm-none-linux-gnueabi-) supported from 0.5.5.201309281715.