Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/Obsolete/ScannerDiscovery61/ExistingArch"
< CDT | Obsolete | ScannerDiscovery61
(New page: Document the existing architecture from it's main client, the parser, to the individual providers.) |
|||
| Line 1: | Line 1: | ||
Document the existing architecture from it's main client, the parser, to the individual providers. | Document the existing architecture from it's main client, the parser, to the individual providers. | ||
| + | |||
| + | === The Parser === | ||
| + | |||
| + | 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. | ||
Revision as of 12:05, 4 September 2009
Document the existing architecture from it's main client, the parser, to the individual providers.
The Parser
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.