1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-04-29 19:45:01 +02:00

Merge remote branch 'cdt/master' into sd90

This commit is contained in:
Andrew Gvozdev 2011-09-10 19:45:38 -04:00
commit cc9627fdb2

View file

@ -2,96 +2,96 @@
<?eclipse version="3.2"?>
<plugin>
<!-- -->
<!-- Xl C ScannerConfigurationDiscoveryProfile definitions -->
<!-- -->
<!-- -->
<!-- Xl C ScannerConfigurationDiscoveryProfile definitions -->
<!-- -->
<!-- We have to extend the core of CDT's make so that we can define a new ScannerConfigurationDiscoveryProfile -->
<!-- A ScannerConfigurationDiscoveryProfile is used to discover information about the standard options used by the compiler, e.g. the standard include directories -->
<!-- We have to extend the core of CDT's make so that we can define a new ScannerConfigurationDiscoveryProfile -->
<!-- A ScannerConfigurationDiscoveryProfile is used to discover information about the standard options used by the compiler, e.g. the standard include directories -->
<!-- Xl C Managed Make Per Project Profile -->
<!-- The Profile gathers together information about the standard include directories and standard definitions used by the compiler -->
<extension
id="XLCManagedMakePerProjectProfile"
name="%profileName"
point="org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile">
<!-- Xl C Managed Make Per Project Profile -->
<!-- The Profile gathers together information about the standard include directories and standard definitions used by the compiler -->
<extension
id="XLCManagedMakePerProjectProfile"
name="%profileName"
point="org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile">
<!-- The ScannerInfoCollector manages the information generated by the Profile so that it can be easily accessed afterwards -->
<scannerInfoCollector
class="org.eclipse.cdt.make.xlc.core.scannerconfig.PerFileXLCScannerInfoCollector"
scope="project">
</scannerInfoCollector>
<!-- The ScannerInfoCollector manages the information generated by the Profile so that it can be easily accessed afterwards -->
<scannerInfoCollector
class="org.eclipse.cdt.make.xlc.core.scannerconfig.PerFileXLCScannerInfoCollector"
scope="project">
</scannerInfoCollector>
<!-- The ScannerInfoProvider search for the information needed by the profile and send it to the ScannerInfoCollector -->
<scannerInfoProvider providerId="specsFile">
<!-- Specifies the compiler command that returns the information about standard include directories and standard definitions -->
<!-- The compiler command used will be always a C compiler command -->
<!-- The output for C or C++ projects will be different as the ScannerInfoProvider substitute the ${specs_file} variable below with a dummy "c" file or "cpp" file -->
<run
arguments="-E -v ${plugin_state_location}/${specs_file}"
command="${XL_compilerRoot}/xlc"
class="org.eclipse.cdt.make.xlc.core.scannerconfig.XlCSpecsRunSIProvider">
</run>
<!-- Specifies the parser for the output generated by the compiler with the above command line -->
<scannerInfoConsoleParser
class="org.eclipse.cdt.make.xlc.core.scannerconfig.XlCSpecsConsoleParser">
</scannerInfoConsoleParser>
</scannerInfoProvider>
<!-- The ScannerInfoProvider search for the information needed by the profile and send it to the ScannerInfoCollector -->
<scannerInfoProvider providerId="specsFile">
<!-- Specifies the compiler command that returns the information about standard include directories and standard definitions -->
<!-- The compiler command used will be always a C compiler command -->
<!-- The output for C or C++ projects will be different as the ScannerInfoProvider substitute the ${specs_file} variable below with a dummy "c" file or "cpp" file -->
<run
arguments="-E -v ${plugin_state_location}/${specs_file}"
command="${XL_compilerRoot}/xlc"
class="org.eclipse.cdt.make.xlc.core.scannerconfig.XlCSpecsRunSIProvider">
</run>
<!-- Specifies the parser for the output generated by the compiler with the above command line -->
<scannerInfoConsoleParser
class="org.eclipse.cdt.make.xlc.core.scannerconfig.XlCSpecsConsoleParser">
</scannerInfoConsoleParser>
</scannerInfoProvider>
</extension>
<!-- -->
<!-- Xl C ScannerConfigurationDiscoveryProfile definitions -->
<!-- -->
</extension>
<!-- -->
<!-- Xl C ScannerConfigurationDiscoveryProfile definitions -->
<!-- -->
<!-- We have to extend the core of CDT's make so that we can define a new ScannerConfigurationDiscoveryProfile -->
<!-- A ScannerConfigurationDiscoveryProfile is used to discover information about the standard options used by the compiler, e.g. the standard include directories -->
<!-- We have to extend the core of CDT's make so that we can define a new ScannerConfigurationDiscoveryProfile -->
<!-- A ScannerConfigurationDiscoveryProfile is used to discover information about the standard options used by the compiler, e.g. the standard include directories -->
<!-- Xl C Managed Make Per Project Profile -->
<!-- The Profile gathers together information about the standard include directories and standard definitions used by the compiler -->
<extension
id="XLCManagedMakePerProjectProfileCPP"
name="%profileNameCPP"
point="org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile">
<!-- Xl C Managed Make Per Project Profile -->
<!-- The Profile gathers together information about the standard include directories and standard definitions used by the compiler -->
<extension
id="XLCManagedMakePerProjectProfileCPP"
name="%profileNameCPP"
point="org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile">
<!-- The ScannerInfoCollector manages the information generated by the Profile so that it can be easily accessed afterwards -->
<scannerInfoCollector
class="org.eclipse.cdt.make.xlc.core.scannerconfig.PerFileXLCScannerInfoCollector"
scope="project">
</scannerInfoCollector>
<!-- The ScannerInfoCollector manages the information generated by the Profile so that it can be easily accessed afterwards -->
<scannerInfoCollector
class="org.eclipse.cdt.make.xlc.core.scannerconfig.PerFileXLCScannerInfoCollector"
scope="project">
</scannerInfoCollector>
<!-- The ScannerInfoProvider search for the information needed by the profile and send it to the ScannerInfoCollector -->
<scannerInfoProvider providerId="specsFile">
<!-- Specifies the compiler command that returns the information about standard include directories and standard definitions -->
<!-- The compiler command used will be always a C compiler command -->
<!-- The output for C or C++ projects will be different as the ScannerInfoProvider substitute the ${specs_file} variable below with a dummy "c" file or "cpp" file -->
<run
arguments="-E -v ${plugin_state_location}/${specs_file}"
command="${XL_compilerRoot}/xlC"
class="org.eclipse.cdt.make.xlc.core.scannerconfig.XlCSpecsRunSIProvider">
</run>
<!-- Specifies the parser for the output generated by the compiler with the above command line -->
<scannerInfoConsoleParser
class="org.eclipse.cdt.make.xlc.core.scannerconfig.XlCSpecsConsoleParser">
</scannerInfoConsoleParser>
</scannerInfoProvider>
</extension>
<extension
point="org.eclipse.cdt.core.LanguageSettingsProvider">
<provider
class="org.eclipse.cdt.managedbuilder.xlc.core.XlcBuiltinSpecsDetector"
id="org.eclipse.cdt.managedbuilder.xlc.core.xlc.specs.detector"
name="CDT XLC Builtin Compiler Settings"
parameter="${COMMAND} -E -V -P -w ${INPUTS}">
<language-scope id="org.eclipse.cdt.core.gcc"/>
<language-scope id="org.eclipse.cdt.core.g++"/>
</provider>
<provider
class="org.eclipse.cdt.make.core.scannerconfig.GCCBuildCommandParser"
id="org.eclipse.cdt.managedbuilder.xlc.core.xlc.build.command.parser"
name="CDT XLC Build Output Parser"
parameter="xl[cC]">
</provider>
</extension>
<!-- The ScannerInfoProvider search for the information needed by the profile and send it to the ScannerInfoCollector -->
<scannerInfoProvider providerId="specsFile">
<!-- Specifies the compiler command that returns the information about standard include directories and standard definitions -->
<!-- The compiler command used will be always a C compiler command -->
<!-- The output for C or C++ projects will be different as the ScannerInfoProvider substitute the ${specs_file} variable below with a dummy "c" file or "cpp" file -->
<run
arguments="-E -v ${plugin_state_location}/${specs_file}"
command="${XL_compilerRoot}/xlC"
class="org.eclipse.cdt.make.xlc.core.scannerconfig.XlCSpecsRunSIProvider">
</run>
<!-- Specifies the parser for the output generated by the compiler with the above command line -->
<scannerInfoConsoleParser
class="org.eclipse.cdt.make.xlc.core.scannerconfig.XlCSpecsConsoleParser">
</scannerInfoConsoleParser>
</scannerInfoProvider>
</extension>
<extension
point="org.eclipse.cdt.core.LanguageSettingsProvider">
<provider
class="org.eclipse.cdt.managedbuilder.xlc.core.XlcBuiltinSpecsDetector"
id="org.eclipse.cdt.managedbuilder.xlc.core.xlc.specs.detector"
name="CDT XLC Builtin Compiler Settings"
parameter="${COMMAND} -E -V -P -w ${INPUTS}">
<language-scope id="org.eclipse.cdt.core.gcc"/>
<language-scope id="org.eclipse.cdt.core.g++"/>
</provider>
<provider
class="org.eclipse.cdt.make.core.scannerconfig.GCCBuildCommandParser"
id="org.eclipse.cdt.managedbuilder.xlc.core.xlc.build.command.parser"
name="CDT XLC Build Output Parser"
parameter="xl[cC]">
</provider>
</extension>
</plugin>