Community
Participate
Working Groups
1. Create a Cross GCC project, set a wrong prefix 2. Open the project properties, C/C++ Build, Settings, Cross Settings 3. Change prefix to the correct value, apply 4. Go to Discovery options. The "Compiler invocation command" is still set to the old one Because of that, it's possible to have completely wrong includes and symbols.
Andrew, this is also the case with "normal" GCC toolchains. The compiler command can be changed in the build settings and the Scanner Discovery options are not updated. I don't expect users to change the compiler command really often for "normal" GCC but we could apply a similar solution for the Cross GCC prefix and the compiler command in all GCC toolchains. I suggest that when the values are different, an information line with a link is displayed below the field: (i) <-(info icon) The compiler command differs from the Compiler invocation command in <link>Discovery options</link> What do you think?
Yes, it is also valid case when scanner discovery command is different from that of compiler. A user can scan a file or run command remotely using ssh etc. Info message sounds as a valid option, other options could be a control such as a checkbox in scanner discovery options or popup question when changing compiler command.
Fixed by changing the Cross GCC toolchain to use a language setting provider. Done part of bug 392404. https://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=c644a857ba56c32171d4f5a738e19aea858f7faf
