Re: [cdt-dev] Managed Builder - specify the location of tools?

["Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>]

I generally create a configuration environment provider for the toolchain and set the PATH variable there. MinGW is done that way.

 

Doug.

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Steve Goodrich
Sent: Wednesday, September 14, 2011 5:44 PM
To: 'CDT General developers list.'
Subject: [cdt-dev] Managed Builder - specify the location of tools?

 

I’m working with the extension point org.eclipse.cdt.managedbuilder.core.buildDefinitions and adding some toolchain (and tool) definitions.  I have multiple toolchains and want to be able to specify which “gcc” or “make” is to be used for a given configuration/toolchain.  I tried this:

      ${eclipse_home}/../tools/compiler1/bin/gcc.exe

 

It shows up in the console window like this:

            C:\MyFolder\win32\eclipse/../tools/xgcc/bin/i386-elf-gcc.exe

Unfortunately, the shell ends up trying to execute this:

            C:MyFolderwin32eclipse/../tools/xgcc/bin/i386-elf-gcc.exe

 

My questions:

1.     Is this the right way to specify the location of a tool/toolchain (by including the path in the command field)?

2.     What is the preferred way of dealing with the \ to / (Windows-to-Linux path) conversion?

 

Thanks!

            -- Steve G.