diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CBuildConsole.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CBuildConsole.html deleted file mode 100644 index 60100b672b2..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CBuildConsole.html +++ /dev/null @@ -1,42 +0,0 @@ - - - -C/C++ Build Console - - - - -

C/C++ Build Console

-

-
Identifier:
org.eclipse.cdt.core.CBuildConsole

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (CBuildConsole+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT CBuildConsole EMPTY>

-

<!ATTLIST CBuildConsole

-

id    CDATA #IMPLIED

class CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CConfigurationDataProvider.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CConfigurationDataProvider.html deleted file mode 100644 index 248d8594b01..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CConfigurationDataProvider.html +++ /dev/null @@ -1,48 +0,0 @@ - - - -CConfigurationData provider - - - - -

CConfigurationData provider

-

-
Identifier:
org.eclipse.cdt.core.CConfigurationDataProvider

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (provider)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #REQUIRED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT provider EMPTY>

-

<!ATTLIST provider

-

natures            CDATA #IMPLIED

class              CDATA #REQUIRED

conflictingNatures CDATA #IMPLIED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CIndex.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CIndex.html deleted file mode 100644 index 7261240097f..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CIndex.html +++ /dev/null @@ -1,143 +0,0 @@ - - - -CIndex - - - - -

CIndex

-

-
Identifier:
org.eclipse.cdt.core.CIndex

-
Since:
4.0 -

- -
Description:
This extension point groups extensions to the index functionality in CDT

-
Configuration Markup:
-

-

<!ELEMENT extension (ExportProjectProvider | ReadOnlyPDOMProvider)+>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT ExportProjectProvider EMPTY>

-

<!ATTLIST ExportProjectProvider

-

class CDATA #REQUIRED>

-

-
-

ExportProjectProvider

-

-This subelement of CIndex allows contribution of alternate IExportProjectProvider implementations. These can then be referenced by fully qualified class name in the command line tool (see option -pprovider). -

-Invoking the application as a headless application - -This example ant file shows how to invoke the tool headlessly, the same approach would work from a shell or batch file. - -


-<project name="Generate PDOM" default="generate">
- <target name="generate">
-  <!-- This script shows how to invoke the default project provider (ExternalExportProjectProvider) -->
-  <property name="pprovider" value="org.eclipse.cdt.core.index.export.ExternalExportProjectProvider"/>
-  <property name="target" value="C:\ExportedPDOMs\acmeSDK_2_5.pdom"/> <!-- Where the output pdom is to go -->
-  <property name="source" value="E:\AcmeSDK\v2.5\inc"/> <!-- e.g. the directory to source content from -->
-  <property name="id" value="com.acme.mysdk.v2.5"/> <!-- the id to store in the generate pdom -->
-  
-  <property name="eclipse.home" value="C:\eclipse"/> <!-- e.g. The eclipse installation to use. This installation must contain CDT 4.0+ plugins -->
-  
-  <java classname="org.eclipse.equinox.launcher.Main">
-   <classpath>
-    <fileset dir="${eclipse.home}/plugins">
-     <include name="*equinox.launcher*.jar"/>
-    </fileset>
-   </classpath>
-   <arg value="-nosplash"/>
-   <arg value="-exitdata"/>
-   <arg value="-application"/><arg value="org.eclipse.cdt.core.GeneratePDOM"/>
-   <arg value="-pprovider"/><arg value="${pprovider}"/>
-   <arg value="-source"/><arg value="${source}"/>
-   <arg value="-target"/><arg value="${target}"/>
-   <arg value="-id"/><arg value="${id}"/>
-  </java>
- </target>
-</project>
-
-

-Invoking the tool via an Eclipse Launch Configuration -

-Specify "org.eclipse.cdt.core.GeneratePDOM" as the application to launch -

-In the Argument tabs provide (for example) - -target C:\ExportedPDOMs\acmeSDK_2_5.pdom -source E:\AcmeSDK\v2.5\inc -include E:\this.h -id com.acme.mysdk.v2.5 -

-
- -

<!ELEMENT ReadOnlyPDOMProvider EMPTY>

-

<!ATTLIST ReadOnlyPDOMProvider

-

class CDATA #REQUIRED>

-

-
-

ReadOnlyPDOMProvider

-

-This subelement of CIndex allows ISVs to contribute read-only prebuilt PDOM files to the CDT Index. The only information needed is the fully qualified class name of an implementatin of org.eclipse.cdt.core.index.IOfflinePDOMProvider. This implementation will be consulted during the eclipse session for the appropriate read-only content to make add to the logical index. The logical index is accessible via the org.eclipse.core.index.IIndex API. - - An example of contributing a prebuilt read-only pdom: -


-<CIndex>
-   <ReadOnlyPDOMProvider class="com.acme.ide.index.AcmeSDKProvider"/>
-</CIndex>
-
- -and the corresponding implementation - -

-package com.acme.ide.index.sdk;
-
-import org.eclipse.core.index.provider.IReadOnlyPDOMProvider;
-import org.eclipse.core.index.provider.IPDOMDescriptor;
-import org.eclipse.core.index.IIndexLocationConverter;
-import org.eclipse.core.index.URIRelativeLocationConverter;
-
-public class AcmeSDKProvider implements IReadOnlyPDOMProvider {
-    public boolean providesFor(ICProject project) {
-        // e.g. decide by looking for acme project nature
-        return AcmeNature.isAcmeProject(project);
-    }
-
-    public IPDOMDescriptor[] getDescriptors(ICConfigurationDescription config) {
-        final IPath sdkBase = AcmeSDKAPI.getSDKBase(config);
-        return new IPDOMDescriptor[] { new IPDOMDescriptor() {
-            public IIndexLocationConverter getIndexLocationConverter() {
-                return new URIRelativeLocationConverter(URIUtil.toURI(sdkBase));
-            }
-            public IPath getLocation() {
-                IPath path = sdkBase.append(AcmeSDKAPI.getPrebuiltPDOMFilename(config));
-                return path;
-            }
-        }};
-    }
-}
-
-
- -
Examples:
See subelement documentation -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-Copyright (c) 2007 Symbian Software Systems and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CIndexer.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CIndexer.html deleted file mode 100644 index cd5a7903f4c..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CIndexer.html +++ /dev/null @@ -1,41 +0,0 @@ - - - -CDT Indexer - - - - -

CDT Indexer

-

-
Identifier:
org.eclipse.cdt.core.CDTIndexer

-
Since:
CDT 3.0 -

- -
Description:
This extension point is used to contribute a new Indexer to the CDT. This indexer can choose to receive event notification from the index manager.

-
Configuration Markup:
-

-

<!ELEMENT extension (run)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #REQUIRED

name  CDATA #REQUIRED>

-

- -

<!ELEMENT run EMPTY>

-

<!ATTLIST run

-

class CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CProject.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CProject.html deleted file mode 100644 index ae38f95cf6b..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CProject.html +++ /dev/null @@ -1,40 +0,0 @@ - - - -C/C++ Project Description - - - - -

C/C++ Project Description

-

-
Identifier:
org.eclipse.cdt.core.CProject

-
Description:
[Enter description of this extension point]

-
Configuration Markup:
-

-

<!ELEMENT extension (cproject)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #REQUIRED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT cproject EMPTY>

-

<!ATTLIST cproject

-

class    CDATA #REQUIRED

natureID CDATA #IMPLIED

platform CDATA #IMPLIED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CodeFormatter.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CodeFormatter.html deleted file mode 100644 index 52f445c53e7..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_CodeFormatter.html +++ /dev/null @@ -1,43 +0,0 @@ - - - -Code Formatter - - - - -

Code Formatter

-

-
Identifier:
org.eclipse.cdt.core.CodeFormatter

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (codeFormatter+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT codeFormatter EMPTY>

-

<!ATTLIST codeFormatter

-

id    CDATA #REQUIRED

name  CDATA #REQUIRED

class CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_PathEntryContainerInitializer.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_PathEntryContainerInitializer.html deleted file mode 100644 index 08d6ed5dde7..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_PathEntryContainerInitializer.html +++ /dev/null @@ -1,42 +0,0 @@ - - - -Path Entry Container Initializers - - - - -

Path Entry Container Initializers

-

-
Identifier:
org.eclipse.cdt.core.pathEntryContainerInitializer

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (pathEntryContainerInitializer)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT pathEntryContainerInitializer EMPTY>

-

<!ATTLIST pathEntryContainerInitializer

-

id    CDATA #REQUIRED

class CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_ProcessList.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_ProcessList.html deleted file mode 100644 index 3a7d34850ed..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_ProcessList.html +++ /dev/null @@ -1,39 +0,0 @@ - - - -Process List Query Exentsion - - - - -

Process List Query Exentsion

-

-
Identifier:
org.eclipse.cdt.core.ProcessList

-
Description:
[Enter description of this extension point]

-
Configuration Markup:
-

-

<!ELEMENT extension (processList)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT processList EMPTY>

-

<!ATTLIST processList

-

class    CDATA #REQUIRED

platform CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_externalSettingsProvider.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_externalSettingsProvider.html deleted file mode 100644 index 34efa67e81e..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_externalSettingsProvider.html +++ /dev/null @@ -1,43 +0,0 @@ - - - -External Settings provider - - - - -

External Settings provider

-

-
Identifier:
org.eclipse.cdt.core.externalSettingsProvider

-
Since:
4.0 -

- -
Description:
The external settings provider would be used to specify provider of include/macro/libraryan settings to be used/applied for the build configuration associated with this provider. -Any number of setting providers can be associated with the build configurations. -This functionality might be used, e.g. by the External SDKs to allow automatic andjustment of the project settings for the projects using thes SDKs, e.g. adding include paths, symbols, etc.

-
Configuration Markup:
-

-

<!ELEMENT extension (provider)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #REQUIRED

name  CDATA #REQUIRED>

-

- -

<!ELEMENT provider EMPTY>

-

<!ATTLIST provider

-

class CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_language.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_language.html deleted file mode 100644 index 87f9c7ed650..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_language.html +++ /dev/null @@ -1,78 +0,0 @@ - - - -CDT Language - - - - -

CDT Language

-

-
Identifier:
org.eclipse.cdt.core.language

-
Since:
CDT 3.1 -

- -
Description:
This extension point is used to declare a language or language variant. Languages define how the C model of a file is created (e.g. to populate the outline view). It also provides hooks to override the low level parsing of translation units into an abstract syntax tree. Practically this is limited to C/C++ language variants only. Completely different languages cannot be modelled reasonably using this extension point.

-
Configuration Markup:
-

-

<!ELEMENT extension ((language | pdomLinkageFactory))+>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT language (contentType)*>

-

<!ATTLIST language

-

id    CDATA #REQUIRED

name  CDATA #REQUIRED

class CDATA #REQUIRED>

-

- -

<!ELEMENT contentType EMPTY>

-

<!ATTLIST contentType

-

id CDATA #IMPLIED>

-

- -

<!ELEMENT pdomLinkageFactory EMPTY>

-

<!ATTLIST pdomLinkageFactory

-

id    CDATA #REQUIRED

class CDATA #REQUIRED>

-

- -
Examples: 

-<language
-      class="org.eclipse.cdt.core.dom.ast.gnu.c.GCCLanguage"
-      id="gcc"
-      name="GNU C">
-   <contentType id="org.eclipse.cdt.core.cSource"/>
-   <contentType id="org.eclipse.cdt.core.cHeader"/>
-</language>
-
-

- -
Supplied Implementation:
CDT comes with following built-in languages: -org.eclipse.cdt.core.language.gcc (GNU C) and -org.eclipse.cdt.core.language.g++ (GNU C++). -

The respective language implementations are -org.eclipse.cdt.core.dom.ast.gnu.c.GCCLanguage and -org.eclipse.cdt.core.dom.ast.gnu.cpp.GPPLanguage -

-

- -
-

-Copyright (c) 2005, 2007 QNX Software Systems and others. -All rights reserved. This program and the accompanying materials are made -available under the terms of the Eclipse Public License v1.0 which -accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_projectConverter.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_projectConverter.html deleted file mode 100644 index c3eff9dc7f6..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_projectConverter.html +++ /dev/null @@ -1,43 +0,0 @@ - - - -project converter - - - - -

project converter

-

-
Identifier:
org.eclipse.cdt.core.projectConverter

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (converter)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT converter EMPTY>

-

<!ATTLIST converter

-

owners  CDATA #IMPLIED

natures CDATA #IMPLIED

class   CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templateAssociations.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templateAssociations.html deleted file mode 100644 index 0e730c4a910..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templateAssociations.html +++ /dev/null @@ -1,73 +0,0 @@ - - - -Template Associations - - - - -

Template Associations

-

-
Identifier:
org.eclipse.cdt.core.templateAssociations

-
Since:
This extension point was added in CDT 4.0 -

- -
Description:
This extension-point allows developers to specify toolchains that should be enabled for selection for use with a pre-existing template. This solves the problem over how ISV's can have templates defined and shipped with CDT support their own toolchains, without having to modify CDT itself.

-
Configuration Markup:
-

-

<!ELEMENT extension (template+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

-

-Each extension consists of a sequence of template elements, each of which define child elements for the new toolchains that should be enabled for selection during new project creation.

-
- -

<!ELEMENT toolChain EMPTY>

-

<!ATTLIST toolChain

-

id CDATA #REQUIRED>

-

-

-This element is used to reference an existing toolchain by its unique identifier.

-
- -

<!ELEMENT template (toolChain*)>

-

<!ATTLIST template

-

id CDATA #REQUIRED>

-

-

-This element references an existing template contribution's unique identifier in order that toolchains contributed separately to the template can be made selectable on project creation.

-
- -
Examples:
If you developed toolchain's with ids "com.foobar.toolchain1.base" and "com.foobar.toolchain2.base", which you wanted enabled for the empty project type built into the cdt core, you could use the following to achieve this: - -

-<extension point="org.eclipse.cdt.core.templateAssociations">
-   <template id="org.eclipse.cdt.build.core.templates.EmptyProject">
-      <toolChain id="com.foobar.toolchain1.base"/>
-      <toolChain id="com.foobar.toolchain2.base"/>
-   </template>
-</extension>
-
-

- -
-

-Copyright (c) 2007 Symbian Software Limited and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -Contributors: -Symbian - Initial API and implementation - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templateProcessTypes.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templateProcessTypes.html deleted file mode 100644 index aab51ff9bf6..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templateProcessTypes.html +++ /dev/null @@ -1,173 +0,0 @@ - - - -Processes Extension point - - - - -

Processes Extension point

-

-
Identifier:
org.eclipse.cdt.core.templateProcessTypes

-
Since:
This extension point was added in CDT 4.0 -

- -
Description:
This extension point is to be extended to define new processes to be used in template descriptors by template writers.

-
Configuration Markup:
-

-

<!ELEMENT extension (processType+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED>

-

-

-One or more elements of processType should be added as children to this element.

-
- -

<!ELEMENT processType ((simple | simpleArray | complex | complexArray)*)>

-

<!ATTLIST processType

-

name          CDATA #REQUIRED

processRunner CDATA #REQUIRED>

-

-

-This element defines a single process. A process is analogous to a procedure with a set of parameters. In similar terms, one can say that this element defines the prototype of this process procedure. One needs to specify all the parameters expected by this process. In the eventual template xml, one needs to specify arguments for the process matching the types and order of these parameters.

-
- -

<!ELEMENT simple EMPTY>

-

<!ATTLIST simple

-

name     CDATA #REQUIRED

external (true | false)

nullable (true | false) >

-

-

-A simple string parameter. In the eventual template xml, one needs to specify the same name as the value of the name attribute of a simple argument alongwith the corresponding value attribute.

-
- -

<!ELEMENT simpleArray EMPTY>

-

<!ATTLIST simpleArray

-

name CDATA #REQUIRED>

-

-

-A simple string array parameter. In the eventual template xml, one needs to specify the same name as the value of the name attribute of a simple-array argument alongwith the corresponding element children, one child per array element with the corresponding value attribute.

-
- -

<!ELEMENT complex ((simple | simpleArray | complex | complexArray))+>

-

<!ATTLIST complex

-

name CDATA #REQUIRED>

-

-

-A complex parameter that groups together any number of simple, simpleArray, complex, complexArray parameters. This is equivalent of an object parameter. In the eventual template xml, one needs to specify the same name as the value of the name attribute of a simple argument alongwith the corresponding children, each child matching the type of the corresponding child of this element.

-
- -

<!ELEMENT complexArray (baseType)>

-

<!ATTLIST complexArray

-

name CDATA #REQUIRED>

-

-

-A complex array parameter. Each element of this parameter is of the same base complex type as specified by the baseType child of this element. In the eventual template xml, one needs to specify the same name as the value of the name attribute of a complex-array argument alongwith the corresponding element children, one child per array element with the corresponding complex type arguments (based on baseType definition).

-
- -

<!ELEMENT baseType ((simple | simpleArray | complex | complexArray))+>

-

-

-This is not a direct parameter of a process. This simply acts as a complex grouping of parameters to be used as the base type of complexArray parameters.

-

-
Examples:
The following is an example of the extension point usage: -

-


-   <extension
-         id="processExample"
-         name="Process Example"
-         point="org.eclipse.cdt.core.templateengine.processTypes">
-
-        <processType
-            name="NewManagedProject"
-            processRunner="org.eclipse.cdt.core.templateengine.process.processes.NewManagedProject">
-         <simple name="name"/>
-         <simple
-               external="true"
-               name="projectType"/>
-         <simple
-               external="true"
-               name="location"
-               nullable="true"/>
-         <simple name="targetType"/>
-        </processType>
-
-        <processType
-            name="SetMBSBooleanOptionValue"
-            processRunner="org.eclipse.cdt.core.templateengine.process.processes.SetMBSBooleanOptionValue">
-         <simple name="projectName"/>
-         <complexArray name="resourcePaths">
-            <baseType>
-               <simple name="id"/>
-               <simple name="value"/>
-               <simple name="path"/>
-            </baseType>
-         </complexArray>
-        </processType>
-
-        <processType
-            name="AddFile"
-            processRunner="org.eclipse.cdt.core.templateengine.process.processes.AddFile">
-         <simple name="projectName"/>
-         <complex name="file">
-            <simple name="source"/>
-            <simple name="target"/>
-            <simple name="replaceable"/>
-         </complex>
-        </processType>
-
-        <processType
-            name="AppendToMBSStringListOptionValues"
-            processRunner="org.eclipse.cdt.core.templateengine.process.processes.AppendToMBSStringListOptionValues">
-         <simple name="projectName"/>
-         <complexArray name="resourcePaths">
-            <baseType>
-               <simple name="id"/>
-               <simpleArray name="values"/>
-               <simple name="path"/>
-            </baseType>
-         </complexArray>
-        </processType>
-
-    </extension>
-
- -For more details on how to define your own templates, please check examples provided under -org.eclipse.cdt.gnu.templates -

- -
Supplied Implementation:
An implementation of this extension point is supplied in org.eclipse.cdt.core.templateengine -

- -
-

-Copyright (c) 2007 Symbian Software Limited and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -Contributors: -Bala Torati (Symbian) - Initial API and implementation - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templates.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templates.html deleted file mode 100644 index ae02c7c66f2..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_core_templates.html +++ /dev/null @@ -1,93 +0,0 @@ - - - -Template Extension point - - - - -

Template Extension point

-

-
Identifier:
org.eclipse.cdt.core.templates

-
Since:
This extension point was added in CDT 4.0 -

- -
Description:
This templates extension point facilitates the users to contribute their Template XMLs to the Template Engine plug-in.

-
Configuration Markup:
-

-

<!ELEMENT extension (template+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

-

-Extension point added to Template Engine plugin. Any plugin, which intends to contribute XML templates to the Template Engine must extend this extension point, and add the template element.

-
- -

<!ELEMENT template (toolChain*)>

-

<!ATTLIST template

-

id                                  CDATA #REQUIRED

location                            CDATA #REQUIRED

projectType                         CDATA #REQUIRED

isCategory                          (true | false)

filterPattern                       CDATA #IMPLIED

pagesAfterTemplateSelectionProvider CDATA #IMPLIED>

-

-

-By adding the templates extension point the users can contribute their Template XMLs to the Template Engine plugin.

-
- -

<!ELEMENT toolChain EMPTY>

-

<!ATTLIST toolChain

-

id CDATA #REQUIRED>

-

-

-This element is used to reference an existing toolchain by its unique identifier.

-
- -
Examples:
The following is an example of the extension point usage: -

-


-   <extension point="org.eclipse.cdt.core.templates">
-      <template
-         id="org.foobar.templates.MyExampleTemplate"
-         location="templates/MyExampleTemplate/template.xml"
-         projectType="org.eclipse.cdt.build.core.buildArtefactType.exe"
-         filterPattern=".*">
-      </template>
-   </extension>
-
- -For more details on how to define your own templates, please check examples provided under org.eclipse.cdt.ui.templateengine -

- -
Supplied Implementation:
An implementation of this extension point is supplied in org.eclipse.cdt.templateengine -

- -
-

-Copyright (c) 2007 Symbian Software Limited and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -Contributors: -Symbian - Initial API and implementation - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_BreakpointActionType.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_BreakpointActionType.html deleted file mode 100644 index 2f97cdba9e3..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_BreakpointActionType.html +++ /dev/null @@ -1,49 +0,0 @@ - - - -BreakpointActionType - - - - -

BreakpointActionType

-

-
Identifier:
org.eclipse.cdt.debug.core.BreakpointActionType

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
Extension to provide additional actions to execute when a breakpoint is hit.

-
Configuration Markup:
-

-

<!ELEMENT extension (actionType)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED>

-

- -

<!ELEMENT actionType EMPTY>

-

<!ATTLIST actionType

-

id    CDATA #IMPLIED

name  CDATA #IMPLIED

class CDATA #IMPLIED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-Copyright (c) 2007 Nokia and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_BreakpointExtension.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_BreakpointExtension.html deleted file mode 100644 index 2b677768dee..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_BreakpointExtension.html +++ /dev/null @@ -1,63 +0,0 @@ - - - -BreakpointExtension - - - - -

BreakpointExtension

-

-
Identifier:
org.eclipse.cdt.debug.core.BreakpointExtension

-
Description:
This extension point defines a mechanism for defining a debug model specific extension to C breakpoints.

-
Configuration Markup:
-

-

<!ELEMENT extension (breakpointExtension*)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT breakpointExtension EMPTY>

-

<!ATTLIST breakpointExtension

-

id           CDATA #REQUIRED

markerType   CDATA #REQUIRED

class        CDATA #REQUIRED

debugModelId CDATA #REQUIRED>

-

- -
Examples:
The following is an example of a breakpoint extension extension point. - -

-


- <extension point="org.eclipse.cdt.debug.BreakpointExtension">
-  <breakpointExtension
-   id="com.example.ExampleBreakpointExtension"
-   markerType="com.example.ExampleBreakpointMarker"
-   debugModeId="com.example.debug"
-   class="com.example.BreakpointExtensionImpl">
-  </breakpointExtension>
- </extension>
-
-

- -In the example above, the specified type of breakpoint extension is implemented by the class "com.example.BreakpointExtensionImpl". -This extension is going to apply to breakpoints with markers extending "com.example.ExampleBreakpointMarker", and to debug model with ID of "com.example.debug". -

- -
-

-Copyright (c) 2007 Wind River Systems and others.
-All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_CDebugger.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_CDebugger.html deleted file mode 100644 index 642e00400c1..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_debug_core_CDebugger.html +++ /dev/null @@ -1,60 +0,0 @@ - - - -CDebugger - - - - -

CDebugger

-

-
Identifier:
org.eclipse.cdt.debug.core.CDebugger

-
Description:
[Enter description of this extension point]

-
Configuration Markup:
-

-

<!ELEMENT extension (debugger+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT debugger (buildIdPattern*)>

-

<!ATTLIST debugger

-

name           CDATA #REQUIRED

modes          CDATA #IMPLIED

class          CDATA #REQUIRED

id             CDATA #REQUIRED

platform       CDATA #IMPLIED

cpu            CDATA #IMPLIED

coreFileFilter CDATA #IMPLIED>

-

- -

<!ELEMENT buildIdPattern EMPTY>

-

<!ATTLIST buildIdPattern

-

pattern CDATA #IMPLIED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-Copyright (c) 2004, 2005 QNX Software Systems and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_core_MakeTargetBuilder.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_core_MakeTargetBuilder.html deleted file mode 100644 index bbe22c8d2a0..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_core_MakeTargetBuilder.html +++ /dev/null @@ -1,42 +0,0 @@ - - - -Make Target Builder - - - - -

Make Target Builder

-

-
Identifier:
org.eclipse.cdt.make.core.MakeTargetBuilder

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
This extension point is used to identify builders that support IMakeBuidlerInfo an arguments.

-
Configuration Markup:
-

-

<!ELEMENT extension (builder)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT builder EMPTY>

-

<!ATTLIST builder

-

builderID CDATA #REQUIRED

id        CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_core_ScannerConfigurationDiscoveryProfile.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_core_ScannerConfigurationDiscoveryProfile.html deleted file mode 100644 index 773b87aa85c..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_core_ScannerConfigurationDiscoveryProfile.html +++ /dev/null @@ -1,101 +0,0 @@ - - - -Scanner Configuration Discovery Profile - - - - -

Scanner Configuration Discovery Profile

-

-
Identifier:
org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile

-
Since:
3.0 -

- -
Description:
A unified definition of a scanner configuration profile. Usually consists of

-- A make build output parser

-- A scanner info collector

-- An external scanner info generator

- - An external scanner info generator output parser

-
Configuration Markup:
-

-

<!ELEMENT extension (scannerInfoCollector , buildOutputProvider? , scannerInfoProvider*)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #REQUIRED

name  CDATA #REQUIRED>

-

-

-Definition of a profile: -- A scanner info collector -- A make build output parser -- A number of external scanner info providers

-
- -

<!ELEMENT scannerInfoCollector EMPTY>

-

<!ATTLIST scannerInfoCollector

-

class CDATA #REQUIRED

scope (project|file) >

-

- -

<!ELEMENT scannerInfoConsoleParser EMPTY>

-

<!ATTLIST scannerInfoConsoleParser

-

class            CDATA #REQUIRED

compilerCommands CDATA #IMPLIED>

-

-

-Make build output or external scanner info provider output parser.

-
- -

<!ELEMENT buildOutputProvider (open? , scannerInfoConsoleParser)>

-

-

-Build output provider is make build or/and build output file.

-

-

<!ELEMENT scannerInfoProvider ((run | open) , scannerInfoConsoleParser)>

-

<!ATTLIST scannerInfoProvider

-

providerId CDATA #REQUIRED>

-

-

-Either a command with arguments whose output will provide scanner information or a file that contains the scanner info.

-
- -

<!ELEMENT run EMPTY>

-

<!ATTLIST run

-

class     CDATA #IMPLIED

command   CDATA #IMPLIED

arguments CDATA #IMPLIED>

-

- -

<!ELEMENT open EMPTY>

-

<!ATTLIST open

-

class CDATA #IMPLIED

file  CDATA #IMPLIED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
org.eclipse.cdt.make.core.GCCStandardMakePerProjectProfile -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_ui_DiscoveryProfilePage.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_ui_DiscoveryProfilePage.html deleted file mode 100644 index d6dbcd5b26d..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_make_ui_DiscoveryProfilePage.html +++ /dev/null @@ -1,49 +0,0 @@ - - - -Scanner configuration discovery profile options page - - - - -

Scanner configuration discovery profile options page

-

-
Identifier:
org.eclipse.cdt.make.ui.DiscoveryProfilePage

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
A

-
Configuration Markup:
-

-

<!ELEMENT extension (profilePage+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

-

-An extension to define implementation of a SCD profile options page.

-
- -

<!ELEMENT profilePage EMPTY>

-

<!ATTLIST profilePage

-

name      CDATA #REQUIRED

profileId CDATA #REQUIRED

class     CDATA #REQUIRED>

-

-

-Element defines a class that implements SCD profile options page for a profile with specified id.

-
- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_ManagedBuildInfo.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_ManagedBuildInfo.html deleted file mode 100644 index 065e2ef8b9f..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_ManagedBuildInfo.html +++ /dev/null @@ -1,247 +0,0 @@ - - - -Managed Build Tools 2.0 (deprecated) - - - - -

Managed Build Tools 2.0 (deprecated)

-

-
Identifier:
org.eclipse.cdt.core.ManagedBuildTools

-
Since:
1.2 -

- -
Description:
The managed build information model describes targets, configurations, and toolchains for the build system.

-
Configuration Markup:
-

-

<!ELEMENT extension (target , tool , configuration , dynamicElementProvider , managedBuildRevision)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT tool (option , optionCategory)>

-

<!ATTLIST tool

-

id                   CDATA #REQUIRED

name                 CDATA #REQUIRED

sources              CDATA #IMPLIED

outputs              CDATA #IMPLIED

command              CDATA #IMPLIED

outputFlag           CDATA #IMPLIED

outputPrefix         CDATA #IMPLIED

dependencyCalculator CDATA #IMPLIED

headerExtensions     CDATA #IMPLIED

natureFilter         (cnature|ccnature|both) >

-

-

-Defines a tool used in the build process.

-
- -

<!ELEMENT option (enumeratedOptionValue , listOptionValue)>

-

<!ATTLIST option

-

id           CDATA #REQUIRED

name         CDATA #REQUIRED

valueType    (string|stringList|boolean|enumerated|includePath|definedSymbols|libs|userObjs) "string"

category     CDATA #IMPLIED

defaultValue CDATA #IMPLIED

command      CDATA #IMPLIED

commandFalse CDATA #IMPLIED

browseType   (none|file|directory)

helpSupplier CDATA #IMPLIED

tip          CDATA #IMPLIED>

-

-

-An option is associated with a tool. Options can contain boolean values, a simple text string, a selection from an enumerated list, or a list of values. Options also map the value they contain to a command-line flag, such as '-g' in the case of debugging symbol information for compilers.

-
- -

<!ELEMENT enumeratedOptionValue EMPTY>

-

<!ATTLIST enumeratedOptionValue

-

id        CDATA #REQUIRED

name      CDATA #REQUIRED

isDefault (true | false)

command   CDATA #IMPLIED>

-

-

-Defines a single value of an enumerated option.

-
- -

<!ELEMENT configuration (toolReference)>

-

<!ATTLIST configuration

-

id   CDATA #REQUIRED

name CDATA #REQUIRED>

-

-

-A configuration is used to gather together certain default tools and options to build target a certain way. For example, a "Debug" configuration might supply tools with the options set to build with debugging symbols, whereas a "Release" configuration would supply tools with options set to create the best performance.

-
- -

<!ELEMENT toolReference (optionReference)>

-

<!ATTLIST toolReference

-

id           CDATA #REQUIRED

command      CDATA #IMPLIED

outputs      CDATA #IMPLIED

outputPrefix CDATA #IMPLIED

outputFlag   CDATA #IMPLIED>

-

-

-This is reserved for future use. It currently gets instantiated for saving tool settings.

-
- -

<!ELEMENT optionReference (listOptionValue , enumeratedOptionValue)>

-

<!ATTLIST optionReference

-

id           CDATA #REQUIRED

defaultValue CDATA #IMPLIED

command      CDATA #IMPLIED>

-

-

-Option references hold onto information the user has changed through the UI. Not all fields will be populated, depending on the option type the reference overrides. For example, the 'name' field is used by enumerated options only.

-
- -

<!ELEMENT target (tool , configuration , toolReference)>

-

<!ATTLIST target

-

id                   CDATA #REQUIRED

name                 CDATA #IMPLIED

isAbstract           (true | false) "false"

parent               CDATA #IMPLIED

artifactName         CDATA #IMPLIED

defaultExtension     CDATA #IMPLIED

isTest               (true | false)

cleanCommand         CDATA #IMPLIED

makeCommand          CDATA #IMPLIED

makeArguments        CDATA #IMPLIED

binaryParser         CDATA #IMPLIED

osList               CDATA #IMPLIED

archList             CDATA #IMPLIED

errorParsers         CDATA #IMPLIED

scannerInfoCollector CDATA #IMPLIED

makefileGenerator    CDATA #IMPLIED>

-

-

-Represents a type of resource that is the target of the build process, for example, a Linux static library. A target contains a sequence of tool definitions and configurations. Targets are arranged in an inheritance hierarchy where a target inherits the list of tools from it's parent and can add to or override tools in this list.

-
- -

<!ELEMENT optionCategory EMPTY>

-

<!ATTLIST optionCategory

-

id    CDATA #REQUIRED

name  CDATA #IMPLIED

owner CDATA #IMPLIED>

-

-

-An optional, but useful, mechanism for grouping options together.

-
- -

<!ELEMENT listOptionValue EMPTY>

-

<!ATTLIST listOptionValue

-

value   CDATA #REQUIRED

builtIn (true | false) >

-

-

-A value for defining individual elements of a list option.

-
- -

<!ELEMENT dynamicElementProvider EMPTY>

-

<!ATTLIST dynamicElementProvider

-

class CDATA #REQUIRED

name  CDATA #REQUIRED>

-

-

-An optional element that allows a tool implementor to supply a class that creates one or more dynamic toolchain elements. For example, the class might create a new tool reference based on the contents of a special file, and a new target that uses that reference.

-
- -

<!ELEMENT managedBuildRevision EMPTY>

-

<!ATTLIST managedBuildRevision

-

fileVersion CDATA #REQUIRED>

-

-
-

-Version identifier for the managed build extension point. It is a string representation, consisting of three (3) tokens separated by a decimal point. The 3 tokens are positive integer numbers. For example, the following are valid version identifiers: -

-

-
- -
Examples:
The following is an example of the extension point usage: -

-


-   <extension
-         id="buildExample"
-         name="Tools for Build Example"
-         point="org.eclipse.cdt.core.ManagedBuildInfo">
-      <target
-            makeFlags="-k"
-            isTest="false"
-            cleanCommand="rm -rf"
-            name="Executable"
-            defaultExtension=".exe"
-            isAbstract="false"
-            makeCommand="make"
-            id="example.target.executable">
-         <tool
-               sources="C"
-               name="Compiler"
-               outputFlag="-o"
-               outputs="exe"
-               command="g++"
-               id="executable.compiler">
-            <optionCategory
-                  owner="executable.compiler"
-                  name="Flags"
-                  id="compiler.category.flags">
-            </optionCategory>
-            <option
-                  defaultValue="-c"
-                  name="Compiler Flags"
-                  category="compiler.category.flags"
-                  valueType="string"
-                  id="category.flags.comp_flags">
-            </option>
-         </tool>
-         <configuration
-               name="Default"
-               id="example.config.default">
-         </configuration>
-      </target>
-   </extension>
-
-

- -
Supplied Implementation:
An implementation of this extension point is supplied in org.eclipse.cdt.ui -

- -
-

-Copyright (c) 2003, 2004 IBM Corporation and others. -All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available on the Eclipse website. - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_buildDefinitions.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_buildDefinitions.html deleted file mode 100644 index 87e8a7171ba..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_buildDefinitions.html +++ /dev/null @@ -1,630 +0,0 @@ - - - -Managed Build Definitions - - - - -

Managed Build Definitions

-

-
Identifier:
org.eclipse.cdt.managedbuilder.core.buildDefinitions

-
Since:
This extension point was added in CDT 2.1 -

- -
Description:
The managed build object model describes project-types, configurations, tool-chains, etc. for the managed build system.

-
Configuration Markup:
-

-

<!ELEMENT extension (projectType* , configuration* , toolChain* , tool* , targetPlatform* , builder* , dynamicElementProvider* , managedBuildRevision? , buildDefinitionStartup*)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT projectType (configuration*)>

-

<!ATTLIST projectType

-

id                         CDATA #REQUIRED

name                       CDATA #IMPLIED

superClass                 CDATA #IMPLIED

isAbstract                 (true | false) "false"

unusedChildren             CDATA #IMPLIED

isTest                     (true | false)

projectEnvironmentSupplier CDATA #IMPLIED

projectMacroSupplier       CDATA #IMPLIED

configurationNameProvider  CDATA #IMPLIED

convertToId                CDATA #IMPLIED

buildProperties            CDATA #IMPLIED

buildArtefactType          CDATA #IMPLIED>

-

-

-Represents a class of project which acts as a template for the projects that the user will create, for example, a Linux static library. A project type contains a sequence of configurations. Project types are arranged in an inheritance hierarchy where a project type inherits the list of configurations from it's parent and can add to or override configurations in this list.

-
- -

<!ELEMENT project (configuration+)>

-

<!ATTLIST project

-

name        CDATA #REQUIRED

projectType CDATA #REQUIRED>

-

-

-The project element is an instance of a projectType element. It appears in the .cdtbuild file, not in an extension definition.

-
- -

<!ELEMENT configuration (toolChain? , resourceConfiguration* , enablement* , folderInfo* , fileInfo*)>

-

<!ATTLIST configuration

-

id                    CDATA #REQUIRED

name                  CDATA #IMPLIED

parent                CDATA #IMPLIED

artifactName          CDATA #IMPLIED

artifactExtension     CDATA #IMPLIED

cleanCommand          CDATA #IMPLIED

errorParsers          CDATA #IMPLIED

prebuildStep          CDATA #IMPLIED

postbuildStep         CDATA #IMPLIED

preannouncebuildStep  CDATA #IMPLIED

postannouncebuildStep CDATA #IMPLIED

description           CDATA #IMPLIED

buildProperties       CDATA #IMPLIED

buildArtefactType     CDATA #IMPLIED>

-

-

-A configuration is used to gather together certain default tools and options to build project a certain way. For example, a "Debug" configuration might supply tools with the options set to build with debugging symbols, whereas a "Release" configuration would supply tools with options set to create the best performance.

-
- -

<!ELEMENT toolChain (tool* , targetPlatform? , builder? , optionCategory* , option* , supportedProperties?)>

-

<!ATTLIST toolChain

-

id                               CDATA #REQUIRED

name                             CDATA #IMPLIED

superClass                       CDATA #IMPLIED

isAbstract                       (true | false) "false"

unusedChildren                   CDATA #IMPLIED

osList                           CDATA #IMPLIED

archList                         CDATA #IMPLIED

errorParsers                     CDATA #IMPLIED

scannerConfigDiscoveryProfileId  CDATA #IMPLIED

targetTool                       CDATA #IMPLIED

secondaryOutputs                 CDATA #IMPLIED

isToolChainSupported             CDATA #IMPLIED

configurationEnvironmentSupplier CDATA #IMPLIED

configurationMacroSupplier       CDATA #IMPLIED

versionsSupported                CDATA #IMPLIED

convertToId                      CDATA #IMPLIED

optionPathConverter              CDATA #IMPLIED

supportsManagedBuild             (true | false)

isSystem                         (true | false) >

-

-

-A tool-integrator-defined, ordered set of tools that tranform the project's resources into the project's outputs. A tool-chain can be defined as part of a configuration, or as an independent specification that is referenced from a separate configuration via the tool-chain superClass attribute.

-
- -

<!ELEMENT resourceConfiguration (tool+)>

-

<!ATTLIST resourceConfiguration

-

resourcePath      CDATA #REQUIRED

exclude           (true | false)

rcbsApplicability (before|after|override|disable)

toolsToInvoke     CDATA #IMPLIED>

-

-

-A place to store build attributes of individual resources that are different from the configuration as a whole.

-
- -

<!ELEMENT tool (option* , optionCategory* , inputType* , outputType* , envVarBuildPath* , enablement* , supportedProperties?)>

-

<!ATTLIST tool

-

id                    CDATA #REQUIRED

name                  CDATA #IMPLIED

superClass            CDATA #IMPLIED

isAbstract            (true | false) "false"

unusedChildren        CDATA #IMPLIED

sources               CDATA #IMPLIED

headerExtensions      CDATA #IMPLIED

outputs               CDATA #IMPLIED

outputFlag            CDATA #IMPLIED

outputPrefix          CDATA #IMPLIED

natureFilter          (cnature|ccnature|both)

command               CDATA #IMPLIED

commandLinePattern    CDATA #IMPLIED

commandLineGenerator  CDATA #IMPLIED

dependencyCalculator  CDATA #IMPLIED

errorParsers          CDATA #IMPLIED

advancedInputCategory (true | false)

customBuildStep       (true | false)

announcement          CDATA #IMPLIED

icon                  CDATA #IMPLIED

versionsSupported     CDATA #IMPLIED

convertToId           CDATA #IMPLIED

optionPathConverter   CDATA #IMPLIED

supportsManagedBuild  (true | false)

isSystem              (true | false) >

-

-

-Defines a tool used in the build process.

-
- -

<!ELEMENT inputType (inputOrder* , additionalInput* , enablement*)>

-

<!ATTLIST inputType

-

id                              CDATA #REQUIRED

name                            CDATA #IMPLIED

superClass                      CDATA #IMPLIED

sourceContentType               CDATA #IMPLIED

sources                         CDATA #IMPLIED

dependencyContentType           CDATA #IMPLIED

dependencyExtensions            CDATA #IMPLIED

option                          CDATA #IMPLIED

assignToOption                  CDATA #IMPLIED

multipleOfType                  (true | false)

primaryInput                    (true | false)

dependencyCalculator            CDATA #IMPLIED

buildVariable                   CDATA #IMPLIED

scannerConfigDiscoveryProfileId CDATA #IMPLIED

languageId                      CDATA #IMPLIED

languageInfoCalculator          CDATA #IMPLIED>

-

-

-Defines a type of input for the tool. Note that the calculated dependencies of an input type are not described by a separate input type, but are described by attributes of this element.

-
- -

<!ELEMENT inputOrder EMPTY>

-

<!ATTLIST inputOrder

-

path     CDATA #REQUIRED

order    CDATA #IMPLIED

excluded (true | false) >

-

-

-Describes optional, ordering, information regarding the inputs of an inputType. Note: This element is not yet implemented

-
- -

<!ELEMENT additionalInput EMPTY>

-

<!ATTLIST additionalInput

-

paths CDATA #REQUIRED

kind  (additionalinput|additionalinputdependency|additionaldependency) >

-

-

-Describes optional information regarding additional inputs and/or dependencies.

-
- -

<!ELEMENT outputType (enablement*)>

-

<!ATTLIST outputType

-

id                CDATA #REQUIRED

name              CDATA #IMPLIED

superClass        CDATA #IMPLIED

outputContentType CDATA #IMPLIED

outputs           CDATA #IMPLIED

option            CDATA #IMPLIED

multipleOfType    (true | false)

primaryInputType  CDATA #IMPLIED

primaryOutput     (true | false)

outputPrefix      CDATA #IMPLIED

outputNames       CDATA #IMPLIED

namePattern       CDATA #IMPLIED

nameProvider      CDATA #IMPLIED

buildVariable     CDATA #IMPLIED>

-

-

-Defines a type of output for the tool.

-
- -

<!ELEMENT optionCategory EMPTY>

-

<!ATTLIST optionCategory

-

id    CDATA #REQUIRED

name  CDATA #REQUIRED

owner CDATA #IMPLIED

icon  CDATA #IMPLIED>

-

-

-An optional, but useful, mechanism for grouping options together.

-
- -

<!ELEMENT option ((listOptionValue* | enumeratedOptionValue*) , enablement*)>

-

<!ATTLIST option

-

id                        CDATA #REQUIRED

name                      CDATA #IMPLIED

superClass                CDATA #IMPLIED

isAbstract                (true | false) "false"

unusedChildren            CDATA #IMPLIED

category                  CDATA #IMPLIED

resourceFilter            (project|file|all) "all"

valueType                 (string|stringList|boolean|enumerated|includePath|definedSymbols|libs|userObjs|symbolFiles|includeFiles|libPaths|libFiles|undefIncludePath|undefDefinedSymbols|undefLibPaths|undefLibFiles|undefIncludeFiles|undefSymbolFiles) "string"

browseType                (none|file|directory)

value                     CDATA #IMPLIED

defaultValue              CDATA #IMPLIED

command                   CDATA #IMPLIED

commandFalse              CDATA #IMPLIED

helpSupplier              CDATA #IMPLIED

tip                       CDATA #IMPLIED

contextId                 CDATA #IMPLIED

valueHandler              CDATA #IMPLIED

valueHandlerExtraArgument CDATA #IMPLIED

applicabilityCalculator   CDATA #IMPLIED

contextId                 CDATA #IMPLIED>

-

-

-An option is associated with a tool. Options can contain boolean values, a simple text string, a selection from an enumerated list, or a list of values. Options also map the value they contain to a command-line flag, such as '-g' in the case of debugging symbol information for compilers. -Options can also be associated with a toolchain. However in such a case the option must be contained in a optionCategory.

-
- -

<!ELEMENT enumeratedOptionValue EMPTY>

-

<!ATTLIST enumeratedOptionValue

-

id        CDATA #REQUIRED

name      CDATA #REQUIRED

isDefault (true | false)

command   CDATA #IMPLIED>

-

-

-Defines a single value of an enumerated option.

-
- -

<!ELEMENT listOptionValue EMPTY>

-

<!ATTLIST listOptionValue

-

value   CDATA #REQUIRED

builtIn (true | false) >

-

-

-A value for defining individual elements of a list option.

-
- -

<!ELEMENT builder EMPTY>

-

<!ATTLIST builder

-

id                           CDATA #REQUIRED

name                         CDATA #IMPLIED

superClass                   CDATA #IMPLIED

isAbstract                   (true | false) "false"

unusedChildren               CDATA #IMPLIED

command                      CDATA #IMPLIED

arguments                    CDATA #IMPLIED

buildfileGenerator           CDATA #IMPLIED

errorParsers                 CDATA #IMPLIED

variableFormat               CDATA #IMPLIED

isVariableCaseSensitive      (true | false) "false"

reservedMacroNames           CDATA #IMPLIED

reservedMacroNameSupplier    CDATA #IMPLIED

macroInputFileNameValue      CDATA #IMPLIED

macroInputFileExtValue       CDATA #IMPLIED

macroInputFileBaseNameValue  CDATA #IMPLIED

macroInputFileRelPathValue   CDATA #IMPLIED

macroInputDirRelPathValue    CDATA #IMPLIED

macroOutputFileNameValue     CDATA #IMPLIED

macroOutputFileExtValue      CDATA #IMPLIED

macroOutputFileBaseNameValue CDATA #IMPLIED

macroOutputFileRelPathValue  CDATA #IMPLIED

macroOutputDirRelPathValue   CDATA #IMPLIED

versionsSupported            CDATA #IMPLIED

convertToId                  CDATA #IMPLIED

supportsManagedBuild         (true | false)

autoBuildTarget              CDATA #IMPLIED

incrementalBuildTarget       CDATA #IMPLIED

cleanBuildTarget             CDATA #IMPLIED

ignoreErrCmd                 CDATA #IMPLIED

parallelBuildCmd             CDATA #IMPLIED

isSystem                     (true | false) >

-

-

-Represents the utility that drives the build process (typically, but not necessarily, a variant of "make").

-
- -

<!ELEMENT targetPlatform EMPTY>

-

<!ATTLIST targetPlatform

-

id             CDATA #REQUIRED

name           CDATA #IMPLIED

superClass     CDATA #IMPLIED

isAbstract     (true | false) "false"

unusedChildren CDATA #IMPLIED

osList         CDATA #IMPLIED

archList       CDATA #IMPLIED

binaryParser   CDATA #IMPLIED>

-

-

-Represents the os/architecture combination(s) upon which the outputs of a tool-chain can be deployed.

-
- -

<!ELEMENT dynamicElementProvider EMPTY>

-

<!ATTLIST dynamicElementProvider

-

class CDATA #REQUIRED

name  CDATA #REQUIRED>

-

-

-An optional element that allows a tool implementor to supply a class that creates one or more dynamic toolchain elements. For example, the class might create a new tool reference based on the contents of a special file, and a new target that uses that reference.

-
- -

<!ELEMENT buildDefinitionStartup EMPTY>

-

<!ATTLIST buildDefinitionStartup

-

class CDATA #REQUIRED

name  CDATA #REQUIRED>

-

-

-An optional element that allows a tool implementor to supply a class that insures a plugin that modifies any build configruation attributes (e.g. the build config id) will get loaded before initial project information is created.

-
- -

<!ELEMENT managedBuildRevision EMPTY>

-

<!ATTLIST managedBuildRevision

-

fileVersion CDATA #REQUIRED>

-

-
-

-Version identifier for the managed build extension point. It is a string representation, consisting of three (3) tokens separated by a decimal point. The 3 tokens are positive integer numbers. For example, the following are valid version identifiers: -

-

-
- -

<!ELEMENT envVarBuildPath EMPTY>

-

<!ATTLIST envVarBuildPath

-

pathType          (buildpathInclude|buildpathLibrary)

variableList      CDATA #REQUIRED

pathDelimiter     CDATA #IMPLIED

buildPathResolver CDATA #IMPLIED>

-

-

-Defines a set of environment variables used by a tool to represent the build paths (include paths or library paths).

-
- -

<!ELEMENT enablement (and* | or* | not* | checkOption* | checkString* | false* | checkHolder* | checkBuildProperty* | hasNature*)>

-

<!ATTLIST enablement

-

type                CDATA "ALL"

attribute           (command|commandFalse|defaultValue|value|artifactExtension)

value               CDATA #IMPLIED

extensionAdjustment (true | false) >

-

-

-Contains boolean expression that specifies option applicability

-
- -

<!ELEMENT and (and* , or* , not* , checkOption* , checkString* , checkHolder* , checkBuildProperty*)>

-

-

-Represents boolean "and" operation

-

-

<!ELEMENT or (and* , or* , not* , checkOption* , checkString* , checkHolder* , checkBuildProperty*)>

-

-

-Represents boolean "or" operation

-

-

<!ELEMENT not (and* | or* | not* | checkOption* | checkString* | checkHolder* | checkBuildProperty*)>

-

-

-Represents boolean "not" operation

-

-

<!ELEMENT checkOption EMPTY>

-

<!ATTLIST checkOption

-

optionId      CDATA #IMPLIED

holderId      CDATA #IMPLIED

value         CDATA #IMPLIED

isRegex       CDATA "false"

otherOptionId CDATA #IMPLIED

otherHolderId CDATA #IMPLIED>

-

-

-Performs an option value check. The option value can be checked either agains some pre-defined value or against the value of another option

-
- -

<!ELEMENT checkString EMPTY>

-

<!ATTLIST checkString

-

string  CDATA #REQUIRED

value   CDATA #REQUIRED

isRegex CDATA "false">

-

-

-Performs a string check.

-
- -

<!ELEMENT false (#PCDATA)>

-

-

-Represents the "false" value. This element can be used as a direct child of the "enablement" element to represent that the given option applicability is disabled. E.g. to specify that the option is never displayed in UI or never used in the command line.

-

-

<!ELEMENT checkHolder EMPTY>

-

<!ATTLIST checkHolder

-

holderId CDATA #REQUIRED>

-

-

-Performs the holder check.

-
- -

<!ELEMENT checkBuildProperty EMPTY>

-

<!ATTLIST checkBuildProperty

-

property CDATA #IMPLIED

value    CDATA #IMPLIED>

-

-

-Performs the Build Property check

-
- -

<!ELEMENT supportedProperties (property)>

-

-

-contains the list of supported properties

-

-

<!ELEMENT property (value+)>

-

<!ATTLIST property

-

id CDATA #IMPLIED>

-

-

-contains the supported values for the property

-
- -

<!ELEMENT value EMPTY>

-

<!ATTLIST value

-

id CDATA #IMPLIED>

-

-

-represents the property value

-
- -

<!ELEMENT folderInfo (toolChain)>

-

<!ATTLIST folderInfo

-

resourcePath CDATA #REQUIRED

exclude      (true | false) >

-

-

-Represents per-folder settings.

-
- -

<!ELEMENT fileInfo EMPTY>

-

<!ATTLIST fileInfo

-

resourcePath      CDATA #IMPLIED

exclude           (true | false)

rcbsApplicability (before|after|override|disable)

toolsToInvoke     CDATA #IMPLIED>

-

-

-Represents per-file settings. -This element has the same meaning as resourceConfiguration. -It is added for consistency with the folderInfo element. -The only difference between this element and the resourceConfiguration is that resourceConfiguration specifies the resource full path, while the fileInfo specifies project-relative resource path in the same way as the folderInfo does.

-
- -

<!ELEMENT hasNature EMPTY>

-

<!ATTLIST hasNature

-

natureId CDATA #IMPLIED>

-

-

-Checks whether the project containing the resource has a given nature

-
- -
Examples:
[Enter examples here.] -

- -
Supplied Implementation:
An implementation of this extension point is supplied in org.eclipse.cdt.ui -

- -
-

-Copyright (c) 2003, 2006 IBM Corporation and others. -All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available on the Eclipse website. - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_buildProperties.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_buildProperties.html deleted file mode 100644 index 4a70deb8edc..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_buildProperties.html +++ /dev/null @@ -1,57 +0,0 @@ - - - -Build Properties - - - - -

Build Properties

-

-
Identifier:
org.eclipse.cdt.managedbuilder.core.buildProperties

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (propertyType* , propertyValue*)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

-

-The build properties extension point is used to specify the property types and their values to be used with the tool definitions. The primary use if the build properties for now is option anablement/adjustment expressions.

-
- -

<!ELEMENT propertyType EMPTY>

-

<!ATTLIST propertyType

-

id   CDATA #REQUIRED

name CDATA #REQUIRED>

-

-

-specifies the property type

-
- -

<!ELEMENT propertyValue EMPTY>

-

<!ATTLIST propertyValue

-

id       CDATA #REQUIRED

name     CDATA #REQUIRED

property CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_projectConverter.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_projectConverter.html deleted file mode 100644 index 62e5866be7f..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_projectConverter.html +++ /dev/null @@ -1,68 +0,0 @@ - - - -Converter - - - - -

Converter

-

-
Identifier:
org.eclipse.cdt.managedbuilder.core.Converter

-
Since:
CDT version 3.0 -

- -
Description:
This extension point allows a tool integrator to contribute a project-type/tool-chain/tool/builder converter to MBS.

-
Configuration Markup:
-

-

<!ELEMENT extension (converter+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

name  CDATA #IMPLIED

id    CDATA #IMPLIED>

-

- -

<!ELEMENT converter EMPTY>

-

<!ATTLIST converter

-

fromId     CDATA #REQUIRED

toId       CDATA #REQUIRED

mbsVersion CDATA #REQUIRED

class      CDATA #REQUIRED

id         CDATA #REQUIRED

name       CDATA #REQUIRED>

-

-

-This extension point allows a tool integrator to contribute a project-type/tool-chain/tool/builder converter to MBS. Converters can be used to upgrade to newer versions, change the project-type, or to perform conversions between different tool chains/tools/buiders.

-
- -
Examples:

- 


-      <extension point="org.eclipse.cdt.managedbuilder.core.converter">
-         <converter
-            fromId="project-type/tool-chain/tool/builder id"
-            toId="project-type/tool-chain/tool/builder id"
-            mbsVersion="The MBS version the converter was written for"
-            class="org.eclipse.cdt.managedbuilder.core.GccConverter">
-         </converter>
-      </extension>
-
-

-

- -
Supplied Implementation:
"Example plugin" has default implementation of the converter -

- -
-

-Copyright (c) 2005 Intel Corporation and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - -Contributors: -Intel Corporation - Initial API and implementation - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_tcModificationInfo.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_tcModificationInfo.html deleted file mode 100644 index 15fab392509..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_core_tcModificationInfo.html +++ /dev/null @@ -1,81 +0,0 @@ - - - -ToolChain Modification Info - - - - -

ToolChain Modification Info

-

-
Identifier:
org.eclipse.cdt.managedbuilder.core.tcModificationInfo

-
Description:

-
Configuration Markup:
-

-

<!ELEMENT extension (conflictDefinition*)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #REQUIRED

name  CDATA #REQUIRED>

-

- -

<!ELEMENT matchObject (pattern*)>

-

<!ATTLIST matchObject

-

objectIds     CDATA #IMPLIED

objectType    (toolChain|tool|builder|configuration)

searchScope   (ALL_EXTENSION_SUPERCLASSES|EXTENSION_OBJECT) "EXTENSION_SUPERCLASSES"

objectIdsType (REGEXP|EXACT_MATCH) "EXACT_MATCH">

-

-

-specifies the buildObject pattern to be matched.

-
- -

<!ELEMENT conflictDefinition (matchObject)>

-

-

-represents templates for objects conflicting with each other. -
See the "Calculating Tool-chain modification info from the “objects-set” info" section for more information -
the "status" object for this element represents the status information to be applied in case the given conflictingSet information is not fulfilled.

-

-

<!ELEMENT pattern EMPTY>

-

<!ATTLIST pattern

-

objectIds     CDATA #REQUIRED

type          (EXACT_MATCH|REGEXP) "EXACT_MATCH"

searchScope   (ALL_EXTENSION_SUPERCLASSES|EXTENSION_OBJECT) "EXTENSION_SUPERCLASSES"

objectIdsType (REGEXP|EXACT_MATCH) >

-

-

-specifies a string pattern

-
- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_ui_newWizardPages.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_ui_newWizardPages.html deleted file mode 100644 index d650931fcc1..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_managedbuilder_ui_newWizardPages.html +++ /dev/null @@ -1,136 +0,0 @@ - - - -Custom Wizard Pages for MBS New Project Wizards - - - - -

Custom Wizard Pages for MBS New Project Wizards

-

-
Identifier:
org.eclipse.cdt.managedbuilder.ui.newWizardPages

-
Since:
3.0 -

- -
Description:
This extension point allows for the specification of pages to the New Managed C/C++ wizards. Via this extension point, the developer may specify one or more wizard pages to add to the wizard, and optionally only add these pages if certain conditions on the project type, project toolchain, and project nature are met. The developer may also specify a Java class which performs any operations pursuant to the state of the wizard when the user clicks Finish.

-
Configuration Markup:
-

-

<!ELEMENT extension (wizardPage+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

-

-Extensions to this extension point must contain at least one wizardPage child element.

-
- -

<!ELEMENT wizardPage (nature* , toolchain* , projectType*)>

-

<!ATTLIST wizardPage

-

ID             CDATA #REQUIRED

pageClass      CDATA #REQUIRED

operationClass CDATA #IMPLIED>

-

-

-Each instance of this element defines an additional page which is added to the New Project wizard. Pages are added after the default pages provided by MBS. Pages are added in the order they are discovered. - -Note that the IWizardPage interface allows a page to specify programmatically and dynamically at runtime what its previous and next pages are. This element does not trump that behaviour, but rather just specifies the order in which the pages are added to the wizard (and hence the order in which the pages appear if they do not override the previous and next page methods). - -Wizard pages as GUI elements by themselves are really not all that useful. More than likely if someone is defining their own wizard pages it’s because they need some additional operations to happen upon project creation in addition to the stock behaviour of creating a basic project, and they want to use their new wizard pages to provide a front end to these operations. - -As such, along with a specification of the GUI wizard page, ISVs may specify a runnable operation that will be executed in the wizard’s doRunEpilogue() method. These contributions will all be executed in the order that the wizard pages were added to the wizard. Not all pages need have such a contribution however, as ISVs may need to perform all the operations associated with their pages as a group. In cases such as this the ISV can define an operation for one of the pages and it can pull data from any of the other pages as required.

-
- -

<!ELEMENT nature EMPTY>

-

<!ATTLIST nature

-

natureID CDATA #REQUIRED>

-

-

-This optional child element of wizardPage specifies the project nature(s) for which the additional pages should apply. One instance of this element is provided per nature supported. - - This would for example allow one to add pages to the New Managed C Project wizard but not the New Managed C++ project wizard, or other hypothetical natures that might be supported by MBS in the future (e.g. someday there might be a Fortran nature). -If no natureID elements are specified, then it is assumed that the page potentially applies to all project natures, although it may still be excluded based on project type or toolchain.

-
- -

<!ELEMENT toolchain EMPTY>

-

<!ATTLIST toolchain

-

toolchainID       CDATA #REQUIRED

versionsSupported CDATA #IMPLIED>

-

-

-This is an optional child element of wizardPage which specifies a toolchain for which the additional pages should apply. One instance of this element is provided per toolchain supported by the page. - -If no toolchain elements are specified, then it is assumed that the page potentially applies to all toolchains, although it may still be excluded based on project type or project nature.

-
- -

<!ELEMENT projectType EMPTY>

-

<!ATTLIST projectType

-

projectTypeID CDATA #REQUIRED>

-

-

-This is an optional child element of wizardPage which specifies a projectType for which the additional pages should apply. One instance of this element is provided per toolchain supported by the page. - -If no projectType elements are specified, then it is assumed that the page potentially applies to all projectTypes, although it may still be excluded based on toolchain or nature.

-
- -
Examples:
- - - - - - - - - - - - - - - - - - - - -

- -
Supplied Implementation:
None. -

- -
-

-Copyright (c) 2005 Texas Instruments Incorporated and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_CDTWizard.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_CDTWizard.html deleted file mode 100644 index 35d54d04c41..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_CDTWizard.html +++ /dev/null @@ -1,43 +0,0 @@ - - - -CDTWizard - - - - -

CDTWizard

-

-
Identifier:
org.eclipse.cdt.ui.CDTWizard

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (wizard+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT wizard EMPTY>

-

<!ATTLIST wizard

-

class  CDATA #IMPLIED

parent CDATA #IMPLIED

name   CDATA #IMPLIED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_CHelpProvider.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_CHelpProvider.html deleted file mode 100644 index 00fc9d5bc86..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_CHelpProvider.html +++ /dev/null @@ -1,42 +0,0 @@ - - - -C Help Provider - - - - -

C Help Provider

-

-
Identifier:
org.eclipse.cdt.ui.CHelpProvider

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (provider)+>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT provider EMPTY>

-

<!ATTLIST provider

-

class CDATA #REQUIRED

id    CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_ConfigManager.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_ConfigManager.html deleted file mode 100644 index 99074fe1e5f..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_ConfigManager.html +++ /dev/null @@ -1,54 +0,0 @@ - - - -ConfigManager - - - - -

ConfigManager

-

-
Identifier:
org.eclipse.cdt.ui.ConfigManager

-
Since:
CDT 4.0 -

- -
Description:
In the new CDT 4.0 project model, you should be able to override the dialog -that gets displayed when clicking the manage button on any of the C/C++ -project property pages,

-
Configuration Markup:
-

-

<!ELEMENT extension (manager+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT manager EMPTY>

-

<!ATTLIST manager

-

class CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-/********************************************************************** - * Copyright (c) 2007 Intel Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * Intel Corporation - initial API and implementation - **********************************************************************/ - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_DocCommentOwner.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_DocCommentOwner.html deleted file mode 100644 index 70307a69f74..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_DocCommentOwner.html +++ /dev/null @@ -1,67 +0,0 @@ - - - -DocCommentOwner - - - - -

DocCommentOwner

-

-
Identifier:
org.eclipse.cdt.ui.DocCommentOwner

-
Since:
5.0 -

- -
Description:
This extension point allows contribution of document comment detection, presentation and editing behaviours to the CDT editor.

- -Where C and C++ define single and multiline comments, there is no corresponding language level definition of distinguished comments recognized by documentation tools. A list of these is available here: Wikipedia Comparison of Documentation Generators

- -The customization for single and multi-line comments is handled by two contributed implementations of the same interface

-The javadoc for this interface describes the individual editor features that can be contributed.

- -A level of understanding of the eclipse and CDT editor infrastructure is needed in order to contribute to this extension point. A good starting point is to look at the GenericDocTag classes in the package - see the API Information section below.

-
Configuration Markup:
-

-

<!ELEMENT extension (owner)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT owner EMPTY>

-

<!ATTLIST owner

-

id         CDATA #REQUIRED

name       CDATA #REQUIRED

multiline  CDATA #REQUIRED

singleline CDATA #REQUIRED>

-

- -
Examples: 

-<extension
-    point="org.eclipse.cdt.ui.DocCommentOwner">
-    <owner
-        id="org.eclipse.cdt.ui.doxygen"
-        name="Doxygen"
-        multiline="org.eclipse.cdt.ui.text.doctools.doxygen.DoxygenMultilineConfiguration"
-        singleline="org.eclipse.cdt.ui.text.doctools.doxygen.DoxygenSingleConfiguration">
-    </owner>
-</extension>
-
-

- -
Supplied Implementation:
An abstract implementation of some key interfaces is given in the package org.eclipse.cdt.ui.text.doctools.generic -

- -
-

-Copyright (c) 2008 Symbian Software Systems and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_HelpInfo.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_HelpInfo.html deleted file mode 100644 index a262c59c79d..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_HelpInfo.html +++ /dev/null @@ -1,54 +0,0 @@ - - - -Allows contributing the map files to the map-file-based CDT CHelpProvider. - - - - -

Allows contributing the map files to the map-file-based CDT CHelpProvider.

-

-
Identifier:
org.eclipse.cdt.ui.HelpInfo

-
Since:
CDT 4.0.2 -

- -
Description:
Allows contributing the map files to -the map-file-based CDT CHelpProvider.

-
Configuration Markup:
-

-

<!ELEMENT extension (helpInfo+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT helpInfo EMPTY>

-

<!ATTLIST helpInfo

-

file   CDATA #REQUIRED

format CDATA #IMPLIED>

-

-

-Allows defining map-file path relative to the plugin directory.

-
- -
Examples:
- - - - -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_IndexerPage.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_IndexerPage.html deleted file mode 100644 index c869b7b00be..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_IndexerPage.html +++ /dev/null @@ -1,44 +0,0 @@ - - - -Indexer Page - - - - -

Indexer Page

-

-
Identifier:
org.eclipse.cdt.ui.IndexerPage

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (indexerUI+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT indexerUI EMPTY>

-

<!ATTLIST indexerUI

-

id        CDATA #REQUIRED

name      CDATA #REQUIRED

indexerID CDATA #REQUIRED

class     CDATA #REQUIRED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_PathContainerPage.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_PathContainerPage.html deleted file mode 100644 index 6f29c1a4e11..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_PathContainerPage.html +++ /dev/null @@ -1,44 +0,0 @@ - - - -Path Container Page - - - - -

Path Container Page

-

-
Identifier:
org.eclipse.cdt.ui.PathContainerPage

-
Since:
[Enter the first release in which this extension point appears.] -

- -
Description:
[Enter description of this extension point.]

-
Configuration Markup:
-

-

<!ELEMENT extension (PathContainerPage)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT PathContainerPage EMPTY>

-

<!ATTLIST PathContainerPage

-

id    CDATA #REQUIRED

class CDATA #REQUIRED

name  CDATA #REQUIRED

icon  CDATA #IMPLIED>

-

- -
Examples:
[Enter extension point usage example here.] -

- -
Supplied Implementation:
[Enter information about supplied implementation of this extension point.] -

- -
-

-

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_ProposalFilter.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_ProposalFilter.html deleted file mode 100644 index ab0c6224b36..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_ProposalFilter.html +++ /dev/null @@ -1,60 +0,0 @@ - - - -Completion Proposal Filter - - - - -

Completion Proposal Filter

-

-
Identifier:
org.eclipse.cdt.ui.ProposalFilter

-
Since:
CDT 3.1 -

- -
Description:
When the user requests code completion for an identifier prefix then proposals are gathered from a variety of sources. It is quite common that several proposals for the same completion are gathered. After gathering it is therefore necessary to filter proposals and present them in an optimal ordering to the user. - -The notion of what is "optimal" may vary from one application to another. This extension point allows the contribution of completion filters which best suit the needs of the user in any given situation. - -The decision about which filter will actually be used remains with the user who can select his preference from a list of all contributed filters (menu Window - Preferences - C/C++ - Editor - Content Assist).

-
Configuration Markup:
-

-

<!ELEMENT extension (ProposalFilter)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT ProposalFilter EMPTY>

-

<!ATTLIST ProposalFilter

-

id    CDATA #REQUIRED

name  CDATA #REQUIRED

class CDATA #REQUIRED>

-

- -
Examples:
See the default implementation in org.eclipse.cdt.internal.ui.text.contentassist.DefaultProposalFilter as an example. -

- -
API Information:
ProposalFilters must implement interface org.eclipse.cdt.ui.text.contentassist.IProposalFilter. -

- -
Supplied Implementation:
The default implementation in org.eclipse.cdt.internal.ui.text.contentassist.DefaultProposalFilter is the default filtering method which is used as long as the user preference is not changed. -

- -
-

-Copyright (c) 2006 Norbert Ploett and others. - -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -Contributors: -Norbert Ploett (Siemens) - Initial Contribution - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_cPropertyTab.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_cPropertyTab.html deleted file mode 100644 index fe859cd0011..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_cPropertyTab.html +++ /dev/null @@ -1,117 +0,0 @@ - - - -cPropertyTab - - - - -

cPropertyTab

-

-
Identifier:
org.eclipse.cdt.managedbuilder.ui.cPropertyTab

-
Since:
4.0 -

- -
Description:
Implementation of property/preference UI element. - -There're 2 ways to display property/preference data: -either on pages with tabs, or on simple pages. - -In first case, each cPropertyTab extending class -represents single tab in tabfolder. -In second case, cPropertyTab extending class -represents whole page contents (except header -elements which are common for all pages). - -Note that cPropertyTab extending class ("tabs" below) do not -distinguish these 2 cases, moreover, they may be shown both -in multi-tab and single-tab mode. It's up to page to select -displaying mode. - -In multi-tab page, tabs are displayed in order defined by -their weights.

-
Configuration Markup:
-

-

<!ELEMENT extension (tab+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT tab EMPTY>

-

<!ATTLIST tab

-

icon    CDATA #IMPLIED

class   CDATA #REQUIRED

name    CDATA #REQUIRED

parent  CDATA #REQUIRED

tooltip CDATA #IMPLIED

weight  CDATA #IMPLIED

helpId  CDATA #IMPLIED>

-

- -
Examples:
- - -

- -
Supplied Implementation:
Implementors in org.eclipse.cdt.ui.newui: -BinaryParsTab -CLocationOutputTab -CLocationSourceTab -CLocationTab -EnvironmentTab -ErrorParsTab -ExpIncludeTab -ExpLibraryPathTab -ExpLibraryTab -ExpSymbolTab -ICPropertyTab -IncludeTab -LanguagesTab -LibraryPathTab -LibraryTab -RefsTab -SDKsTab -SymbolTab - -Implementors in org.eclipse.cdt.managedbuilder.ui.newui: -ArtifactTab -BuilderSettingsTab -BuildStepsTab -CBuildLocationOutputTab -CPropertyVarsTab -DiscoveryTab -ToolChainEditTab -ToolSettingsTab -

- -
-

-/******************************************************************************* - * Copyright (c) 2007 Intel Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * Intel Corporation - initial API and implementation - *******************************************************************************/ - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_completionProposalComputer.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_completionProposalComputer.html deleted file mode 100644 index 199c9fc50af..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_completionProposalComputer.html +++ /dev/null @@ -1,91 +0,0 @@ - - - -Completion Proposal Computer - - - - -

Completion Proposal Computer

-

-
Identifier:
org.eclipse.cdt.ui.completionProposalComputer

-
Since:
4.0 -

- -
Description:
This extension point allows to contribute completion proposal computers to participate in the content assist process of the C/C++ editor.

-
Configuration Markup:
-

-

<!ELEMENT extension (completionProposalComputer | proposalCategory)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #REQUIRED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT completionProposalComputer (partition)*>

-

<!ATTLIST completionProposalComputer

-

class      CDATA #REQUIRED

activate   (true | false) "false"

categoryId CDATA "org.eclipse.cdt.ui.defaultProposalCategory">

-

-

-A proposal computer contribution. If no partition types are specified, the computer is added to all partition types.

-
- -

<!ELEMENT partition EMPTY>

-

<!ATTLIST partition

-

type (__dftl_partition_content_type|__c_multiline_comment|__c_singleline_comment|__c_string|__c_character|__c_preprocessor|__c_multiline_doc_comment|__c_singleline_doc_comment) >

-

- -

<!ELEMENT proposalCategory EMPTY>

-

<!ATTLIST proposalCategory

-

icon CDATA #IMPLIED>

-

-

-A proposal category contribution defines categories of proposals used to group them in the UI.

-
- -
Examples:
The following is an example of a completion proposal computer contribution: - -

-


- <extension point="org.eclipse.cdt.ui.completionProposalComputer"
-   id="textual_proposals"
-   name="Text Proposals">
-   <proposalCategory icon="icons/wordcompletions.png"/>
- </extension>
- <extension point="org.eclipse.cdt.ui.completionProposalComputer"
-   id="WordCompletionProposalComputer"
-   name="Word Completion Proposal Computer">
-   <completionProposalComputer
-      class="org.eclipse.cdt.internal.ui.text.contentassist.HippieProposalComputer"
-      categoryId="org.eclipse.ui.texteditor.textual_proposals">
-      <partition type="__c_multiline_comment"/>
-   </completionProposalComputer>
- </extension>
-
-

-

- -
Supplied Implementation:
see org.eclipse.cdt.internal.ui.text.contentassist.HippieProposalComputer for an example. -

- -
-

-Copyright (c) 2006, 2007 IBM Corporation and others.
-All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_foldingStructureProviders.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_foldingStructureProviders.html deleted file mode 100644 index 6baa9ff35df..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_foldingStructureProviders.html +++ /dev/null @@ -1,51 +0,0 @@ - - - -C/C++ Folding Structure Provider - - - - -

C/C++ Folding Structure Provider

-

-
Identifier:
org.eclipse.cdt.ui.foldingStructureProviders

-
Since:
3.0 -

- -
Description:
Contributions to this extension point define folding structures for the C/C++ editor. That is, they define the regions of a C/C++ source file that can be folded away. See org.eclipse.jface.text.source.ProjectionViewer for reference. -

-Extensions may optionally contribute a preference block which will appear on the C/C++ editor preference page. -

-
Configuration Markup:
-

-

<!ELEMENT extension (provider)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT provider EMPTY>

-

<!ATTLIST provider

-

id               CDATA #REQUIRED

name             CDATA #IMPLIED

class            CDATA #REQUIRED

preferencesClass CDATA #IMPLIED>

-

- -
Examples:
See org.eclipse.cdt.ui.text.folding.DefaultCFoldingStructureProvider for an example. -

- -
Supplied Implementation:
org.eclipse.cdt.ui.text.folding.DefaultCFoldingStructureProvider provides the default folding structure for the C/C++ editor. - org.eclipse.cdt.internal.ui.text.folding.DefaultCFoldingPreferenceBlock provides the preference block for the default structure provider. -

- -
-

-Copyright (c) 2001, 2006 IBM Corporation and others.
-All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_newCfgDialog.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_newCfgDialog.html deleted file mode 100644 index 8eb6bb33421..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_newCfgDialog.html +++ /dev/null @@ -1,64 +0,0 @@ - - - -newCfgDialog - - - - -

newCfgDialog

-

-
Identifier:
org.eclipse.cdt.ui.newCfgDialog

-
Since:
4.0 -

- -
Description:
Contributions to this extension point define specific dialog for new configuration creation. This dialog will be called from "Manage configurations" screen instead of standard (independent of managed build system) dialog.
-Contributed extension is usually provided with whole managed build system (MBS), so new dialog may be able to handle some MBS-specific features.
-To disinguish numerous dialogs for separate MBSs, mbs_id element should be the same as corresponding MBS Id.

-
Configuration Markup:
-

-

<!ELEMENT extension (dialog+)>

-

<!ATTLIST extension

-

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>

-

- -

<!ELEMENT dialog EMPTY>

-

<!ATTLIST dialog

-

class  CDATA #REQUIRED

title  CDATA #REQUIRED

mbs_id CDATA #REQUIRED>

-

- -
Examples:
- - -

- -
Supplied Implementation:
org.eclipse.cdt.managedbuilder.ui.newui.NewCfgDialog -

- -
-

-/******************************************************************************* - * Copyright (c) 2007 Intel Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * Intel Corporation - initial API and implementation - *******************************************************************************/ - -

- - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_quickAssistProcessors.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_quickAssistProcessors.html deleted file mode 100644 index bb4936560bb..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_quickAssistProcessors.html +++ /dev/null @@ -1,269 +0,0 @@ - - - -Quick Assist Processor - - - - -

Quick Assist Processor

-

-
Identifier:
org.eclipse.cdt.ui.quickAssistProcessors

-
Since:
5.1 -

- -
Description:
This extension point allows to add a Quick Assist processor to offer new Quick Assists in the C/C++ editor. -This extension point supports the enablement tag. Properties to test on are: -
-
  • translationUnit: type ITranslationUnit; the translation unit the quick assist is applied on
    • - -
  • projectNatures: type Collection; all project natures of the current project
    • -

    -

    -
    Configuration Markup:
    -

    -

    <!ELEMENT extension (quickAssistProcessor+)>

    -

    <!ATTLIST extension

    -

    point CDATA #REQUIRED

    id    CDATA #IMPLIED

    name  CDATA #IMPLIED>

    -

    - -

    <!ELEMENT quickAssistProcessor (enablement?)>

    -

    <!ATTLIST quickAssistProcessor

    -

    id                  CDATA #REQUIRED

    name                CDATA #IMPLIED

    class               CDATA #IMPLIED

    requiredSourceLevel CDATA #IMPLIED>

    -

    - -

    <!ELEMENT enablement (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    -

    -A generic root element. The element can be used inside an extension point to define its enablement expression. - The children of an enablement expression are combined using the and operator.

    -

    -

    <!ELEMENT not (not | and | or | instanceof | test | systemTest | equals | count | with | resolve | adapt | iterate | reference)>

    -

    -

    -This element represent a NOT operation on the result of evaluating it's sub-element expression.

    -

    -

    <!ELEMENT and (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    -

    -This element represent an AND operation on the result of evaluating all it's sub-elements expressions.

    -

    -

    <!ELEMENT or (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    -

    -This element represent an OR operation on the result of evaluating all it's sub-element expressions.

    -

    -

    <!ELEMENT instanceof EMPTY>

    -

    <!ATTLIST instanceof

    -

    value CDATA #REQUIRED>

    -

    -

    -This element is used to perform an instanceof check of the object in focus. The expression returns - EvaluationResult.TRUE if the object's type is a sub type of the type specified by the attribute value. - Otherwise EvaluationResult.FALSE is returned.

    -
    - -

    <!ELEMENT test EMPTY>

    -

    <!ATTLIST test

    -

    property              CDATA #REQUIRED

    args                  CDATA #IMPLIED

    value                 CDATA #IMPLIED

    forcePluginActivation (true | false) >

    -

    -

    -This element is used to evaluate the property state of the object in focus. The set of - testable properties can be extended using the propery tester extension point. The test - expression returns EvaluationResult.NOT_LOADED if the property tester doing the actual - testing isn't loaded yet and the attribute forcePluginActivation is set to false. - If forcePluginActivation is set to true and the evaluation context used to evaluate - this expression support plug-in activation then evaluating the property will result in - activating the plug-in defining the tester.

    -
    - -

    <!ELEMENT systemTest EMPTY>

    -

    <!ATTLIST systemTest

    -

    property CDATA #REQUIRED

    value    CDATA #REQUIRED>

    -

    -

    -Tests a system property by calling the System.getProperty method and compares the result - with the value specified through the value attribute.

    -
    - -

    <!ELEMENT equals EMPTY>

    -

    <!ATTLIST equals

    -

    value CDATA #REQUIRED>

    -

    -

    -This element is used to perform an equals check of the object in focus. The expression returns - EvaluationResult.TRUE if the object is equal to the value provided by the attribute value. Otherwise - EvaluationResult.FALSE is returned.

    -
    - -

    <!ELEMENT count EMPTY>

    -

    <!ATTLIST count

    -

    value CDATA #REQUIRED>

    -

    -

    -This element is used to test the number of elements in a collection.

    -
    - -

    <!ELEMENT with (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    <!ATTLIST with

    -

    variable CDATA #REQUIRED>

    -

    -

    -This element changes the object to be inspected for all its child element to the object - referenced by the given variable. If the variable can not be resolved then the expression - will throw a ExpressionException when evaluating it. The children of a with expression - are combined using the and operator.

    -
    - -

    <!ELEMENT resolve (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    <!ATTLIST resolve

    -

    variable CDATA #REQUIRED

    args     CDATA #IMPLIED>

    -

    -

    -This element changes the object to be inspected for all its child element to the object - referenced by the given variable. If the variable can not be resolved then the expression - will throw a ExpressionException when evaluating it. The children of a with expression - are combined using the and operator.

    -
    - -

    <!ELEMENT adapt (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    <!ATTLIST adapt

    -

    type CDATA #REQUIRED>

    -

    -

    -This element is used to adapt the object in focus to the type specified by the attribute - type. The expression returns not loaded if either the adapter or the type referenced isn't - loaded yet. It throws a ExpressionException during evaluation if the type name doesn't exist - at all. The children of an adapt expression are combined using the and operator.

    -
    - -

    <!ELEMENT iterate (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    <!ATTLIST iterate

    -

    operator (or|and)

    ifEmpty  (true | false) >

    -

    -

    -This element is used to iterate over a variable that is of type java.util.Collection. If - the object in focus is not of type java.util.Collection then an ExpressionException will - be thrown while evaluating the expression.

    -
    - -

    <!ELEMENT reference EMPTY>

    -

    <!ATTLIST reference

    -

    definitionId IDREF #REQUIRED>

    -

    -

    -This element is used to reference an expression from the org.eclipse.core.expressions.definitions extension point. The expression definition will be evaluated within the current expression element using the current evaluation context.

    -
    - -
    Examples:
    The following is an example of a Quick Assist processor contribution: - -

    -

    
- <extension point="org.eclipse.cdt.ui.quickAssistProcessors">
-  <quickAssistProcessor
-   id="AdvancedQuickAssistProcessor"
-   name="Advanced Quick Assist Processor"
-   class="com.example.AdvancedQuickAssistProcessor">
-  </quickAssistProcessor>
-   <enablement>
-      <with variable="projectNatures">
-         <iterate operator="or">
-            <equals value="org.eclipse.cdt.core.cnature"/>
-            <equals value="org.eclipse.cdt.core.ccnature"/>
-         </iterate>
-      </with>
-   </enablement>
- </extension>
-
    -

    -

    - -
    -

    -Copyright (c) 2001, 2008 IBM Corporation and others.
    -All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - -

    - - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_quickFixProcessors.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_quickFixProcessors.html deleted file mode 100644 index 58f0757d4bb..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_quickFixProcessors.html +++ /dev/null @@ -1,288 +0,0 @@ - - - -Quick Fix Processor - - - - -

    Quick Fix Processor

    -

    -
    Identifier:
    org.eclipse.cdt.ui.quickFixProcessors

    -
    Since:
    4.1 -

    - -
    Description:
    This extension point allows to add a Quick Fix processor to offer new Quick Fixes on C/C++ problems. -

    -Extension can specify which problem marker types it can handle. It will only get problems of these types to process. -

    -

    -This extension point supports the enablement tag. Properties to test on are: -

    -
  • translationUnit: type ITranslationUnit; the translation unit the quick assist is applied on
    • - -
  • projectNatures: type Collection; all project natures of the current project
    • -
    -

    -

    -
    Configuration Markup:
    -

    -

    <!ELEMENT extension (quickFixProcessor+)>

    -

    <!ATTLIST extension

    -

    point CDATA #REQUIRED

    id    CDATA #IMPLIED

    name  CDATA #IMPLIED>

    -

    - -

    <!ELEMENT quickFixProcessor (enablement? , handledMarkerTypes*)>

    -

    <!ATTLIST quickFixProcessor

    -

    id    CDATA #REQUIRED

    name  CDATA #IMPLIED

    class CDATA #REQUIRED>

    -

    - -

    <!ELEMENT handledMarkerTypes (markerType+)>

    -

    -

    -Specifies the marker types of the problems this quick fix processor can handle. -If no handled marker type are specified, the processor will get problems of types org.eclipse.cdt.core.problem, org.eclipse.cdt.core.buildpath_problem and org.eclipse.cdt.core.task.

    -

    -

    <!ELEMENT markerType EMPTY>

    -

    <!ATTLIST markerType

    -

    id CDATA #REQUIRED>

    -

    - -

    <!ELEMENT enablement (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    -

    -A generic root element. The element can be used inside an extension point to define its enablement expression. - The children of an enablement expression are combined using the and operator.

    -

    -

    <!ELEMENT not (not | and | or | instanceof | test | systemTest | equals | count | with | resolve | adapt | iterate | reference)>

    -

    -

    -This element represent a NOT operation on the result of evaluating it's sub-element expression.

    -

    -

    <!ELEMENT and (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    -

    -This element represent an AND operation on the result of evaluating all it's sub-elements expressions.

    -

    -

    <!ELEMENT or (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    -

    -This element represent an OR operation on the result of evaluating all it's sub-element expressions.

    -

    -

    <!ELEMENT instanceof EMPTY>

    -

    <!ATTLIST instanceof

    -

    value CDATA #REQUIRED>

    -

    -

    -This element is used to perform an instanceof check of the object in focus. The expression returns - EvaluationResult.TRUE if the object's type is a sub type of the type specified by the attribute value. - Otherwise EvaluationResult.FALSE is returned.

    -
    - -

    <!ELEMENT test EMPTY>

    -

    <!ATTLIST test

    -

    property              CDATA #REQUIRED

    args                  CDATA #IMPLIED

    value                 CDATA #IMPLIED

    forcePluginActivation (true | false) >

    -

    -

    -This element is used to evaluate the property state of the object in focus. The set of - testable properties can be extended using the propery tester extension point. The test - expression returns EvaluationResult.NOT_LOADED if the property tester doing the actual - testing isn't loaded yet and the attribute forcePluginActivation is set to false. - If forcePluginActivation is set to true and the evaluation context used to evaluate - this expression support plug-in activation then evaluating the property will result in - activating the plug-in defining the tester.

    -
    - -

    <!ELEMENT systemTest EMPTY>

    -

    <!ATTLIST systemTest

    -

    property CDATA #REQUIRED

    value    CDATA #REQUIRED>

    -

    -

    -Tests a system property by calling the System.getProperty method and compares the result - with the value specified through the value attribute.

    -
    - -

    <!ELEMENT equals EMPTY>

    -

    <!ATTLIST equals

    -

    value CDATA #REQUIRED>

    -

    -

    -This element is used to perform an equals check of the object in focus. The expression returns - EvaluationResult.TRUE if the object is equal to the value provided by the attribute value. Otherwise - EvaluationResult.FALSE is returned.

    -
    - -

    <!ELEMENT count EMPTY>

    -

    <!ATTLIST count

    -

    value CDATA #REQUIRED>

    -

    -

    -This element is used to test the number of elements in a collection.

    -
    - -

    <!ELEMENT with (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    <!ATTLIST with

    -

    variable CDATA #REQUIRED>

    -

    -

    -This element changes the object to be inspected for all its child element to the object - referenced by the given variable. If the variable can not be resolved then the expression - will throw a ExpressionException when evaluating it. The children of a with expression - are combined using the and operator.

    -
    - -

    <!ELEMENT resolve (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    <!ATTLIST resolve

    -

    variable CDATA #REQUIRED

    args     CDATA #IMPLIED>

    -

    -

    -This element changes the object to be inspected for all its child element to the object - referenced by the given variable. If the variable can not be resolved then the expression - will throw a ExpressionException when evaluating it. The children of a with expression - are combined using the and operator.

    -
    - -

    <!ELEMENT adapt (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    <!ATTLIST adapt

    -

    type CDATA #REQUIRED>

    -

    -

    -This element is used to adapt the object in focus to the type specified by the attribute - type. The expression returns not loaded if either the adapter or the type referenced isn't - loaded yet. It throws a ExpressionException during evaluation if the type name doesn't exist - at all. The children of an adapt expression are combined using the and operator.

    -
    - -

    <!ELEMENT iterate (not , and , or , instanceof , test , systemTest , equals , count , with , resolve , adapt , iterate , reference)*>

    -

    <!ATTLIST iterate

    -

    operator (or|and)

    ifEmpty  (true | false) >

    -

    -

    -This element is used to iterate over a variable that is of type java.util.Collection. If - the object in focus is not of type java.util.Collection then an ExpressionException will - be thrown while evaluating the expression.

    -
    - -

    <!ELEMENT reference EMPTY>

    -

    <!ATTLIST reference

    -

    definitionId IDREF #REQUIRED>

    -

    -

    -This element is used to reference an expression from the org.eclipse.core.expressions.definitions extension point. The expression definition will be evaluated within the current expression element using the current evaluation context.

    -
    - -
    Examples:
    The following is an example of a Quick Fix processor contribution: - -

    -

    
- <extension point="org.eclipse.cdt.ui.quickFixProcessors">
-  <quickFixProcessor
-   id="AdvancedQuickFixProcessor"
-   name="Advanced Quick Fix Processor"
-   class="com.example.AdvancedQuickFixProcessor">
-   <handledMarkerTypes>
-      <markerType id="org.eclipse.myplugin.audits"/>
-   </handledMarkerTypes>
-   <enablement>
-      <with variable="projectNatures">
-         <iterate operator="or">
-            <equals value="org.eclipse.cdt.core.cnature"/>
-         </iterate>
-      </with>
-   </enablement>
-  </quickFixProcessor>
- </extension>
-
    -

    -

    - -
    -

    -Copyright (c) 2001, 2007 IBM Corporation and others.
    -All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - -

    - - diff --git a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_textHovers.html b/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_textHovers.html deleted file mode 100644 index bb5f4d75a03..00000000000 --- a/doc/org.eclipse.cdt.doc.isv/reference/extension-points/org_eclipse_cdt_ui_textHovers.html +++ /dev/null @@ -1,58 +0,0 @@ - - - -C/C++ Editor Text Hovers - - - - -

    C/C++ Editor Text Hovers

    -

    -
    Identifier:
    org.eclipse.cdt.ui.textHovers

    -
    Description:
    This extension point is used to plug-in text hovers in a C/C++ editor.

    -
    Configuration Markup:
    -

    -

    <!ELEMENT extension (hover*)>

    -

    <!ATTLIST extension

    -

    point CDATA #REQUIRED

    id    CDATA #IMPLIED

    name  CDATA #IMPLIED>

    -

    - -

    <!ELEMENT hover EMPTY>

    -

    <!ATTLIST hover

    -

    id          CDATA #REQUIRED

    class       CDATA #REQUIRED

    label       CDATA #IMPLIED

    description CDATA #IMPLIED

    activate    (true | false) "false">

    -

    - -
    Examples:
    The following is an example of a hover definition: - -

    -

    
- <extension point="org.eclipse.cdt.ui.textHovers">
-  <hover
-    label="Debug Text Hover"
-    perspective="org.eclipse.debug.ui.DebugPerspective"
-    class="org.eclipse.cdt.debug.internal.ui.editors.DebugTextHover"
-    id="org.eclipse.cdt.debug.internal.ui.editors.DebugTextHover">
-  </hover>
- </extension>
-
    -

    -

    - -
    -

    -Copyright (c) 2001, 2006 IBM Corporation and others.
    -All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - -

    - -