Community
Participate
Working Groups
If a user has Cygwin in his PATH it will always be executed in org.eclipse.cdt.core.CommandLauncher.execute(IPath commandPath, String[] args, String[] env, IPath workingDirectory, IProgressMonitor monitor) Even if the application itself was not found, this effectively mean as soon as a user has Cygwin in path, there's no way to run other compilers. This also happens even if Cygwin.cygwinToWindowsPath(location.toString(), envPathValue) was not called, somewhere in native code in the Starter.exe application.
This is the way how $PATH works in general, isn't it? There are 2 ways to "run other compilers" - one is to use full (or relative) path to the program and another is to provide $PATH pointing to the program path. What is your expectation how it should work? Could you share more details about your use case?
I agree that this is the general PATH behaviour, however the code in CommandLauncher already accounts for that and builds a cygwin path when it finds cygwin. In my case, I have a external compiler path pointing to my own make.exe (i.e. C:\[application]\[buildpath]\make.exe and cygwin still gets called to execute my own exe, which is caused by Starter.exe always calling cygwin regardless of what I specified as compiler.
