[cdt-dev] Include path discovery hardcoded to use "gcc"

[John Dallaway <jld@xxxxxxxxxxxxxxx>]

I'm looking at options for a fix for bug 117294:

  http://bugs.eclipse.org/bugs/show_bug.cgi?id=117294

Ideally, I would like to fix this by forcing the scanner to use the
user-specified compiler tool for the current managed build project (eg
"arm-elf-gcc") rather than using "gcc".

I have verified that I can hard code a new tool for scanning by
overriding the value of the fCompileCommand variable within
GCCSpecsRunSIProvider.initialize(), but there does not appear to be an
elegant way to access ManagedBuildInfo.getToolForSource() from here
without breaking the existing abstractions.

An alternative approach might be to generalize the "Discovery Options"
code and UI currently used by unmanaged make projects and use them also
for managed make projects. But the user would then have to specify the
compiler tool both in the build tools UI and in the discovery options UI.

Is there a reason why the tool used for scanning was kept distinct from
the tool used for compiling within CDT?

Any other thoughts on the best way to address this bug would be most
welcome.

John Dallaway