Allows plug-ins to contribute to detection of compiler include paths and preprocessor defines from a command-line text.
<p>This extension point teaches the <i>CompileCommandsParser</i> to analyze compiler-specific command-lines incl. options for a specific compiler. The detected include paths, preprocessor defines and preprocessor un-defines from the compiler command-line get passed to the CDT indexer.</p>
<p>Third party compiler vendors may use this extension point to add their compiler (or other tool) for improved syntax highlighting in the CDT's C/C++ editors.
Specifies the details for detection of a specific compiler by its executable name and how the include paths, preprocessor defines and preprocessor un-defines are processed.
The fully qualified name of a class that implements <code>org.eclipse.cdt.cmake.is.participant.IToolDetectionParticipant</code>, The implementation must provide a public no-argument constructor.<br/>
You may want to consider sub-classing <code>org.eclipse.cdt.cmake.is.participant.DefaultToolDetectionParticipant</code> for convenience instead of directly implementing the interface.
The order in which the participant takes place in the tool detection chain, specified as an positive integer value. Values below 10000 are reserved for internal purposes and will not be honored.
The easiest way to implement a tool detection participant would be to sub-class <code>org.eclipse.cdt.cmake.is.participant.DefaultToolDetectionParticipant</code>.
To configure your class, pass an instance of <code>org.eclipse.cdt.cmake.is.participant.DefaultToolCommandlineParser</code> in its super-constructor.<br/>
Some predifined parsers for tool arguments can be found in the classes <code>Arglets</code> and <code>ResponseFileArglets</code>.