Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
CDT/Obsolete/ScannerDiscovery61/ExistingArch
< CDT | Obsolete | ScannerDiscovery61
Document the existing architecture from it's main client, the parser, to the individual providers.
Doug's Discoveries
- At the core of the Scanner Discovery profile is the IScannerInfo interface. It has two methods, getIncludePaths, and getDefinedSymbols. It is used by a number of clients to determine the compiler options to help with parsing.
- There is also an IExtendedScannerInfo that adds is additional methods for other command line options (mainly from gcc) that can affect the compile, e.g. macro files, include files, and local include paths.
- The IScannerInfo type hierarchy is very interesting. e.g. there are two ScannerInfo classes. Be careful which one you're looking at. Which ones get actually used?