mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-07-12 19:45:22 +02:00
b8bd15844b
This change adds the ALL_FLAGS that does not limit tool options to those declared as IOption::isForScannerDiscovery when launching the compiler to discover compiler built-ins. This is needed as many other flags, either entered manually in "Other flags" or some of the existing flags with checkboxes such as "-ansi", "-fPIC", and "-fstack-protector-all" which all affect scanner discovery as they can all change what macros are built-in to the compiler. The current solution has as a drawback that some settings, like -I and -D then appear twice. For example in the "Includes" node in the "Project Explorer" My only reservation about this change is if there is an option that can be specified successfully at build time, but when used at scanner discovery time causes the compiler to fail, or return incorrect results. Therefore I have added a new field, excludeFromScannerDiscovery to tool options (buildDefinitions extension point) that allows tool integrators to always exclude a command line option from ALL_FLAGS. I have also added a new "Other flags (excluded from discovery)" to the "Miscellaneous" tab to allow compiler options to be entered by the user. |
||
|---|---|---|
| .. | ||
| .settings | ||
| cheatsheets | ||
| concepts | ||
| getting_started | ||
| images | ||
| intro | ||
| META-INF | ||
| reference | ||
| setting_up_eclipse_cdt | ||
| tasks | ||
| .gitignore | ||
| .project | ||
| about.html | ||
| book.css | ||
| build.properties | ||
| contexts_CDT.xml | ||
| contexts_CDT_DEBUGGER.xml | ||
| contexts_CDT_DEBUGGER_DSFGDB.xml | ||
| contexts_CDT_DEBUGGER_MI.xml | ||
| contexts_CDT_LAUNCH.xml | ||
| contexts_CDT_make.xml | ||
| customBuildCallbacks.xml | ||
| help.css | ||
| notices.html | ||
| plugin.properties | ||
| plugin.xml | ||
| pom.xml | ||
| toc.xml | ||
| topics_Concepts.xml | ||
| topics_Getting_Started.xml | ||
| topics_Reference.xml | ||
| topics_Tasks.xml | ||