[cdt-dev] "Other toolchain" projects attempt scanner config discovery

["Sergey Prigogin" <eclipse.sprigogin@xxxxxxxxx>]

Currently "other toolchain" projects are not truly "other". They try to do scanner config discovery with whatever gcc compiler that happens to be in the system path (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=226419). The discovered symbols then get hidden away, but include directories make it to the the project properties. This behavior doesn't make sense and should be fixed. "Other toolchain" projects are not gcc ones and should not use gcc by default. Scanner config discovery should still be supported, but only if the user explicitly provides the name of the compiler binary.

If you know of an existing application that would be broken by such a change, please speak up, or better yet, add a comment to https://bugs.eclipse.org/bugs/show_bug.cgi?id=226419.

-sergey