diff options
Diffstat (limited to 'doc/org.eclipse.cdt.doc.isv')
9 files changed, 1174 insertions, 1174 deletions
diff --git a/doc/org.eclipse.cdt.doc.isv/book.css b/doc/org.eclipse.cdt.doc.isv/book.css index 139eb28a09b..0d00c10b7e0 100644 --- a/doc/org.eclipse.cdt.doc.isv/book.css +++ b/doc/org.eclipse.cdt.doc.isv/book.css @@ -1 +1 @@ -P.Code {
display: block;
text-align: left;
text-indent: 0.00pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 15pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #4444CC;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: "Courier New";
}
H6.CaptionFigColumn {
display: block;
text-align: left;
text-indent: 0.000000pt;
margin-top: 3.000000pt;
margin-bottom: 11.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: "Arial";
}
P.Note {
display: block;
text-align: left;
text-indent: 0pt;
margin-top: 19.500000pt;
margin-bottom: 19.500000pt;
margin-right: 0.000000pt;
margin-left: 30pt;
font-size: 11.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: "Arial";
}
EM.UILabel {
font-weight: Bold;
font-style: Regular;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
}
EM.CodeName {
font-weight: Bold;
font-style: Regular;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family:"Courier New";
}
/* following font face declarations need to be removed for DBCS */
body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, Helvetica, sans-serif; color: #000000}
pre { font-family: Courier, monospace}
/* end font face declarations */
/* following font size declarations should be OK for DBCS */
body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-size: 10pt; }
pre { font-size: 10pt}
/* end font size declarations */
body { background: #FFFFFF}
h1 { font-size: 18pt; margin-top: 5; margin-bottom: 1 }
h2 { font-size: 14pt; margin-top: 25; margin-bottom: 3 }
h3 { font-size: 11pt; margin-top: 20; margin-bottom: 3 }
h4 { font-size: 10pt; margin-top: 20; margin-bottom: 3; font-style: italic }
p { margin-top: 10px; margin-bottom: 10px }
pre { margin-left: 6; font-size: 9pt }
a:link { color: #0000FF }
a:hover { color: #000080 }
a:visited { text-decoration: underline }
ul { margin-top: 0; margin-bottom: 10 }
li { margin-top: 0; margin-bottom: 0 }
li p { margin-top: 0; margin-bottom: 0 }
ol { margin-top: 0; margin-bottom: 10 }
dl { margin-top: 0; margin-bottom: 10 }
dt { margin-top: 0; margin-bottom: 0; font-weight: bold }
dd { margin-top: 0; margin-bottom: 0 }
strong { font-weight: bold}
em { font-style: italic}
var { font-style: italic}
div.revision { border-left-style: solid; border-left-width: thin;
border-left-color: #7B68EE; padding-left:5 }
th { font-weight: bold }
\ No newline at end of file +P.Code {
display: block;
text-align: left;
text-indent: 0.00pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 15pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #4444CC;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: "Courier New";
}
H6.CaptionFigColumn {
display: block;
text-align: left;
text-indent: 0.000000pt;
margin-top: 3.000000pt;
margin-bottom: 11.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: "Arial";
}
P.Note {
display: block;
text-align: left;
text-indent: 0pt;
margin-top: 19.500000pt;
margin-bottom: 19.500000pt;
margin-right: 0.000000pt;
margin-left: 30pt;
font-size: 11.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: "Arial";
}
EM.UILabel {
font-weight: Bold;
font-style: Regular;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
}
EM.CodeName {
font-weight: Bold;
font-style: Regular;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family:"Courier New";
}
/* following font face declarations need to be removed for DBCS */
body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, Helvetica, sans-serif; color: #000000}
pre { font-family: Courier, monospace}
/* end font face declarations */
/* following font size declarations should be OK for DBCS */
body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-size: 10pt; }
pre { font-size: 10pt}
/* end font size declarations */
body { background: #FFFFFF}
h1 { font-size: 18pt; margin-top: 5; margin-bottom: 1 }
h2 { font-size: 14pt; margin-top: 25; margin-bottom: 3 }
h3 { font-size: 11pt; margin-top: 20; margin-bottom: 3 }
h4 { font-size: 10pt; margin-top: 20; margin-bottom: 3; font-style: italic }
p { margin-top: 10px; margin-bottom: 10px }
pre { margin-left: 6; font-size: 9pt }
a:link { color: #0000FF }
a:hover { color: #000080 }
a:visited { text-decoration: underline }
ul { margin-top: 0; margin-bottom: 10 }
li { margin-top: 0; margin-bottom: 0 }
li p { margin-top: 0; margin-bottom: 0 }
ol { margin-top: 0; margin-bottom: 10 }
dl { margin-top: 0; margin-bottom: 10 }
dt { margin-top: 0; margin-bottom: 0; font-weight: bold }
dd { margin-top: 0; margin-bottom: 0 }
strong { font-weight: bold}
em { font-style: italic}
var { font-style: italic}
div.revision { border-left-style: solid; border-left-width: thin;
border-left-color: #7B68EE; padding-left:5 }
th { font-weight: bold }
.typewriter {font-family:monospace;}
.bold {font-weight:600;}
.linethrough {text-decoration: line-through;}
.underline {text-decoration: underline;}
\ No newline at end of file diff --git a/doc/org.eclipse.cdt.doc.isv/cdtOptions b/doc/org.eclipse.cdt.doc.isv/cdtOptions index 608b90c040e..a7614513108 100644 --- a/doc/org.eclipse.cdt.doc.isv/cdtOptions +++ b/doc/org.eclipse.cdt.doc.isv/cdtOptions @@ -7,7 +7,7 @@ -splitIndex -windowtitle "Eclipse CDT API Specification" -doctitle "Eclipse CDT API Specification" --header "<b>Eclipse CDT</b><br>Pre-release 3.0" +-header "<strong>Eclipse CDT</strong><br>Pre-release 3.0" -bottom "Copyright (c) IBM Corp. and others 2004. All Rights Reserved." -group "C/C++ Development Tools Core Plug-in Packages" "org.eclipse.cdt.core:org.eclipse.cdt.core.*" -group "C/C++ Development Tools Debug Core Plug-in Packages" "org.eclipse.cdt.debug.core:org.eclipse.cdt.debug.core.*" diff --git a/doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/migration_guides/4.0/migration_guide_40.html b/doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/migration_guides/4.0/migration_guide_40.html index c0161b509bc..3d2641aef8e 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/migration_guides/4.0/migration_guide_40.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/migration_guides/4.0/migration_guide_40.html @@ -67,10 +67,10 @@ table.MsoTableGrid <table border="0" cellpadding="2" width="100%"> <tbody> <tr> - <td align="left" width="72%"><font class="indextop">Migrating your - tool-chain integration to CDT 4.0</font><br> - <font class="indexsub">This document describes steps needed to be - done to migrate the existing tool-chain integrations to the CDT 4.0</font></td> + <td align="left" width="72%">Migrating your + tool-chain integration to CDT 4.0<br> + This document describes steps needed to be + done to migrate the existing tool-chain integrations to the CDT 4.0</td> <td width="28%"><img src="http://dev.eclipse.org/images/Idea.jpg" alt="" height="86" width="120"></td> </tr> @@ -144,8 +144,8 @@ please refer to the "What's New in the CDT Build System" document.</p> different tool-chain/tool/builder must have different names as well as toolChain/tool/builder build definitions representing one and the same tool-chain/tool/builder must have identical names.</p> - <p class="MsoNormal" style="margin-top:0; margin-bottom:0"><b> - Example:</b> to illustrate the above requirement here is how this is handled + <p class="MsoNormal" style="margin-top:0; margin-bottom:0"><strong> + Example:</strong> to illustrate the above requirement here is how this is handled in the gnu tool-chain definitions:</p> <p class="MsoNormal" style="margin-top:0; margin-bottom:0"> The gnu plug-in contains the gcc linker tool on Linux is defined as</p> diff --git a/doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/whats_new/4.0/whats_new_CBS_40.html b/doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/whats_new/4.0/whats_new_CBS_40.html index be0d827295a..5136b3e2288 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/whats_new/4.0/whats_new_CBS_40.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/whats_new/4.0/whats_new_CBS_40.html @@ -31,7 +31,7 @@ h3 margin-left:0in; page-break-after:avoid; font-size:14.0pt; - font-family:Arial; + font-family:"Arial"; font-style:italic} table.MsoTableGrid {border:1.0pt solid windowtext; @@ -68,11 +68,11 @@ table.MsoTableGrid <table border="0" cellpadding="2" width="100%"> <tbody> <tr> - <td align="left" width="72%"><font class="indextop">What's New in CDT - Build System 4.0</font><br> - <font class="indexsub">This document outlines the new features presented + <td align="left" width="72%">What's New in CDT + Build System 4.0<br> + This document outlines the new features presented in the new - CDT build system in CDT 4.0</font></td> + CDT build system in CDT 4.0</td> <td width="28%"><img src="http://dev.eclipse.org/images/Idea.jpg" height="86" width="120" alt="idea"></td> </tr> @@ -196,11 +196,11 @@ functionality (org.eclipse.cdt.managedbuilder.core and org.eclipse.cdt.managedbuilder.ui plug-ins). So all the API that were used for the Managed Build Projects in the CDT 3.x becomes valid for the Makefile Projects in the 4.0, i.e</p> -<p style="margin-top: 0; margin-bottom: 0">The <b> -org.eclipse.cdt.managedbuilder.core.buildDefinitions</b> extension point serves +<p style="margin-top: 0; margin-bottom: 0">The <strong> +org.eclipse.cdt.managedbuilder.core.buildDefinitions</strong> extension point serves as an entry-point for the tool integration into the Build System.</p> -<p style="margin-top: 0; margin-bottom: 0">The <b> -org.eclipse.cdt.managedbuilder.core.ManagedBuildManager</b> class serves as an +<p style="margin-top: 0; margin-bottom: 0">The <strong> +org.eclipse.cdt.managedbuilder.core.ManagedBuildManager</strong> class serves as an entry-point for accessing/manipulating the Build Settings information.</p> <p>From the API point of view there is no principal difference between the Makefile and Managed Build Projects. From the Build System perspective the @@ -230,21 +230,21 @@ Project Wizard" user description for more detail on the New Project Wizard type and tool-chain(s) to be used with the project type.</p> <p> </p> <p><img border="0" src="../../migration_guides/4.0/migrat1.gif" alt="New project wizard dialog"></p> -<p><b>Presenting project-types and tool-chains in the New Project Wizard</b></p> +<p><span class="bold">Presenting project-types and tool-chains in the New Project Wizard</span></p> <p>A tool-integrator has two options of presenting his project-types in the wizard.</p> <ol> <li>Define a new custom Project Type entry.</li> <li>Use the general project type entries mechanism.</li> </ol> -<p><b><font color="#FF0000">NOTE:</font></b> The new New Project Wizard now +<p><strong><span style="color:#FF0000">NOTE:</span></strong> The new New Project Wizard now operates with tool-chains allowing to select the tool-chain(s) to be used on project creation. Thus it is required that all toolChain/tool/builder build definitions representing different tool-chains/tools/builders must have different names as well as toolChain/tool/builder build definitions representing one and the same tool-chain/tool/builder must have identical names.</p> -<p class="MsoNormal" style="margin-top:0; margin-bottom:0"><b> - Example:</b> to illustrate the above requirement here is how this is handled +<p class="MsoNormal" style="margin-top:0; margin-bottom:0"><strong> + Example:</strong> to illustrate the above requirement here is how this is handled in the gnu tool-chain definitions:</p> <p class="MsoNormal" style="margin-top:0; margin-bottom:0"> The gnu plug-in contains the gcc linker tool on Linux is defined as</p> @@ -276,14 +276,14 @@ wizard.</p> different tool(executable) than the Linux linker definition. The cygwin linker definition specifies the name="%ToolName.linker.cygwin.gnu.c" that differs from the one defined by the Linux gcc linker.</p> -<p><b>Defining new Project Type entries</b></p> +<p><span class="bold">Defining new Project Type entries</span></p> <p>In case a tool-integrator is willing his/her project type to be displayed as separate entries with custom names, his project-type definition must specify a "name" property for the project-type, e.g.</p> <p><img border="0" src="whats_3.gif" alt="Project type definition and new project wizard"></p> <p>When the project type entry is selected in the wizard the "Toolchain:" pane will display the list of tool-chains defined/associated with the project type</p> -<p><b>Using general project type entries</b></p> +<p><span class="bold">Using general project type entries</span></p> <p>The "general project types" mechanism allows grouping multiple project types/tool-chains under one project-type entry thus ensuring the compactness of the project-type information and ensuring a common user experience across @@ -291,7 +291,7 @@ different tool-chains and integrations. When the general project type entry is s "ToolChains:" pane will list all tool-chains contributed from different project types allowing user to select the tool-chain to be used with the given project-type.</p> -<p><b>What are the general project type entries?</b></p> +<p><span class="bold">What are the general project type entries?</span></p> <p>The general project type entries mechanism is made based upon the new Build Properties mechanism introduces in the new CDT Build System. Each general project type entry is a value of the "buildArtefactType" property which represents the build @@ -308,7 +308,7 @@ shared library</p> org.eclipse.cdt.managedbuilder.core.buildProperties extension point.</p> <p>See the "Build Properties" section for more detail on the Build Properties mechanism.</p> -<p><b>Contributing to the general project type entries</b></p> +<p><span class="bold">Contributing to the general project type entries</span></p> <p>The minimal steps needed to specify that the general project type entry should be used, a project-type definition should specify the "buildArtefact" attribute and assign it to one of the values of the buildArtefactType build property, e.g.</p> @@ -353,8 +353,8 @@ E.g.</p> <span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: navy"> id=</span><span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: green">"cdt.managedbuild.tool.gnu.builder.mingw.base"</span></p> <p class="MsoNormal" style="text-autospace: none; margin-top: 0; margin-bottom: 0"> -<span style="font-family: Courier New"><font size="2" color="#008000"> -</font><span style="font-size: 10.0pt; color: navy"> ...</span></span></p> +<span style="font-family: Courier New"> +<span style="font-size: 10.0pt; color: navy"> ...</span></span></p> <p class="MsoNormal" style="text-autospace: none; margin-top: 0; margin-bottom: 0"> <span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: black"> </span> <span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: navy"> @@ -418,9 +418,9 @@ supported</p> <p style="margin-top: 0; margin-bottom: 0"> </p> <table border="1" width="725" height="45"> <tr> - <td height="12" width="352" align="center"><b>Modification type</b></td> - <td height="12" width="357" align="center"><b>Possible levels of - modifications</b></td> + <td height="12" width="352" align="center"><strong>Modification type</strong></td> + <td height="12" width="357" align="center"><strong>Possible levels of + modifications</strong></td> </tr> <tr> <td height="11" width="352">Changing/substituting the entire tool-chain</td> @@ -484,12 +484,12 @@ following </p> properties associated with the configuration. (See the "Build Properties mechanism" section for detail on the Build Properties mechanism)</p></li> </ol> -<p><font color="#FF0000"><b>NOTE: </b></font> In order to function properly +<p><span style="color:#FF0000"><strong>NOTE: </strong></span> In order to function properly the tool-chain modification functionality requires that all toolChain/tool/builder build definitions representing different tool-chains/tools/builders must have different names as well as toolChain/tool/builder build definitions representing one and the same tool-chain/tool/builder must have identical names.</p> -<p class="MsoNormal" style="margin-top:0; margin-bottom:0"><b> - Example:</b> to illustrate the above requirement here is how this is handled +<p class="MsoNormal" style="margin-top:0; margin-bottom:0"><strong> + Example:</strong> to illustrate the above requirement here is how this is handled in the gnu tool-chain definitions:</p> <p class="MsoNormal" style="margin-top:0; margin-bottom:0"> The gnu plug-in contains the gcc linker tool on Linux is defined as</p> @@ -562,8 +562,8 @@ functionality:</p> changing the value of the buildArtefactType property in case the tool-chain supports that.</li> </ol> -<p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"><b>Defining new -Build Properties and their values</b></p> +<p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"><span class="bold">Defining new +Build Properties and their values</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0">Build Properties are defined with the org.eclipse.cdt.managedbuilder.core.buildProperties @@ -776,13 +776,13 @@ Build System-predefined properties</span></p> <tr style="height: 13.5pt"> <td width="120" valign="top" style="width: 1.25in; height: 13.5pt; border: 1.0pt solid windowtext; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in"> <p class="MsoNormal" align="center" style="text-align: center; margin-top: 0; margin-bottom: 0"> - <b><span lang="EN-US">Property id</span></b></td> + <strong><span lang="EN-US">Property id</span></strong></td> <td width="324" valign="top" style="width: 243.0pt; height: 13.5pt; border-left: medium none; border-right: 1.0pt solid windowtext; border-top: 1.0pt solid windowtext; border-bottom: 1.0pt solid windowtext; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in"> <p class="MsoNormal" align="center" style="text-align: center; margin-top: 0; margin-bottom: 0"> - <b><span lang="EN-US">Description</span></b></td> + <strong><span lang="EN-US">Description</span></strong></td> <td width="168" valign="top" style="width: 1.75in; height: 13.5pt; border-left: medium none; border-right: 1.0pt solid windowtext; border-top: 1.0pt solid windowtext; border-bottom: 1.0pt solid windowtext; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in"> <p class="MsoNormal" align="center" style="text-align: center; margin-top: 0; margin-bottom: 0"> - <b><span lang="EN-US">Pre-defined Values</span></b></td> + <strong><span lang="EN-US">Pre-defined Values</span></strong></td> </tr> <tr style="height: 8.25pt"> <td width="120" valign="top" style="width: 1.25in; height: 8.25pt; border-left: 1.0pt solid windowtext; border-right: 1.0pt solid windowtext; border-top: medium none; border-bottom: 1.0pt solid windowtext; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in"> @@ -848,8 +848,8 @@ Build System-predefined properties</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"><span lang="EN-US"> </span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> -<p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"><b>Automatic tool -settings adjustment with Build Properties</b></p> +<p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"><span class="bold">Automatic tool +settings adjustment with Build Properties</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0">Tool-chain ant tool definitions can specify enablement expressions to make their default settings be @@ -994,8 +994,8 @@ font-family:"Courier New";color:navy"></option></span></p> information on using enablement expressions please refer to the description of the org.eclipse.cdt.managedbuilder.core.buildDefinitions extension-point.</p> <p style="margin-top: 0; margin-bottom: 0"> </p> -<p style="margin-top: 0; margin-bottom: 0"><b>Specifying the set of supported -build properties</b></p> +<p style="margin-top: 0; margin-bottom: 0"><span class="bold">Specifying the set of supported +build properties</span></p> <p style="margin-top: 0; margin-bottom: 0"> </p> <p style="margin-top: 0; margin-bottom: 0">The tool-chain modification and New Project Wizard mechanisms need to know the set of build properties each @@ -1077,8 +1077,8 @@ color:black"> </span><span style="font-size:10.0pt;font-f </ul> </li> </ol> -<p style="margin-top: 0; margin-bottom: 0"><b>Assigning the set of build -properties for configurations/project-types</b></p> +<p style="margin-top: 0; margin-bottom: 0"><span class="bold">Assigning the set of build +properties for configurations/project-types</span></p> <p style="margin-top: 0; margin-bottom: 0"> </p> <p style="margin-top: 0; margin-bottom: 0">Once the tools/tool-chains has specified the setting adjustment expressions it is possible to use one and the @@ -1102,9 +1102,9 @@ buildArtefactType=</span><span lang="EN-US" style="font-size: 10.0pt; font-famil configurations. The buildArtefactType is a convenience attribute that allows to specify the value for the "buildArtefactType" property.</span></p> <p class="MsoNormal" style="text-autospace: none; margin-top: 0; margin-bottom: 0"> -<font size="2"><span style="font-family: Courier New">It is possible to specify +<span style="font-family: Courier New">It is possible to specify the "buildProperties" attribute for the project type and define the set of build -properties there in the same way as for configuration (see below)</span></font></p> +properties there in the same way as for configuration (see below)</span></p> <p class="MsoNormal" style="text-autospace: none; margin-top: 0; margin-bottom: 0"> <span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: black"> .......</span><span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: navy">></span></p> @@ -1114,8 +1114,8 @@ properties there in the same way as for configuration (see below)</span></font>< <span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: navy"> <configuration</span></p> <p class="MsoNormal" style="text-autospace: none; margin-top: 0; margin-bottom: 0"> -<font size="2" color="#000080"><span style="font-family: Courier New"> -...</span></font></p> +<span style="font-family: Courier New"> +...</span></p> <p class="MsoNormal" style="text-autospace: none; margin-top: 0; margin-bottom: 0"> <span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: black"> </span> @@ -1138,8 +1138,8 @@ color:navy">></span></p> <span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: black"> .....</span><span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: navy">></span></p> <p class="MsoNormal" style="text-autospace: none; margin-top: 0; margin-bottom: 0"> -<font size="2" color="#000080"><span style="font-family: Courier New"> -...</span></font></p> +<span style="font-family: Courier New"> +...</span></p> <p class="MsoNormal" style="text-autospace: none; margin-top: 0; margin-bottom: 0"> <span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: black"> </span> @@ -1172,9 +1172,9 @@ font-family:"Courier New";color:navy"> </toolChain></span>< The folderInfo is a new element presented in 4.0. The element represents the per-folder settings<table border="1" width="688" height="58" id="table21"> <tr> - <td height="30" width="271" align="center"><b>Property</b></td> - <td height="30" width="235" align="center"><b>Description</b></td> - <td height="30" width="160" align="center"><b>Default Value</b></td> + <td height="30" width="271" align="center"><strong>Property</strong></td> + <td height="30" width="235" align="center"><strong>Description</strong></td> + <td height="30" width="160" align="center"><strong>Default Value</strong></td> </tr> <tr> <td height="20" width="271">resourcePath</td> @@ -1202,9 +1202,9 @@ path, while the fileInfo specifies project-relative resource path in the same way as the folderInfo does.</p> <table border="1" width="688" height="58" id="table22"> <tr> - <td height="30" width="271" align="center"><b>Property</b></td> - <td height="30" width="235" align="center"><b>Description</b></td> - <td height="30" width="160" align="center"><b>Default Value</b></td> + <td height="30" width="271" align="center"><strong>Property</strong></td> + <td height="30" width="235" align="center"><strong>Description</strong></td> + <td height="30" width="160" align="center"><strong>Default Value</strong></td> </tr> <tr> <td height="20" width="271">resourcePath</td> @@ -1249,9 +1249,9 @@ way as the folderInfo does.</p> the default value is used ONLY in case the property is undefined for all tool-chain's super-classes<table border="1" width="688" height="58"> <tr> - <td height="30" width="271" align="center"><b>Property</b></td> - <td height="30" width="235" align="center"><b>Description</b></td> - <td height="30" width="160" align="center"><b>Default Value</b></td> + <td height="30" width="271" align="center"><strong>Property</strong></td> + <td height="30" width="235" align="center"><strong>Description</strong></td> + <td height="30" width="160" align="center"><strong>Default Value</strong></td> </tr> <tr> <td height="20" width="271">supportsManagedBuild</td> @@ -1266,9 +1266,9 @@ tool-chain's super-classes<table border="1" width="688" height="58"> the default value is used ONLY in case the property is undefined for all tool's super-classes<table border="1" width="688" height="58" id="table19"> <tr> - <td height="30" width="271" align="center"><b>Property</b></td> - <td height="30" width="235" align="center"><b>Description</b></td> - <td height="30" width="160" align="center"><b>Default Value</b></td> + <td height="30" width="271" align="center"><strong>Property</strong></td> + <td height="30" width="235" align="center"><strong>Description</strong></td> + <td height="30" width="160" align="center"><strong>Default Value</strong></td> </tr> <tr> <td height="20" width="271">supportsManagedBuild</td> @@ -1283,9 +1283,9 @@ super-classes<table border="1" width="688" height="58" id="table19"> the default value is used ONLY in case the property is undefined for all input types's super-classes<table border="1" width="688" height="58" id="table20"> <tr> - <td height="30" width="271" align="center"><b>Property</b></td> - <td height="30" width="235" align="center"><b>Description</b></td> - <td height="30" width="160" align="center"><b>Default Value</b></td> + <td height="30" width="271" align="center"><strong>Property</strong></td> + <td height="30" width="235" align="center"><strong>Description</strong></td> + <td height="30" width="160" align="center"><strong>Default Value</strong></td> </tr> <tr> <td height="20" width="271">languageId</td> @@ -1320,9 +1320,9 @@ types's super-classes<table border="1" width="688" height="58" id="table20"> the default value is used ONLY in case the property is undefined for all input types's super-classes<table border="1" width="688" height="58" id="table23"> <tr> - <td height="30" width="271" align="center"><b>Property</b></td> - <td height="30" width="235" align="center"><b>Description</b></td> - <td height="30" width="160" align="center"><b>Default Value</b></td> + <td height="30" width="271" align="center"><strong>Property</strong></td> + <td height="30" width="235" align="center"><strong>Description</strong></td> + <td height="30" width="160" align="center"><strong>Default Value</strong></td> </tr> <tr> <td height="20" width="271">parallelBuildCmd</td> diff --git a/doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltIndexes.html b/doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltIndexes.html index b4a95d726c5..4fc587350a4 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltIndexes.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltIndexes.html @@ -541,8 +541,8 @@ table.MsoTableGrid <p class=MsoTitle style='text-align:justify'><o:p> </o:p></p> -<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight: -normal'><span style='font-size:11.0pt'><o:p> </o:p></span></b></p> +<p class=MsoNormal style='text-align:justify'><span class="bold" style='mso-bidi-font-weight: +normal'><span style='font-size:11.0pt'><o:p> </o:p></span></span></p> <p class=MsoToc1 style='tab-stops:right dotted 431.5pt'><!--[if supportFields]><span style='font-size:11.0pt;font-weight:normal;mso-bidi-font-weight:bold'><span @@ -796,13 +796,13 @@ style='mso-element:field-end'></span></span><![endif]--></a></span></span><span style='font-size:12.0pt;text-transform:none;font-weight:normal;mso-no-proof: yes'><o:p></o:p></span></p> -<p class=MsoNormal style='text-align:justify'><!--[if supportFields]><b +<p class=MsoNormal style='text-align:justify'><!--[if supportFields]><span class="bold"> style='mso-bidi-font-weight:normal'><span style='font-size:11.0pt'><span -style='mso-element:field-end'></span></span></b><![endif]--><b -style='mso-bidi-font-weight:normal'><span style='font-size:11.0pt'><o:p> </o:p></span></b></p> +style='mso-element:field-end'></span></span></span><![endif]--><span class="bold" +style='mso-bidi-font-weight:normal'><span style='font-size:11.0pt'><o:p> </o:p></span></span></p> -<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight: -normal'><span style='font-size:11.0pt'><o:p> </o:p></span></b></p> +<p class=MsoNormal style='text-align:justify'><span class="bold" style='mso-bidi-font-weight: +normal'><span style='font-size:11.0pt'><o:p> </o:p></span></span></p> <h1 style='text-align:justify'><a name="_Toc164570182">Overview</a></h1> @@ -864,8 +864,8 @@ sufficient.</p> <p class=MsoNormal style='text-align:justify'>The call-back for project creation must implement the following interface</p> -<p class=MsoBodyText style='text-align:justify;text-indent:36.0pt'><b -style='mso-bidi-font-weight:normal'>org.eclipse.cdt.core.index.export.IExportProjectProvider<o:p></o:p></b></p> +<span class=MsoBodyText style='text-align:justify;text-indent:36.0pt'><strong +style='mso-bidi-font-weight:normal'>org.eclipse.cdt.core.index.export.IExportProjectProvider<o:p></o:p></strong></span> <p class=MsoBodyText style='text-align:justify;text-indent:36.0pt'><o:p> </o:p></p> @@ -993,7 +993,7 @@ release.</p> <p class=MsoBodyText style='text-align:justify'>A default implementation of this interface, which is also intended to be sub-classed, is<span -style='mso-tab-count:1'> </span><b style='mso-bidi-font-weight:normal'>org.eclipse.cdt.core.index.export.ExternalExportProjectProvider</b></p> +style='mso-tab-count:1'> </span><strong style='mso-bidi-font-weight:normal'>org.eclipse.cdt.core.index.export.ExternalExportProjectProvider</strong></p> <p class=MsoBodyText style='text-align:justify'><o:p> </o:p></p> @@ -1559,9 +1559,9 @@ style='mso-bookmark:_Toc164570192'></span><span style='font-size:11.0pt'><o:p></ generated and distributed to the user’s computer, the mechanism to have that content appear within a CDT 4.0 session is via another extension point:</p> -<p class=MsoNormal style='text-align:justify'><b style='mso-bidi-font-weight: -normal'><span style='mso-tab-count:1'> </span><span class=SpellE>org.eclipse.cdt.core.CIndex.ReadOnlyPDOMProvider</span><i -style='mso-bidi-font-style:normal'><o:p></o:p></i></b></p> +<span class=MsoNormal style='text-align:justify'><strong style='mso-bidi-font-weight: +normal'><span style='mso-tab-count:1'> </span><span class=SpellE>org.eclipse.cdt.core.CIndex.ReadOnlyPDOMProvider</span><em +style='mso-bidi-font-style:normal'><o:p></o:p></em></strong></span> <p class=MsoNormal style='text-align:justify'><o:p> </o:p></p> @@ -1581,12 +1581,12 @@ _Toc164570193'></span></h2> has the concept of project configurations, which in terms of code corresponds to the interface:</p> -<p class=MsoNormal style='text-align:justify;text-indent:36.0pt'><span -class=SpellE><b style='mso-bidi-font-weight:normal'>org.eclipse.cdt.core.settings.model.ICConfigurationDescription</b></span><b -style='mso-bidi-font-weight:normal'><o:p></o:p></b></p> +<span class=MsoNormal style='text-align:justify;text-indent:36.0pt'><span +class=SpellE><strong style='mso-bidi-font-weight:normal'>org.eclipse.cdt.core.settings.model.ICConfigurationDescription</strong></span><strong +style='mso-bidi-font-weight:normal'><o:p></o:p></strong></span> -<p class=MsoNormal style='text-align:justify;text-indent:36.0pt'><b -style='mso-bidi-font-weight:normal'><o:p> </o:p></b></p> +<span class=MsoNormal style='text-align:justify;text-indent:36.0pt'><strong +style='mso-bidi-font-weight:normal'><o:p> </o:p></strong></span> <p class=MsoNormal style='text-align:justify'>The index model allows content to be associated with <span class=SpellE>ICConfigurationDescription</span> objects diff --git a/doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltVersioning.html b/doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltVersioning.html index ec4fabde8f7..74bbf9e27ef 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltVersioning.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltVersioning.html @@ -167,7 +167,7 @@ another. “Built With” is the vertical axis.</p> <td width=118 valign=top style='width:88.55pt;border-top:none;border-left: none;border-bottom:solid white 2.25pt;border-right:solid white 2.25pt; background:#CCCCCC;padding:0cm 5.4pt 0cm 5.4pt'> - <p class=MsoNormal><b><span style='font-size:8.0pt'>Built With \ Use With</span></b></p> + <span class=MsoNormal><strong><span style='font-size:8.0pt'>Built With \ Use With</span></strong></span> </td> <td width=118 valign=top style='width:88.55pt;border-top:none;border-left: none;border-bottom:solid white 2.25pt;border-right:solid white 2.25pt; @@ -186,7 +186,7 @@ another. “Built With” is the vertical axis.</p> </td> <td width=44 valign=top style='width:32.8pt;border:none;border-bottom:solid white 2.25pt; background:#CCCCCC;padding:0cm 5.4pt 0cm 5.4pt'> - <p class=MsoNormal><b> </b></p> + <span class=MsoNormal><strong> </strong></span> </td> </tr> <tr style='mso-yfti-irow:1'> diff --git a/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html b/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html index 2dd20a15d48..47fe067d3f6 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html @@ -68,10 +68,10 @@ table.MsoTableGrid <table border="0" cellpadding="2" width="100%"> <tbody> <tr> - <td align="left" width="72%"><font class="indextop">Managed Build -System Extensibility Document</font><br> - <font class="indexsub">This document describes the design of the -managed build system and how to extend it.</font></td> + <td align="left" width="72%">Managed Build +System Extensibility Document<br> + This document describes the design of the +managed build system and how to extend it.</td> <td width="28%"><img src="http://dev.eclipse.org/images/Idea.jpg" alt="idea" height="86" width="120"></td> </tr> @@ -219,8 +219,8 @@ managed build system and how to extend it.</font></td> </div> <!-- End of Table of Contents --><br> <p class="section"><a name="_TocSectionIntro">1 Introduction</a></p> -<p style="margin-top: 0; margin-bottom: 0"><b><font color="#FF0000">NOTE: </font> -</b>the document describes the CDT Managed Build System (MBS) 3.x functionality. +<p style="margin-top: 0; margin-bottom: 0"><strong><span style="color:#FF0000">NOTE: </span> +</strong>the document describes the CDT Managed Build System (MBS) 3.x functionality. Although there have been lots of significant changes made to the Build System in the 4.0, the document still remains valid since all the 4.0 build system changes were made by extending the MBS functionality described in this document.</p> @@ -439,7 +439,7 @@ contains the following primary objects: </p> </table> <p class="subsection"><a name="_TocSectionUIModel_1">2.1 User Scenarios</a></p> <p>The following sections describe how the user interacts with MBS. Text -in <font color="#FF0000">red </font>indicates MBS functionality that is not yet +in <span style="color:#FF0000">red </span>indicates MBS functionality that is not yet implemented, but is intended to be implemented in future releases of MBS.</p> <h3 class="subsection">2.1.1 Creating a New Project</h3> <p class="MsoNormal" style="margin-top:6.0pt">The CDT user’s experience with the @@ -464,7 +464,7 @@ consideration by turning them off in the MBS Preferences page.</span></p> filtering, however configurations that use tool-chains that are not installed will not be able to be built on the host system.</p> <p class="MsoNormal" style="margin-top:6.0pt">After selecting the project type, -the user selects 1 … <i>n </i>configurations for her new project from the list +the user selects 1 … <em>n </em>configurations for her new project from the list of configurations defined in the project type. Different configurations can use different tool-chains. The list of configurations is, by default, filtered by:</p> @@ -501,63 +501,63 @@ tool-chain. It should be easy for a user to take an existing CDT project t different host system and quickly create a configuration that builds on that host system using a version of the tool-chain that supports the new host.</span></p> <p class="MsoNormal" style="margin-top:6.0pt">The user -can also pick 1 … <i>n </i>configurations from the list of default +can also pick 1 … <em>n </em>configurations from the list of default configurations defined in the project type. The list of configurations is, by default, filtered as specified above.</p> <h3 class="subsection">2.1.3 Modifying the Tool-chain of the Configuration</h3> <p class="MsoNormal">The user can select a configuration and modify the following attributes of the tool-chain: </p> <ol style="margin-top: 0in; margin-bottom: 0in" start="1" type="1"> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">The command used to invoke a - particular tool in the tool-chain.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">The set of error parsers to + <li style="margin-top: 6.0pt"> + The command used to invoke a + particular tool in the tool-chain.</li> + <li style="margin-top: 6.0pt"> + The set of error parsers to be used with the build output and the order that the error parsers will be - invoked </font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">The binary parser to be used - with the build binary outputs.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">The set of file extensions - that are processed by a tool.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">The + invoked </li> + <li style="margin-top: 6.0pt"> + The binary parser to be used + with the build binary outputs.</li> + <li style="margin-top: 6.0pt"> + The set of file extensions + that are processed by a tool.</li> + <li style="margin-top: 6.0pt"> + The addition of Custom Build steps before or after the build. The user specifies the commands - to be executed by the step.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">The mapping of an individual + to be executed by the step.</li> + <li style="margin-top: 6.0pt"> + The mapping of an individual resource to a Custom Build step. The user specifies the commands to be executed by the step, the input dependencies of the step, and the output files that are created by the - step.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2" color="#FF0000">The mapping of + step.</li> + <li style="margin-top: 6.0pt"> + The mapping of a set of file extensions to a Custom Build step. The user specifies the commands to be executed by the step, the input dependencies of the step, and the output resources that are created by the - step.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2"><span style="color:red">The + step.</li> + <li style="margin-top: 6.0pt"> + <span style="color:red">The tool-chain itself: The user can change the tool-chain to be used with the configuration. All applicable settings are automatically transferred to the - new tool-chain.</span></font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2"><span style="color:red">The + new tool-chain.</span></li> + <li style="margin-top: 6.0pt"> + <span style="color:red">The mapping of an individual resource to a tool: </span> <span style="color:red">The available tools come from the configuration’s - tool-chain, from a different tool-chain or from individually defined tools.</span></font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2"><span style="color:red">The + tool-chain, from a different tool-chain or from individually defined tools.</span></li> + <li style="margin-top: 6.0pt"> + <span style="color:red">The mapping of a set file extensions to a category of tools or a specific tool: The user can modify the current assignments and add new assignments. The available tools come from the configuration’s tool-chain, - from a different tool-chain or from individually defined tools.</span></font></li> + from a different tool-chain or from individually defined tools.</span></li> </ol> <h3 class="subsection">2.1.4 Modifying the Tool Options of the Configuration</h3> <p class="MsoNormal" style="margin-top:6.0pt">The user can modify the options of -an individual configuration<font color="#FF0000">, or he can make changes to a set of configurations -that he has selected</font>. <font color="#FF0000">The user can select a set of configurations individually</font><span style="color:red"> +an individual configuration<span style="color:#FF0000">, or he can make changes to a set of configurations +that he has selected</span>. <span style="color:#FF0000">The user can select a set of configurations individually</span><span style="color:red"> or by selecting a “category” of configurations. The names of the categories are defined by the configuration provider – “debug” and “release” are commonly supported. Categories which group configurations by target platform could also @@ -612,18 +612,18 @@ project file (.cdtbuild).</p> <p class="MsoNormal" style="margin-top:6.0pt">When MBS reads a project file with an older version number:</p> <ol style="margin-top: 0in; margin-bottom: 0in" start="1" type="1"> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">MBS asks the user to confirm - the conversion.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">If the user confirms the + <li style="margin-top: 6.0pt"> + MBS asks the user to confirm + the conversion.</li> + <li style="margin-top: 6.0pt"> + If the user confirms the conversion, the project file is converted and the project can no longer be - loaded by previous versions of MBS.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">If the user does not confirm + loaded by previous versions of MBS.</li> + <li style="margin-top: 6.0pt"> + If the user does not confirm the conversion, the MBS information is loaded in a read-only mode, and any changes made to the MBS information will be discarded when the project is - closed.</font></li> + closed.</li> </ol> <p class="MsoNormal" style="margin-top:6.0pt">When MBS reads a project file with a newer version number, it displays an error message, and does not load the MBS @@ -634,38 +634,38 @@ also define a version number. The version number is appended to the end of the element id, and stored by MBS with each reference to the element. MBS attempts to resolve references in the following manner:</p> <ol style="margin-top: 0in; margin-bottom: 0in" start="1" type="1"> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">MBS looks up the id with the - version specified with the reference. </font> </li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">If not found, MBS looks up + <li style="margin-top: 6.0pt"> + MBS looks up the id with the + version specified with the reference. </li> + <li style="margin-top: 6.0pt"> + If not found, MBS looks up all occurrences of the id, and selects a match in the following order: - </font> + <ol style="margin-top: 0in; margin-bottom: 0in" start="1" type="a"> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">the id with the closest - higher version number that lists the referenced version in its <i> - versionsSupported</i> attribute</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">the id with no version - information specified</font></li> + <li style="margin-top: 6.0pt"> + the id with the closest + higher version number that lists the referenced version in its <em> + versionsSupported</em> attribute</li> + <li style="margin-top: 6.0pt"> + the id with no version + information specified</li> </ol> </li> </ol> <p class="MsoNormal" style="margin-top:6.0pt">If a match is found, there are 2 scenarios:</p> <ol style="margin-top: 0in; margin-bottom: 0in" start="1" type="1"> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">The version is still + <li style="margin-top: 6.0pt"> + The version is still actively supported by the tool integrator, and the MBS information is - loaded.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"> - <font face="arial, helvetica, geneva" size="2">The version specifies that a + loaded.</li> + <li style="margin-top: 6.0pt"> +The version specifies that a conversion to a later version of the tool-chain/tool/builder is required. At the discretion of the tool-chain/tool/builder, the conversion may occur automatically, or the converter may prompt the user to confirm the upgrade. The same rules apply as above for whether or not the user confirms the - conversion.</font></li> + conversion.</li> </ol> <p class="MsoNormal" style="margin-top:6.0pt">If no match is found, MBS displays an error message, and does not load the MBS information. None of the MBS @@ -681,16 +681,16 @@ describes the format of the grammar and what the information is used for by the build model. See the CDT 3.0 Gnu tool-chain definitions for an example of using the managed build object model.</p> <h3>Common Attributes</h3> -<p>Many of the MBS elements require the specification of the <i>id </i> +<p>Many of the MBS elements require the specification of the <em>id </em> attribute. The attribute value typically takes a form similar to Eclipse -package names, e.g. "cdt.managedbuild.tool.gnu.c.linker". Each <i>id</i> +package names, e.g. "cdt.managedbuild.tool.gnu.c.linker". Each <em>id</em> must be unique within MBS and among all of the loaded manifest files. It is suggested that you include your company/organization name in -the <i>id</i>s that you create.</p> -<p>Many of the MBS elements can specify the <i>name </i>attribute. The +the <em>id</em>s that you create.</p> +<p>Many of the MBS elements can specify the <em>name </em>attribute. The attribute value is used in the MBS user interface, and may therefore change if your tool-chain supports more than one language. You can use a plugin.properties file in order to define these strings in an external file (see the Gnu tool-chain definitions for an example).</p> -<p>Many of the MBS elements can specify the <i>superClass </i>attribute. +<p>Many of the MBS elements can specify the <em>superClass </em>attribute. The attribute value is the id of an element of the same type as this element. For most attributes, when the value of an attribute is not specified in an element, the value will default to the value defined by the first super-class @@ -708,8 +708,8 @@ that the attribute is required by the schema for every instance of the element.& "No" means that the attribute is never required and an appropriate default is supplied if necessary. "In Hierarchy" means that the attribute is not required by the schema, but MBS requires that the attribute be specified -either by the element itself, or inherited from one of its ancestors (see the <i>superClass - </i>attribute).</li> +either by the element itself, or inherited from one of its ancestors (see the <em>superClass + </em>attribute).</li> </ul> <p class="subsection"><a name="_TocSectionGrammar_1">3.1 Model</a></p> <p class="MsoNormal" style="margin-top:6.0pt">The figure below shows a UML model @@ -729,7 +729,7 @@ template for the projects that a user will create. The projectType contain or more children of type configuration. These are the default configurations that the user can choose from. Note that there is no reason to define a projectType element in a .cdtbuild file. It would never be used since projectType elements are used to populate the New Project dialog boxes.</p> -<p class="MsoNormal" style="margin-top:6.0pt">You must provide a unique identifier for the project-type in the <i>id</i> +<p class="MsoNormal" style="margin-top:6.0pt">You must provide a unique identifier for the project-type in the <em>id</em> attribute. The build model uses this information to distinguish between the project-type definitions it finds. You must also @@ -739,22 +739,22 @@ in the UI and new project wizards.</p> <p class="MsoNormal" style="margin-top:6.0pt">Project-types can be arranged into hierarchies to promote the efficient sharing of configurations. If you have defined a project-type that should not be selected by the user, but is a root -for other project-types, it may be declared abstract by setting the <i> -isAbstract</i> attribute to ‘true’. Abstract project-types do not appear in the +for other project-types, it may be declared abstract by setting the <em> +isAbstract</em> attribute to ‘true’. Abstract project-types do not appear in the UI. Descendents of an abstract project-type will have the same configurations that the abstract project-type has. For these children to -function properly, their <i>superClass</i> attribute must contain +function properly, their <em>superClass</em> attribute must contain the unique identifier of the super-class project-type.</p> <p class="MsoNormal" style="margin-top:6.0pt">A concrete project type must have at least one configuration defined for it. A configuration must define (or inherit) a set of tool-chain definitions that work together to produce the build goal as an output.</p> <p class="MsoNormal" style="margin-top:6.0pt">A projectType may define a project -level environment variable provider in the <i>projectEnvironmentSupplier</i> attribute. See § +level environment variable provider in the <em>projectEnvironmentSupplier</em> attribute. See § 7.6 for additional information.<br> </p> <p class="MsoNormal" style="margin-top:6.0pt">A projectType may define a project -level macro provider in the <i>projectMacroSupplier</i> attribute. See § +level macro provider in the <em>projectMacroSupplier</em> attribute. See § 7.8 for additional information.<br> </p> <p class="subsection">3.2.1 Schema</p> @@ -820,7 +820,7 @@ UI.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top" height="17"> - <font size="2">The unique identifier of the projectType that this projectType is derived from.</font></td> + The unique identifier of the projectType that this projectType is derived from.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top" height="17"> @@ -835,10 +835,10 @@ UI.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top" height="49"> - <p><font size="2">Flags the projectType as abstract. An abstract + <p>Flags the projectType as abstract. An abstract projectType can not be selected by the user in the UI, but projectTypes derived from this projectType will inherit its attributes and children. - The default value is false.</font></p> + The default value is false.</p> </td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" @@ -854,9 +854,9 @@ UI.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top" height="49"> - <p><font size="2">A projectType can be flagged for test purposes only. It + <p>A projectType can be flagged for test purposes only. It can be manipulated programmatically, in JUnit tests for example, but not - selected by the user in the UI. The default value is false.</font></p> + selected by the user in the UI. The default value is false.</p> </td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" @@ -938,21 +938,21 @@ a manifest file – it would never be used.</p> <p class="MsoNormal" style="margin-top:6.0pt">The following steps occur when a CDT user creates a new Managed Build project:</p> <ol> - <li><font face="arial, helvetica, geneva" size="2">A new managedProject element is - created. Its <i>projectType</i> attribute is set to the projectType that - the user selected. Its <i>name</i> attribute is set to the project name - that the user entered.</font></li> - <li><font face="arial, helvetica, geneva" size="2">When the user adds a + <li>A new managedProject element is + created. Its <em>projectType</em> attribute is set to the projectType that + the user selected. Its <em>name</em> attribute is set to the project name + that the user entered.</li> + <li>When the user adds a default configuration, the selected configuration element is cloned to - become a child of the managedProject element created in step 1.</font></li> - <li><font face="arial, helvetica, geneva" size="2">Add a tool-chain element - that specifies as its <i>superClass</i> the tool-chain that is the child of - the selected configuration element.</font></li> - <li><font face="arial, helvetica, geneva" size="2">For each tool element + become a child of the managedProject element created in step 1.</li> + <li>Add a tool-chain element + that specifies as its <em>superClass</em> the tool-chain that is the child of + the selected configuration element.</li> + <li>For each tool element child of the tool-chain that is the child of the selected configuration element, create a tool element child of the cloned configuration’s - tool-chain element that specifies the original tool element as its <i> - superClass</i>.</font></li> + tool-chain element that specifies the original tool element as its <em> + superClass</em>.</li> </ol> <p class="MsoNormal" style="margin-top:6.0pt">This prepares the new project/configurations for modification by the user.</p> @@ -998,8 +998,8 @@ UI. This is the name that the user entered in the New Project wizard.</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top" height="33"> - <font size="2">The unique identifier of the projectType that was used when - creating this project.</font></td> + The unique identifier of the projectType that was used when + creating this project.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top" height="33"> @@ -1019,8 +1019,8 @@ configuration.</p> child of type tool-chain. This describes how the project’s resources are transformed into the build artifact. The configuration is responsible for maintaining the name of the final build goal. The user selects the name of the -build artifact in the UI, and the configuration maintains it in the <i> -artifactName</i> and <i>artifactExtension </i>attributes. The +build artifact in the UI, and the configuration maintains it in the <em> +artifactName</em> and <em>artifactExtension </em>attributes. The configuration can contain one or more children of type resourceConfiguration. These describe build settings of individual resources that are different from the configuration as a whole. </p> @@ -1029,10 +1029,10 @@ attribute that will be used by the build model to manage the configuration. It must also have a <var>name</var> that will be displayed in the UI in the build property page and new project wizards. The configuration contains the information needed to “clean” the build files on -the host machine. The configuration can specify the <i>cleanCommand</i> +the host machine. The configuration can specify the <em>cleanCommand</em> attribute which specifies a command that removes the build files.</p> -<p class="MsoNormal" style="margin-top:6.0pt">The<i> prebuildStep, -preannounceBuildStep, postbuildStep </i>and <i>postannouncebuildStep </i> +<p class="MsoNormal" style="margin-top:6.0pt">The<em> prebuildStep, +preannounceBuildStep, postbuildStep </em>and <em>postannouncebuildStep </em> attributes define a custom build step to be run before and/or after the the build steps defined by the tool-chain. These attributes are not typically defined in the manifest file, but are instead added by a user from the @@ -1084,8 +1084,8 @@ track of this specific configuration.</td> parent</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">The unique identifier of the configuration that this - configuration is derived from.</font></td> + The unique identifier of the configuration that this + configuration is derived from.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -1096,8 +1096,8 @@ track of this specific configuration.</td> artifactName</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">The name of the build goal defined by the configuration. - This can be set by the user in the UI.</font></td> + The name of the build goal defined by the configuration. + This can be set by the user in the UI.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -1108,8 +1108,8 @@ track of this specific configuration.</td> artifactExtension</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">The extension that the build goal will have, for example - ‘.exe’ or ‘.so’</font></td> + The extension that the build goal will have, for example + ‘.exe’ or ‘.so’</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> in hierarchy</td> @@ -1120,8 +1120,8 @@ track of this specific configuration.</td> cleanCommand</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">The command to remove intermediary and output files on the - build machine.</font></td> + The command to remove intermediary and output files on the + build machine.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -1135,13 +1135,13 @@ track of this specific configuration.</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font size="2">The semi-colon separated list of the default error parsers + The semi-colon separated list of the default error parsers to be used with this configuration. The list is ordered with the first error parser on the list invoked first, the second error parser second, and so on. The list may contain the error parsers defined by CDT and/or other installed error parser extensions. The list of error parsers to be used may be changed by the user on a per-configuration basis. When - specified, this overrides the tool-chain errorParsers attribute.</font></td> + specified, this overrides the tool-chain errorParsers attribute.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -1249,33 +1249,33 @@ only on a limited subset of operating system/architecture combinations. For example, it does not make much sense to allow a user to try to build a Solaris shared library project if they are running Eclipse and CDT on Windows. You can specify the operating systems and architectures that the tool-chain is supported -on as a comma-separated list in the <i>osList</i> and <i>archList</i> +on as a comma-separated list in the <em>osList</em> and <em>archList</em> attributes. </p> -<p class="MsoNormal" style="margin-top:6.0pt">A tool-chain should specify the <i> -targetTool </i>attribute to identify the tool that runs to generate the primary +<p class="MsoNormal" style="margin-top:6.0pt">A tool-chain should specify the <em> +targetTool </em>attribute to identify the tool that runs to generate the primary build output. If this is not specified, MBS uses the file extension of the build artifact name supplied by the user. This will work when the user uses one of the extensions expected by the tool, but will not work if they do not.</p> <p class="MsoNormal" style="margin-top:6.0pt">MBS supports multiple versions of -a tool-chain. The <i>versionsSupported</i><b> </b>attribute contains a +a tool-chain. The <em>versionsSupported</em><strong> </strong>attribute contains a list of supported versions of a particular tool chain. This indicates that there is no need to perform a conversion when user imports/loads a project with one of the supported tool chain versions. When a tool integrator decides to no longer support a version of a tool chain, they continue to ship the old tool chain definition and specify the id with version number of the tool chain definition -to convert to in the <i>convertToId</i> attribute. If changes to the project +to convert to in the <em>convertToId</em> attribute. If changes to the project information need to be performed by the conversion, the tool chain must provide a converter extension to perform the conversion. If no converter extension is provided, then there won’t be any conversion. See § 8.2 for additional information.</p> <p class="MsoNormal" style="margin-top:6.0pt">A tool-chain may define a -configuration level environment variable provider in the <i>configurationEnvironmentSupplier</i> attribute. See § +configuration level environment variable provider in the <em>configurationEnvironmentSupplier</em> attribute. See § 7.6 for additional information.<br> </p> <p class="MsoNormal" style="margin-top:6.0pt">A tool-chain may define a configuration -level macro provider in the <i>configurationMacroSupplier</i> attribute. See § +level macro provider in the <em>configurationMacroSupplier</em> attribute. See § 7.8 for additional information.<br> </p> <p class="MsoNormal" style="margin-top:6.0pt">A tool-chain may be associated @@ -1329,8 +1329,8 @@ the schema table below.</p> superClass</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">The unique identifier of the toolChain that this toolChain - is derived from.</font></td> + The unique identifier of the toolChain that this toolChain + is derived from.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -1341,11 +1341,11 @@ the schema table below.</p> isAbstract</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">Flags the toolChain as abstract. An abstract toolChain + Flags the toolChain as abstract. An abstract toolChain must be defined as a top level object in the model definition and cannot be selected by the user in the UI, but tool-chains derived from this tool-chain will inherit its attributes and children. The default value - is false.</font></td> + is false.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -1356,10 +1356,10 @@ the schema table below.</p> targetTool</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <span style="font-family: Arial"><font size="2">A semi-colon separated + <span style="font-family: Arial">A semi-colon separated list of the identifiers of the tools that can be used to create the build artifact. A list is required, for example, when there are 2 - versions of a target tool that are used with different project natures.</font></span></td> + versions of a target tool that are used with different project natures.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -1371,11 +1371,11 @@ the schema table below.</p> secondaryOutputs</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <span style="font-family: Arial"><font size="2">A semi-colon separated + <span style="font-family: Arial">A semi-colon separated list of the identifiers of other output types, besides the primary output of the targetTool, that are also considered to be build artifacts. The build file generator will ensure that the outputs - get built.</font></span></td> + get built.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -1387,15 +1387,15 @@ the schema table below.</p> osList</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva"> + <span class="typewriter"><span style="font-size: 10.0pt"> The comma separated list of operating systems that the tool-chain is supported on. The - valid list of</font></span></tt><font size="2"> operating system</font><tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva">s - is the string values returned by Platform.getOS().</font></span></tt><font size="2"><br> - I</font><tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva">f + valid list of</span></span> operating system<span class="typewriter"><span style="font-size: 10.0pt">s + is the string values returned by Platform.getOS().</span></span><br> + I<span class="typewriter"><span style="font-size: 10.0pt">f the osList attribute is not specified, or if the value is "all", then the tool-chain is supported on all operating systems. Otherwise, the tool-chain is only displayed when CDT is running on one of the specified - operating systems, unless the user has turned off filtering.</font></span></tt></td> + operating systems, unless the user has turned off filtering.</span></span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -1409,20 +1409,20 @@ the schema table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva"> + <span class="typewriter"><span style="font-size: 10.0pt"> The comma separated list of architectures that the tool-chain is supported on. The - valid list of</font></span></tt><font size="2"> </font><tt> - <span style="font-size: 10.0pt"><font face="arial, helvetica, geneva"> - architectures is the string values returned by Platform.getOSArch().</font></span></tt><font size="2"><br> - </font><tt><span style="font-size: 10.0pt"> - <font face="arial, helvetica, geneva">If the archList attribute is not + valid list of</span></span> <span class="typewriter"> + <span style="font-size: 10.0pt"> + architectures is the string values returned by Platform.getOSArch().</span></span><br> + <span class="typewriter"><span style="font-size: 10.0pt"> + If the archList attribute is not specified, or if the value is "all", then the tool-chain is supported on all architectures. Otherwise, the tool-chain is only displayed when CDT is running on one of the specified architectures, unless the user has - turned off filtering.</font></span></tt></td> + turned off filtering.</span></span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" - valign="top"> + valign="top"> no</td> </tr> <tr> @@ -1431,13 +1431,13 @@ the schema table below.</p> valign="top">errorParsers</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" - valign="top"><font size="2">The semi-colon separated list of the default error + valign="top">The semi-colon separated list of the default error parsers to be used with this tool-chain. The list is ordered with the first error parser on the list invoked first, the second error parser second, and so on. The list may contain the error parsers defined by CDT and/or other installed error parser extensions. When specified, this overrides the tool errorParsers attributes of the tool children of - the tool-chain and the builder child of the tool-chain.</font></td> + the tool-chain and the builder child of the tool-chain.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top">no</td> @@ -1486,8 +1486,8 @@ the schema table below.</p> method to be called to determine if support for the tool-chain is currently installed on the system. MBS uses this information in order to filter the choices presented to the CDT user and to inform the - user when support needed by their project is not installed. If the <i> - isToolChainSupported </i>callback is not provided by the tool-chain + user when support needed by their project is not installed. If the <em> + isToolChainSupported </em>callback is not provided by the tool-chain definition, the tool-chain is treated as supported. If all configurations defined for the given project type are not supported the project type is treated as unsupported.</td> @@ -1575,9 +1575,9 @@ the schema table below.</p> <p class="subsection"><a name="_TocSectionGrammar_6">3.6 Builder</a></p> <p class="MsoNormal" style="margin-top:6.0pt">The builder element represents the utility that drives the build process (typically, but not necessarily, a variant -of “make”). It defines the command needed to invoke the build utility in the <i> -command</i> attribute. Any special flags that need to be passed to the builder -are defined in the <i>arguments</i> attribute. The builder can specify the +of “make”). It defines the command needed to invoke the build utility in the <em> +command</em> attribute. Any special flags that need to be passed to the builder +are defined in the <em>arguments</em> attribute. The builder can specify the error parser(s) to be used to parse its output. The builder also specifies a Java class that generates the build file. MBS provides built-in gnu makefile generation.</p> @@ -1585,7 +1585,7 @@ generation.</p> build macros and how they interact with the build file generator. </p> <p class="MsoNormal">The builder can specify the template of how to convert a build macro that contains an environment variable into the build file -environment variable format by specifying the <i>variableFormat</i> attribute. +environment variable format by specifying the <em>variableFormat</em> attribute. </p> <p class="MsoNormal">The builder can specify the builder internal (reserved) macro names and the macro names reserved by a build file generator (used to @@ -1593,24 +1593,24 @@ store the list of objects files, input files, etc.). This information will be used by the build file generator in the case where the build environment variable macros are not to be expanded in the build file. If an environment variable build macro name conflicts with the name of some reserved macro, it -always gets resolved in the build file. See the <i>reservedMacroNames</i> and <i> -reservedMacroNameSupplier</i> attributes below.</p> +always gets resolved in the build file. See the <em>reservedMacroNames</em> and <em> +reservedMacroNameSupplier</em> attributes below.</p> <p class="MsoNormal">The builder can provide the values for the file-context -build macros. To provide the value for the macro ${<macro_name>}, the <i> -macro<macro_name>Value</i> attribute should be specified. The value of this +build macros. To provide the value for the macro ${<macro_name>}, the <em> +macro<macro_name>Value</em> attribute should be specified. The value of this attribute should be set to the value of the given macro. MBS will resolve the value of unsupported file-context macros to their actual macro value. In this case, a separate rule for each file will be generated when file-specific macros are used. See the gnu tool-chain for an example of setting these attributes for gnu make.</p> <p class="MsoNormal" style="margin-top:6.0pt">MBS supports multiple versions of -a builder. The <i>versionsSupported</i><b> </b>attribute contains a list +a builder. The <em>versionsSupported</em><strong> </strong>attribute contains a list of supported versions of a particular builder. This indicates that there is no need to perform a conversion when user imports/loads a project with one of the supported builder versions. When a tool integrator decides to no longer support a version of a builder, they continue to ship the old builder definition and -specify the id with version number of the new builder to convert to in the <i> -convertToId</i> attribute. If changes to the project information need to be +specify the id with version number of the new builder to convert to in the <em> +convertToId</em> attribute. If changes to the project information need to be performed by the conversion, the tool chain definition must provide a converter extension to perform the conversion. If no converter extension is provided, then there won’t be any conversion. See § 8.2 for additional information.</p> @@ -1636,87 +1636,87 @@ the schema table below.</p> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">id</font></td> + id</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">A unique identifier that the model manager will use to keep -track of this specific builder.</font></td> + A unique identifier that the model manager will use to keep +track of this specific builder.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">yes</font></td> + yes</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">name</font></td> + name</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">Human-readable name for the builder to be used in the UI.</font></td> + Human-readable name for the builder to be used in the UI.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">superClass</font></td> + superClass</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2" face="Arial">The unique identifier of the builder that this builder is - derived from.</font></td> + The unique identifier of the builder that this builder is + derived from.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">isAbstract</font></td> + isAbstract</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2" face="Arial">Flags the builder as abstract. An abstract builder must be + Flags the builder as abstract. An abstract builder must be defined as a top level object in the model definition and cannot be selected by the user in the UI, but builders derived from this builder - will inherit its attributes and children. The default value is false.</font></td> + will inherit its attributes and children. The default value is false.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">command</font></td> + command</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">Specifies the default command to start the build + Specifies the default command to start the build utility for your toolchain. If the user changes this through the UI, the overriden value will be stored in the project build file. The build model will default to this value if the user ever resets a change. - The default is "make".</font></td> + The default is "make".</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">arguments</font></td> + arguments</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2" face="Arial">Specifies the additional, default arguments + Specifies the additional, default arguments that will be passed to the build utility when it is called by the builder. If the user changes the flags through the UI, the overriden value will be stored in the project build settings file. The build model will default to this value if the user ever resets a change. The default - is “-k”.</font></td> + is “-k”.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font face="Arial">errorParsers</font></td> + errorParsers</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> Specifies the default list of error parsers used by the builder. These @@ -1727,32 +1727,32 @@ track of this specific builder.</font></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">buildfileGenerator</font></td> + buildfileGenerator</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font size="2" face="Arial">The name of a class that implements IManagedBuilderMakefileGenerator. </font> + The name of a class that implements IManagedBuilderMakefileGenerator. See § 7.2 for additional information.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">variableFormat</font></td> + variableFormat</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <p class="MsoNormal"><font face="Arial">The value of this attribute should + <p class="MsoNormal">The value of this attribute should be set to the expression representing the variable format. For example, to generate macros with the ${macro} format, the attribute would contain ${=}. To generate macros with the @macro format, the attribute would @@ -1762,107 +1762,107 @@ track of this specific builder.</font></td> contain environment variables are resolved by MBS to their actual value. The user can also specify that build macros that contain environment variables be resolved to their actual value, as explained - earlier.</font></td> + earlier.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial"><span style="background-color: #FFFF00">i</span>sVariableCase - Sensitive</font></td> + <span style="background-color: #FFFF00">i</span>sVariableCase + Sensitive</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">Specifies whether the + <span style="font-family: Arial">Specifies whether the builder variables are case sensitive or not. Can be set to either “true” or “false”. The default is “true”. If the builder does not support case-sensitive variables and there are some build environment variables that differ only in case (Environment variables on Unix-like operating systems are case sensitive), then those macros will always get resolved - in the buildfile.</font></span></td> + in the buildfile.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">reservedMacro - Names</font></td> + reservedMacro + Names</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <p class="MsoNormal"><font face="Arial">Comma-separated list of reserved + <p class="MsoNormal">Comma-separated list of reserved macro names. The macro name could contain either the exact name or the java regular expression. The latter could be used to supply the pattern of variable names that are generated by MBS in case the “buildVariable” attribute of the “InputType” element is not specified, etc. If this attribute is specified and the reservedMacroNameSupplier is not - specified, the following macro names will be treated as reserved:</font></p> + specified, the following macro names will be treated as reserved:</p> <p class="MsoNormal" style="text-indent: -.25in; margin-left: .25in"> - <font face="Arial">1.</font><span style="font-style: normal; font-variant: normal; font-weight: normal; font-family: Arial"><font size="2"> </font></span><font face="Arial">a + 1.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-family: Arial"> </span>a macro name that is equal to one of the names specified in the - reservedMacroNames value</font></p> + reservedMacroNames value</p> <p class="MsoNormal" style="text-indent: -.25in; margin-left: .25in"> - <font face="Arial">2.</font><span style="font-style: normal; font-variant: normal; font-weight: normal; font-family: Arial"><font size="2"> </font></span><font face="Arial">a + 2.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-family: Arial"> </span>a macro name that matches one of the regexp patterns specified in the - reservedMacroNames value</font></p> + reservedMacroNames value</p> <p class="MsoNormal" style="text-indent: -.25in; margin-left: .25in"> - <font face="Arial">3.</font><span style="font-style: normal; font-variant: normal; font-weight: normal; font-family: Arial"><font size="2"> </font></span><font face="Arial">a + 3.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-family: Arial"> </span>a macro name that is equal to one of the build variable names specified - InputType elements of the tools used in the tool-chain</font></p> - <span style="font-family: Arial"><font size="2">If this attribute is not + InputType elements of the tools used in the tool-chain</p> + <span style="font-family: Arial">If this attribute is not specified, MBS will assume that there are no reserved macro names that could conflict with the build environment variable macros, except names specified in the “buildVariable” attribute of the “InputType” elements: - these names will always be treated as reserved.</font></span></td> + these names will always be treated as reserved.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">reservedMacro - NameSupplier</font></td> + reservedMacro + NameSupplier</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <p class="MsoNormal"><font face="Arial">Should be set to the name of the + <p class="MsoNormal">Should be set to the name of the class that implements the IReservedMacroNameSupplier interface. If this attribute is specified the reservedMacroNames attribute is ignored, and - the following macro names will be treated as reserved:</font></p> + the following macro names will be treated as reserved:</p> <p class="MsoNormal" style="text-indent: -.25in; margin-left: .25in"> - <font face="Arial">1.</font><span style="font-style: normal; font-variant: normal; font-weight: normal; font-family: Arial"><font size="2"> </font></span><font face="Arial">macro - names that the IReservedMacroNamesSupplier specifies as reserved</font></p> + 1.<span style="font-style: normal; font-variant: normal; font-weight: normal; font-family: Arial"> </span>macro + names that the IReservedMacroNamesSupplier specifies as reserved</p> <p style="text-indent: -0.25in; margin-left: 0.25in"> - <span style="font-family: Arial"><font size="2">2. a macro + <span style="font-family: Arial">2. a macro name that is equal to one of the build variable names specified - InputType elements in the tools used in the tool-chain. </font> + InputType elements in the tools used in the tool-chain. </span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">macroInputFile - NameValue</font></td> + macroInputFile + NameValue</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">Represents the InputFileName macro value. The macro + Represents the InputFileName macro value. The macro specifies the input file name. The input file has the following meaning:<br> 1. If a tool does not accept building multiple files of the primary input type with one tool invocation, the input file is the file of the @@ -1870,94 +1870,94 @@ track of this specific builder.</font></td> 2. If a tool accepts building multiple files of the primary input type with one tool invocation the input file is undefined and the macros representing the input file contain information about one of the inputs - of the primary input type being built.</font></td> + of the primary input type being built.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">macroInputFile - ExtValue</font></td> + macroInputFile + ExtValue</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">Represents the InputFileExt macro value. The macro - specifies the extension of the input file.</font></td> + Represents the InputFileExt macro value. The macro + specifies the extension of the input file.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">macroInputFile - BaseNameValue</font></td> + macroInputFile + BaseNameValue</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">Represents the InputFileBaseName macro value. The macro + Represents the InputFileBaseName macro value. The macro specifies the base name of the input file. That is the file name with an - extension stripped.</font></td> + extension stripped.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">macroInputFile - RelPathValue</font></td> + macroInputFile + RelPathValue</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">Represents the InputFileRelPath macro value. The macro - specifies the input file path relative to the builder current directory.</font></td> + Represents the InputFileRelPath macro value. The macro + specifies the input file path relative to the builder current directory.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">macroInputDir - RelPathValue</font></td> + macroInputDir + RelPathValue</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">Represents the InputDirRelPath macro value. The macro + Represents the InputDirRelPath macro value. The macro specifies the input file directory path relative to the builder current - directory.</font></td> + directory.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td style="border-style: none solid solid double; border-width: medium 1pt 1pt 1.5pt; border-left: 1.5pt double windowtext; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">macroInputDir - RelPathValue</font></td> + macroInputDir + RelPathValue</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">Represents the InputDirRelPath macro value. The macro + Represents the InputDirRelPath macro value. The macro specifies the input file directory path relative to the builder current - directory.</font></td> + directory.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font face="Arial">no</font></td> + no</td> </tr> <tr> <td @@ -2079,12 +2079,12 @@ track of this specific builder.</font></td> </table> <p class="subsection"><a name="_TocSectionGrammar_7">3.7 Target Platform</a></p> <p class="MsoNormal">The targetPlatform element represents the os/architecture -combination(s) upon which the output of a tool-chain can be deployed. The <i> -osList </i>and <i>archList</i> attributes contain the Eclipse names of the +combination(s) upon which the output of a tool-chain can be deployed. The <em> +osList </em>and <em>archList</em> attributes contain the Eclipse names of the operating systems and architectures described by this element. </p> <p class="MsoNormal" style="margin-top:6.0pt">CDT offers a facility for parsing binary files if it knows which output format the build artifact has been -produced with. The <i>binaryParser</i> attribute must contain the id of the +produced with. The <em>binaryParser</em> attribute must contain the id of the appropriate parser if you want build artifacts of the tool-chain to be parsed in the workspace.</p> <p class="subsection">3.7.1 Schema</p> @@ -2133,8 +2133,8 @@ the workspace.</p> superClass</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">The unique identifier of the targetPlatform that this - targetPlatform is derived from.</font></td> + The unique identifier of the targetPlatform that this + targetPlatform is derived from.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -2145,11 +2145,11 @@ the workspace.</p> isAbstract</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">Flags the targetPlatform as abstract. An abstract + Flags the targetPlatform as abstract. An abstract targetPlatform must be defined as a top level object in the model definition and can not be selected by the user in the UI, but target platforms derived from this target platform will inherit its attributes - and children. The default value is false.</font></td> + and children. The default value is false.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -2160,12 +2160,12 @@ the workspace.</p> osList</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva"> + <span class="typewriter"><span style="font-size: 10.0pt"> The list of operating systems that is valid for this target platform. - The valid list of</font></span></tt><font size="2"> operating system</font><tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva">s - is the string values returned by Platform.getOS(). </font></span></tt><font size="2">I</font><tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva">f + The valid list of</span></span> operating system<span class="typewriter"><span style="font-size: 10.0pt">s + is the string values returned by Platform.getOS(). </span></span>I<span class="typewriter"><span style="font-size: 10.0pt">f the osList attribute is not specified, or if the value is "all", then - the target platform supports all operating systems.</font></span></tt></td> + the target platform supports all operating systems.</span></span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2179,12 +2179,12 @@ the workspace.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva"> + <span class="typewriter"><span style="font-size: 10.0pt"> The list of architectures that is valid for this target platform. The - valid list of</font></span></tt><font size="2"> architecture</font><tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva">s - is the string values returned by Platform.getOSArch(). </font></span></tt><font size="2">I</font><tt><span style="font-size: 10.0pt"><font face="arial, helvetica, geneva">f + valid list of</span></span> architecture<span class="typewriter"><span style="font-size: 10.0pt">s + is the string values returned by Platform.getOSArch(). </span></span>I<span class="typewriter"><span style="font-size: 10.0pt">f the archList attribute is not specified, or if the value is "all", then - the target platform supports all architectures.</font></span></tt></td> + the target platform supports all architectures.</span></span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2196,8 +2196,8 @@ the workspace.</p> valign="top">binaryParser</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" - valign="top">Semi-colon separated list of the<font size="2"> ids of the appropriate parser(s) for the build - artifact</font></td> + valign="top">Semi-colon separated list of the ids of the appropriate parser(s) for the build + artifact</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top">no</td> @@ -2207,7 +2207,7 @@ the workspace.</p> <p class="subsection"><a name="_TocSectionGrammar_8">3.8 Tool</a></p> <p class="MsoNormal" style="margin-top:6.0pt">The tool element represents the tool in the user model. <span style="color:red"> </span>A tool must have a -unique <i>id</i> for the build model, and a <i>name</i> that is displayed to a +unique <em>id</em> for the build model, and a <em>name</em> that is displayed to a user through the UI. A tool can be defined as part of a tool-chain, or as an independent specification.</p> <p class="MsoNormal" style="margin-top:6.0pt">A tool may contain one or more @@ -2227,29 +2227,29 @@ library paths.</p> <p class="MsoNormal" style="margin-top:6.0pt">Certain tools logically belong to certain kinds of projects. For example, the Gnu compiler is invoked differently for C and C++ source files. You can specify a filter for a tool based on the -nature of a project using the <i>natureFilter</i> attribute. When a new C +nature of a project using the <em>natureFilter</em> attribute. When a new C project is created, a “cnature” is added to it. New C++ projects have both a “cnature” and “ccnature”. The build model interprets the filter as follows. If you specify a ‘cnature’ filter, then the tool will only be displayed if the -project has a “cnature” and does <i>not</i> have a “ccnature”. If you specify a +project has a “cnature” and does <em>not</em> have a “ccnature”. If you specify a ‘ccnature’ filter, then the tool will be displayed if the project has a “ccnature”. The default if no filter is specified is to display the tool for all projects.</p> -<p class="MsoNormal" style="margin-top:6.0pt">Each tool specifies a <i>command</i> +<p class="MsoNormal" style="margin-top:6.0pt">Each tool specifies a <em>command</em> that will be placed in the build file during the build file generation stage of building. If the tool requires a special output flag, such as ‘-o’ for a compiler or linker, the -implementer must specify that in the <i>outputFlag</i> attribute.</p> -<p class="MsoNormal" style="margin-top:6.0pt">The <i>commandLineGenerator</i> +implementer must specify that in the <em>outputFlag</em> attribute.</p> +<p class="MsoNormal" style="margin-top:6.0pt">The <em>commandLineGenerator</em> attribute allows the implementer to specify a class that implements the <code>IManagedCommandLineGenerator</code> interface. An explanation of how to replace the default command line generator can be found in § 7.4. </p> <p class="MsoNormal" style="margin-top:6.0pt">MBS supports multiple versions of -a tool. The <i>versionsSupported</i><b> </b>attribute contains a list of +a tool. The <em>versionsSupported</em><strong> </strong>attribute contains a list of supported versions of a particular tool. This indicates that there is no need to perform a conversion when user imports/loads a project with one of the supported tool versions. When a tool integrator decides to no longer support a version of a tool, they continue to ship the old tool definition and specify the id with -version number of the tool to convert to in the <i>convertToId</i> attribute. +version number of the tool to convert to in the <em>convertToId</em> attribute. If changes to the project information need to be performed by the conversion, the tool chain must provide a converter extension to perform the conversion. If no converter extension is provided, then there won’t be any conversion. @@ -2318,8 +2318,8 @@ build model.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font size="2">The unique identifier of the tool that this tool is derived - from.</font></td> + The unique identifier of the tool that this tool is derived + from.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2333,10 +2333,10 @@ build model.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font size="2">Flags the tool as abstract. An abstract tool must be + Flags the tool as abstract. An abstract tool must be defined as a top level object in the model definition and can not be selected by the user in the UI, but tools derived from this tool will - inherit its attributes and children. The default value is false.</font></td> + inherit its attributes and children. The default value is false.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2469,7 +2469,7 @@ Gnu C compiler, or g++ for the Gnu C++ compiler.</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font size="2">Specifies a command “pattern” that indicates how the parts + Specifies a command “pattern” that indicates how the parts of the command line are used to create the entire command line. The pattern consists of the replaceable variables COMMAND, FLAGS, OUTPUT_FLAG, OUTPUT_PREFIX, OUTPUT and INPUTS. The default command line @@ -2477,7 +2477,7 @@ Gnu C compiler, or g++ for the Gnu C++ compiler.</td> ${COMMAND} ${FLAGS} ${OUTPUT_FLAG}${OUTPUT_PREFIX}${OUTPUT} ${INPUTS}, except when customBuildStep is true, where the default is $(COMMAND). White space and other characters are significant and are copied to the - generated command.</font></td> + generated command.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2491,13 +2491,13 @@ Gnu C compiler, or g++ for the Gnu C++ compiler.</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">When True, indicates that + <span style="font-family: Arial">When True, indicates that the Tool represents a CDT end-user-defined custom build step. The default is False. When True, the default value of the commandLinePattern attribute changes to “$(command)”. This attribute is used by the implementation of Custom Build Steps on the MBS configuration property page. It is not intended for use by tools defined by a - tool-integrator.</font></span></td> + tool-integrator.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2511,12 +2511,12 @@ Gnu C compiler, or g++ for the Gnu C++ compiler.</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <font size="2">Contains a semi-colon separated, ordered, list of error + Contains a semi-colon separated, ordered, list of error parser ids. MBS adds the error parser(s) to the end of the toolChain error parser list, if not already present, when a project resource is defined to use the tool. The error parser(s) can be removed by the CDT user, and is automatically removed when there are no more project - resources that use the tool.</font></td> + resources that use the tool.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2727,8 +2727,8 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">A unique identifier that - the MBS will use to track this element.</font></span></td> + <span style="font-family: Arial">A unique identifier that + the MBS will use to track this element.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2742,8 +2742,8 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top" height="19"> - <span style="font-family: Arial"><font size="2">The name of the input type - that is displayed to the user in the UI.</font></span></td> + <span style="font-family: Arial">The name of the input type + that is displayed to the user in the UI.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top" height="19"> @@ -2757,8 +2757,8 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">The unique identifier of - the inputType that this inputType is derived from.</font></span></td> + <span style="font-family: Arial">The unique identifier of + the inputType that this inputType is derived from.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2772,10 +2772,10 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">The id of an Eclipse + <span style="font-family: Arial">The id of an Eclipse content type that describes this input type. If both the sources attribute and the sourceContentType attribute are specified, the - sourceContentType will be used if it is defined in Eclipse.</font></span></td> + sourceContentType will be used if it is defined in Eclipse.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2789,10 +2789,10 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">A comma-separated list of + <span style="font-family: Arial">A comma-separated list of file extensions that the tool will produce output for. Note that the user will not be able to modify the set of file extensions as they can - when sourceContentType is specified.</font></span></td> + when sourceContentType is specified.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2806,11 +2806,11 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">The id of an Eclipse + <span style="font-family: Arial">The id of an Eclipse content type used for dependency files. If both the dependencyExtensions attribute and the dependencyContentType attribute are specified, the dependencyContentType will be used if it is defined - in Eclipse.</font></span></td> + in Eclipse.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2824,10 +2824,10 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">A comma-separated list of + <span style="font-family: Arial">A comma-separated list of file extensions used by dependency files. Note that the user will not be able to modify the set of file extensions as they can when - dependencyContentType is specified.</font></span></td> + dependencyContentType is specified.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2876,10 +2876,10 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">True if all of the inputs + <span style="font-family: Arial">True if all of the inputs of this category are used in one invocation of the tool. The inputs can be project resources, or the outputs of other tools in the tool-chain. - The default is False.</font></span></td> + The default is False.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2893,8 +2893,8 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">True is this is considered - the primary input of the tool. The default is False.</font></span></td> + <span style="font-family: Arial">True is this is considered + the primary input of the tool. The default is False.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2908,10 +2908,10 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">The name of a class that + <span style="font-family: Arial">The name of a class that provides the source file dependency calculation for the input type. The class implements the IManagedDependencyGenerator2 interface. The default - is none.</font></span></td> + is none.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2925,13 +2925,13 @@ attributes of the InputType element are described in the table below.</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">A variable used in the + <span style="font-family: Arial">A variable used in the build file to represent the list of input files. The same variable name can be used by an outputType to identify a set of output files that contribute to this tool’s input (i.e., those using the same buildVariable name). A build variable is ignored when multipleOfType is false and this is the primary input of the tool. The default name is - chosen by MBS.</font></span></td> + chosen by MBS.</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -2970,12 +2970,12 @@ specified by the user (or tool integrator).</p> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> - <span style="font-family: Arial"><font size="2">Defines a semi-colon + <span style="font-family: Arial">Defines a semi-colon separated list of the relative or absolute path of the resource(s) to which this element applies. The resource(s) must be a member of the project, the output from another tool in the tool-chain, or an external file. The file name of a path can use GNU Make pattern rule syntax (in - order to generate the name from the output file name).</font></span></td> + order to generate the name from the output file name).</span></td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> @@ -3005,7 +3005,7 @@ specified by the user (or tool integrator).</p> <span style="font-size:10.0pt;font-family:Arial"> AdditionalInputDependency – added as both.</span></li> </ul> - <span style="font-family: Arial"><font size="2">The default is </font> + <span style="font-family: Arial">The default is </span><span style="font-size: 10.0pt; font-family: Arial"> AdditionalInputDependency.</span></td> <td @@ -3032,22 +3032,22 @@ file(s) generated from this OutputType. This is necessary in order for MBS to generate correct build files, and to allow for input ordering. The precedence order for determining the output resource names is the following:</p> <ol style="margin-top: 0in; margin-bottom: 0in" start="1" type="1"> - <li class="MsoNormal" style="margin-top: 6.0pt"><font face="Arial" size="2"> + <li style="margin-top: 6.0pt"> If this is the “target” tool in the tool-chain, and this is the primary - OutputType, use the user-defined artifact name and extension.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"><font face="Arial" size="2"> - If the <i>option</i> attribute is specified, use the value of the option.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"><font face="Arial" size="2"> - If the <i>nameProvider </i>attribute is specified, call the nameProvider and use - the returned name(s).</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"><font face="Arial" size="2"> - If the <i>outputNames </i>attribute is specified, use the value of the attribute.</font></li> - <li class="MsoNormal" style="margin-top: 6.0pt"><font face="Arial" size="2"> - Use the <i>namePattern</i> attribute value to construct the name from the input - file name.</font></li> + OutputType, use the user-defined artifact name and extension.</li> + <li style="margin-top: 6.0pt"> + If the <em>option</em> attribute is specified, use the value of the option.</li> + <li style="margin-top: 6.0pt"> + If the <em>nameProvider </em>attribute is specified, call the nameProvider and use + the returned name(s).</li> + <li style="margin-top: 6.0pt"> + If the <em>outputNames </em>attribute is specified, use the value of the attribute.</li> + <li style="margin-top: 6.0pt"> + Use the <em>namePattern</em> attribute value to construct the name from the input + file name.</li> </ol> <p> If the output of the tool usually has a special prefix, like the prefix -‘lib’ for libraries on POSIX systems, the implementer must specify this in the <i>outputPrefix</i> +‘lib’ for libraries on POSIX systems, the implementer must specify this in the <em>outputPrefix</em> attribute.</p> <p class="subsection">3.11.1 Schema</p> <table @@ -3295,8 +3295,8 @@ attribute.</p> </tbody> </table> <p class="subsection"><a name="_TocSectionGrammar_12">3.12 Option Category</a></p> -<p><font size="2">The optionCategory element represents the option category in -the user model. A tool </font>can have a large number of options. To help organize the user +<p>The optionCategory element represents the option category in +the user model. A tool can have a large number of options. To help organize the user interface for these options, a hierarchical set of option categories can be defined. A unique identifier must be specified in the <var>id</var> @@ -3401,12 +3401,12 @@ Options'. This will be the name the user sees displayed in the UI.</p> <p class="MsoNormal">The option element represents the option in the user model. Options are used to organize and maintain the command arguments that are sent to tools during the build. Users interact with the build model through the UI to -set the value of options. Each option must have a unique <i>id</i> for the -build model to properly manage it. A descriptive <i>name</i> that will appear in +set the value of options. Each option must have a unique <em>id</em> for the +build model to properly manage it. A descriptive <em>name</em> that will appear in the UI must be specified. Options can be organized into categories to keep the UI more manageable. If an option category has been defined for the tool, and the option should be displayed as part of that category, then the unique identifier -of the option category must be specified in the <i>category</i> attribute.</p> +of the option category must be specified in the <em>category</em> attribute.</p> <p class="subsection">3.13.1 Option Types</p> <p>Some options contain commands to turn a feature off or on, such as setting a flag to see descriptive messages from a tool. Others contain @@ -3434,7 +3434,7 @@ in respectively.</p> commands that take a user-defined value. The UI representation for a string option is a text box.</p> <p class="subsection">3.12.1.2 Boolean Options</p> -<p><font size="2">Boolean options are</font> used to specify an option that is +<p>Boolean options are used to specify an option that is either true or false. The UI representation for a boolean option is a check box. The value of the option is set true by selecting the check box, and false by deselecting it. If true, the <var>command</var> @@ -3485,21 +3485,21 @@ is ignored for all other option types.<br> <p class="subsection">3.13.2 Values and Default Values</p> <p class="MsoNormal" style="margin-top:6.0pt">An option can define a default value that applies to the option until a value has been specified. An option -defines its default value using the <i>defaultValue</i> attribute. When an +defines its default value using the <em>defaultValue</em> attribute. When an option has a value that has been specifically set, the value is contained in the -<i>value</i> attribute. In order to determine the current value of an option, +<em>value</em> attribute. In order to determine the current value of an option, MBS performs the following steps until a value is found:</p> <ol> - <li><font face="arial, helvetica, geneva" size="2">Examine the <i>value</i> - attribute of the option.</font></li> - <li><font face="arial, helvetica, geneva" size="2">Examine the <i>value</i> - attribute of the option’s <i>superClass </i>recursively.</font></li> - <li><font face="arial, helvetica, geneva" size="2">Examine the <i> - defaultValue</i> attribute of the option.</font></li> - <li><font face="arial, helvetica, geneva" size="2">Examine the <i> - defaultValue</i> attribute of the option’s <i>superClass recursively</i>.</font></li> - <li><font face="arial, helvetica, geneva" size="2">Use the default value for - the option type.</font></li> + <li>Examine the <em>value</em> + attribute of the option.</li> + <li>Examine the <em>value</em> + attribute of the option’s <em>superClass </em>recursively.</li> + <li>Examine the <em> + defaultValue</em> attribute of the option.</li> + <li>Examine the <em> + defaultValue</em> attribute of the option’s <em>superClass recursively</em>.</li> + <li>Use the default value for + the option type.</li> </ol> <p class="MsoNormal" style="margin-top:6.0pt">The type of option will determine how the build model treats the value it finds associated with the attribute. @@ -3512,18 +3512,18 @@ enumerated options search through the defined enumerated values for the default. are passed to build tools with unique flags, depending on the compiler and the option. For example, an option defining the paths a linker should search for libraries might contain a large number of search paths, but each path is passed -to the linker with a ‘-L’ flag. The <i>command</i> attribute is used to hold the +to the linker with a ‘-L’ flag. The <em>command</em> attribute is used to hold the actual flag to pass along with the option value. </p> <p class="MsoNormal" style="margin-top:6.0pt">The build model handles the value it finds associated with the command attribute differently depending on the type of value the option is managing based on the following heuristic. For string -options the option value is appended to the value of the <i>command </i> -attribute. The <i>command </i>attribute can be empty in order to support an area -for typing in additional options. For enumerated options, the <i>command</i> +options the option value is appended to the value of the <em>command </em> +attribute. The <em>command </em>attribute can be empty in order to support an area +for typing in additional options. For enumerated options, the <em>command</em> associated with the selected enumerated value is used, not the command defined -in the option. For boolean options, the <i>command</i> is used if the option -value is set to true, otherwise the value of the <i>commandFalse</i> attribute -is used. For list options, the <i>command</i> is applied to each element of the +in the option. For boolean options, the <em>command</em> is used if the option +value is set to true, otherwise the value of the <em>commandFalse</em> attribute +is used. For list options, the <em>command</em> is applied to each element of the list.</p> <table style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> @@ -3697,8 +3697,8 @@ build model.</p> superClass</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">The unique identifier of the option that this option is - derived from.</font></td> + The unique identifier of the option that this option is + derived from.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -3709,10 +3709,10 @@ build model.</p> isAbstract</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">Flags the option as abstract. An abstract option must be + Flags the option as abstract. An abstract option must be defined as a top level object in the model definition and can not be selected by the user in the UI, but options derived from this option - will inherit its attributes and children. The default value is false.</font></td> + will inherit its attributes and children. The default value is false.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -3760,8 +3760,8 @@ can be the id of the tool which is also a category. The default category value</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;" height="18"> - <font size="2">Value assigned to the option by the end user or in a - default configuration. </font>For options containing a Boolean + Value assigned to the option by the end user or in a + default configuration. For options containing a Boolean value, the string ‘true’ is treated as true, any other value as false.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;" height="18"> @@ -3795,12 +3795,12 @@ not edited it. For options containing a Boolean value, the string style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top"> <p>An optional value that specifies the actual command that will -be passed to the tool on the command line. <font size="2">The command +be passed to the tool on the command line. The command provides a “pattern” for specifying where the value should be placed for options of type string and stringlist. The pattern can contain the replaceable variable “value”. If no ${value} is specified in the command, the option value is appended to the end of the specified - command.</font></p> + command.</p> </td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" @@ -3842,11 +3842,11 @@ needed.</td> valign="top">resourceFilter</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" - valign="top"><font size="2">Specifies the resource types that this option + valign="top">Specifies the resource types that this option applies to. The values are “project”, “file”, and “all”. The default is “all”. Specifying “project” indicates that the option is displayed when modifying a configuration’s options, but not when modifying an - individual file’s options. Specifying “file” indicates the opposite.</font></td> + individual file’s options. Specifying “file” indicates the opposite.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt;" valign="top">no</td> @@ -4122,8 +4122,8 @@ attributes are specified in the schema table below.</p> resourcePath</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">The path of the project resource to which this - resourceConfiguration applies.</font></td> + The path of the project resource to which this + resourceConfiguration applies.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> yes</td> @@ -4134,10 +4134,10 @@ attributes are specified in the schema table below.</p> exclude</td> <td style="border-style: none solid solid none; border-width: medium 1pt 1pt medium; border-right: 1pt solid windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> - <font size="2">Specifies whether the resource is excluded from building in + Specifies whether the resource is excluded from building in the parent configuration. The default value is false. The resourceConfiguration element retains its tool children, if any - exist, even when excluded from the build.</font></td> + exist, even when excluded from the build.</td> <td style="border-style: none double solid none; border-width: medium 1.5pt 1pt medium; border-right: 1.5pt double windowtext; border-bottom: 1pt solid windowtext; padding: 0in 5.4pt; vertical-align: top;"> no</td> @@ -4256,7 +4256,7 @@ attributes are specified in the schema table below.</p> <p class="MsoNormal">The name of a class that implements the IBuildPathResolver interface that the tool-integrator can supply in order to provide his/her own logic of resolving the variable values to the build paths</p> - <p class="MsoNormal"><b>Design note:</b> the reason why this callback is + <p class="MsoNormal"><strong>Design note:</strong> the reason why this callback is needed is because some tools may store the build paths in some special way or in the format other than <path1><delimiter><path2><delimiter>…<pathN>. The example of such a tool is gcc for Win32 Cygwin. The cygwin @@ -4800,7 +4800,7 @@ to expand it. Click on the expansion icon beside META-INF, and then double click the <span style="font-weight: 700">MANIFEST.MF</span> file to edit its contents.</li> <li>We have to add a dependency between our project and the <code>org.eclipse.cdt.managedbuilder.core</code> -plug-in where the extension point is defined. Click on the <b>Dependencies</b> +plug-in where the extension point is defined. Click on the <strong>Dependencies</strong> tab located along the bottom of the manifest editor. Click the <span style="font-weight: bold;">Add…</span> button located beside the <span style="font-weight: bold;">Required Plug-Ins</span> @@ -4845,7 +4845,7 @@ property in the <span style="font-weight: bold;">Extension Element Details</span> column. For now, let’s use the name <code>Example Executable</code> for our projectType.</li> <li>Make sure that the values of <span style="font-weight: bold;">isTest</span> - and<b> isAbstract</b> are<b> </b>set + and<strong> isAbstract</strong> are<strong> </strong>set to false.<br> </li> </ol> @@ -4881,8 +4881,8 @@ following list <code>org.eclipse.cdt.core.MakeErrorParser;org.eclipse.cdt.core.G org.eclipse.cdt.core.VCErrorParser</code></li> </ol> <p style="font-weight: normal;" class="subsection"> -<b> -<a name="_TocSectionTutorial_6">6.6 Adding a ToolChain</a></b></p> +<strong> +<a name="_TocSectionTutorial_6">6.6 Adding a ToolChain</a></strong></p> <p style="font-weight: normal;"> Each configuration requires a toolChain child that defines the set of tools used by the configuration.</p> @@ -4908,8 +4908,8 @@ you are running on a version of Solaris, or <code>other</code> if none of the above apply.</li> </ol> <p style="font-weight: normal;" class="subsection"> -<b> -<a name="_TocSectionTutorial_7">6.7 Adding a Builder</a></b></p> +<strong> +<a name="_TocSectionTutorial_7">6.7 Adding a Builder</a></strong></p> <p style="font-weight: normal;"> Each toolChain can have a builder child that describes the build utility used by the tool-chain to create the build artifacts of the configuration.</p> @@ -4946,8 +4946,8 @@ property and to be <code>Example Target Platform </code> and the valu style="font-weight: bold;">id</span> to be <code> example.toolchain.targetplatform</code>.</li></a></a> <li>Our target platform is the same as our host platform. Enter the - same value for the <b>osList</b> property as entered for the ToolChain <b> - osList</b>.</li> + same value for the <strong>osList</strong> property as entered for the ToolChain <strong> + osList</strong>.</li> <li>Set the value of the binary parser property based on the platform you will be using to create your example projects on. For example, if you @@ -4955,8 +4955,8 @@ are running this tutorial on Linux or Solaris, enter the value <code>org.eclipse If you are running the tutorial on Windows, enter the value <code>org.eclipse.cdt.core.PE</code>.</li> </ol> <p style="font-weight: normal;" class="subsection"> -<b> -<a name="_TocSectionTutorial_9">6.9 Adding a Tool</a></b></p> +<strong> +<a name="_TocSectionTutorial_9">6.9 Adding a Tool</a></strong></p> <p style="font-weight: normal;"> Each toolChain describes the set of tools used by the build utility to create the build artifacts of the configuration.</p> @@ -4981,41 +4981,41 @@ property.</li> </ol> <a name="_TocSectionTutorial_18"> <p style="font-weight: normal;" class="subsection"> -<b> -<a name="_TocSectionTutorial_10">6.10 Adding Input and Output Types</a></b></p> +<strong> +<a name="_TocSectionTutorial_10">6.10 Adding Input and Output Types</a></strong></p> <p style="font-weight: normal;"> Each tool describes its inputs and outputs in InputType and OutputType elements. </p> <ol> <li> - <p style="font-weight: normal;">Right click on <b>Compiler</b> to get the - context menu and select <b>New > inputType</b>. Name the inputType - <font face="Courier New">Compiler Input</font><font face="Arial"> and make - its<b> id </b></font><font face="Courier New"> - example.toolchain.compiler.input.</font></p></li> + <p style="font-weight: normal;">Right click on <strong>Compiler</strong> to get the + context menu and select <strong>New > inputType</strong>. Name the inputType + <span style="font-family:Courier New">Compiler Input</span> and make + its<strong> id </strong><span style="font-family:Courier New"> + example.toolchain.compiler.input.</span></p></li> <li> <p style="font-weight: normal;">Our imaginary compiler only works on c source files. Locate the <span style="font-weight: bold;">sourceContentType</span> property and set it to - <font face="Courier New">org.eclipse.cdt.core.cSource</font>.</p></li> + <span style="font-family:Courier New">org.eclipse.cdt.core.cSource.</span></p></li> <li> <p style="font-weight: normal;">The build model needs to know if there are any special file extensions that indicate a file is a ‘header’ file. Set the <span style="font-weight: 700">dependencyContentType</span> -property to be <code>org.eclipse.cdt.core.cHeader </code><font face="Arial"> - <code><font face="Arial">and the <span style="font-weight: 700"> - dependencyCalculator </span>property to be </font></code></font><code> - <font face="Courier New"> - org.eclipse.cdt.managedbuilder.makegen.internal.DefaultIndexerDependencyCalculator</font></code>. +property to be <code>org.eclipse.cdt.core.cHeader </code> + <code>and the <span style="font-weight: 700"> + dependencyCalculator </span>property to be </code><code> + <span style="font-family:Courier New"> + org.eclipse.cdt.managedbuilder.makegen.internal.DefaultIndexerDependencyCalculator</span></code>. </p></li> <li> - <p style="font-weight: normal;">Set the <b>primaryInput</b> property to - <font face="Courier New">true.</font></p></li> + <p style="font-weight: normal;">Set the <strong>primaryInput</strong> property to + <span style="font-family:Courier New">true.</span></p></li> <li> - <p style="font-weight: normal;">Right click on <b>Compiler</b> to get the - context menu and select <b>New > outputType</b>. Name the outputType - <font face="Courier New">Compiler Output</font><font face="Arial"> and make - its<b> id </b></font><font face="Courier New"> - example.toolchain.compiler.output.</font></p></li> + <p style="font-weight: normal;">Right click on <strong>Compiler</strong> to get the + context menu and select <strong>New > outputType</strong>. Name the outputType + <span style="font-family:Courier New">Compiler Output</span> and make + its<strong> id </strong><span style="font-family:Courier New"> + example.toolchain.compiler.output.</span></p></li> <li> <p style="font-weight: normal;">Let us assume that the output of the compiler is an object module that has the @@ -5025,14 +5025,14 @@ tool to <code>o</code>.</p></li> <li> <p style="font-weight: normal;">The object modules created by your compiler are typically used as a group by another tool, for example a linker or - archiver. Set the <b>buildVariable</b> property to be - <font face="Courier New">OBJS. </font><font face="Arial">You would use the + archiver. Set the <strong>buildVariable</strong> property to be + <span style="font-family:Courier New">OBJS.</span> You would use the same name as the <span style="font-weight: 700">buildVariable </span>with - the inputType of this other tool</font><font face="Courier New">.</font></p> + the inputType of this other tool.</p> </li> <li> - <p style="font-weight: normal;">Set the <b>primaryOutput</b> property to - <font face="Courier New">true.</font></p></li> + <p style="font-weight: normal;">Set the <strong>primaryOutput</strong> property to + <span style="font-family:Courier New">true.</span></p></li> </ol> <p class="subsection"> <a name="_TocSectionTutorial_11">6.11 Testing the ProjectType</a></p> @@ -5073,8 +5073,8 @@ Projects</span> view to access the context menu, and select <span style="font-weight: bold;">Properties</span> to open the property browser for the project. Select <span style="font-weight: bold;">C/C++ Build</span> -from the choices, select the <b>Tool Settings</b> tab, and note that the tool we defined appears in the list.</li> - <li>Select the <b>Build Settings</b> tab. The user can change the +from the choices, select the <strong>Tool Settings</strong> tab, and note that the tool we defined appears in the list.</li> + <li>Select the <strong>Build Settings</strong> tab. The user can change the build output name and the build command from here, and the MBS will manage that selection between sessions.</li> <li>Select the <span style="font-weight: bold;">Error Parsers</span> @@ -5148,12 +5148,12 @@ the category that you entered in step 4.</li> compiler (remember, you add the option to the tool and set its category via the <span style="font-weight: bold;">category</span> property). Set the <span style="font-weight: bold;">name</span> of the option to <code>Other -flags</code>, its <b>id</b> to <code>example.toolchain.compiler.general.otherflags</code>, its <span style="font-weight: bold;">valueType</span> +flags</code>, its <strong>id</strong> to <code>example.toolchain.compiler.general.otherflags</code>, its <span style="font-weight: bold;">valueType</span> to <code>string</code>, and its <span style="font-weight: bold;">defaultValue</span> to <code>-c</code>.</li> <li>Add a check-box option to the 'General' category of the compiler. Name it <code>Error messages, </code> - set the<b> id</b> to <code>example.toolchain.compiler.general.errmsgs,</code> and set its - <b>valueType</b> to <code>boolean</code>. + set the<strong> id</strong> to <code>example.toolchain.compiler.general.errmsgs,</code> and set its + <strong>valueType</strong> to <code>boolean</code>. This is a boolean option, so it might have a command associated with the selected and unselected states. In this case we want to turn on reporting when it is selected, and turn it off when it is deselected. @@ -5202,7 +5202,7 @@ the preprocessor symbols defined for the project. </p> <p>MBS gathers information about the defined symbols and include paths from a number of sources:</p> -<p><b>User-defined symbols and include paths: </b>You can flag certain +<p><strong>User-defined symbols and include paths: </strong>You can flag certain tool options as special so the build model will know to pay special attention to them. As the implementer of the tool integration, you should make sure your @@ -5210,16 +5210,16 @@ specification has options of type “includePaths” and “definedS The build model will pay special attention to these options and provide them to the appropriate clients in the CDT core without any further intervention on your part.</p> -<p><b>Pre-defined symbols and include paths: </b>A toolChain may specify +<p><strong>Pre-defined symbols and include paths: </strong>A toolChain may specify the id of scanner configuration discovery profile for gathering the built-in compiler settings. See the org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile extension point description in the reference documentation for more information. If a collector is specified, MBS invokes it to return the pre-defined symbols and include paths. If a collector is not specified, MBS searches for -options of type “includePaths” and “definedSymbols” with the <b>builtIn</b> +options of type “includePaths” and “definedSymbols” with the <strong>builtIn</strong> attribute set to true.</p> -<p><b>Environment include paths: </b>Your build definition may specify a -envVarBuildPath element with the <b>pathType</b> attribute set to "buildpathInclude". +<p><strong>Environment include paths: </strong>Your build definition may specify a +envVarBuildPath element with the <strong>pathType</strong> attribute set to "buildpathInclude". If specified, MBS will read the environment variable(s) for additional include paths. See § 3.17 for additional information regarding the envVarBuildPath element.</p> @@ -5268,8 +5268,8 @@ not difficult. You must supply the plugin manifest we created inside the Eclipse platform's plug-in directory. The plug-in directory is named plugins and is typically located underneath the main directory where you installed the Eclipse -platform.<b> -</b></p> +platform.<strong> +</strong></p> <ol> <li style="font-weight: normal;">From the <span style="font-weight: bold;">Plug-in @@ -5282,9 +5282,9 @@ page, chose <span style="font-weight: bold;">Deployable Plugins and Fragments</s the export destination list. Click the <span style="font-weight: bold;">Next ></span> button. </li> - <li style="font-weight: normal;">In the <b>Deployable Plugins and Fragments</b> - dialog, Export<font face="Arial"> </font> <code><font face="Arial"> - Destination section, select Directory and </font></code><font face="Arial">click the</font> Browse... button. + <li style="font-weight: normal;">In the <strong>Deployable Plugins and Fragments</strong> + dialog, Export <code> + Destination section, select Directory and </code>click the Browse... button. Browse to your Eclipse installation. Deselect all Export Options. Click the Finish button.</li> <li>Restart Eclipse, switch to the <span style="font-weight: bold;">C/C++ @@ -5366,34 +5366,34 @@ dependencyCalculator attribute. Typically, dependency calculators are only relevant for a "compiler" tool, but what tool you use to specify the generator (or generators) is arbitrary.</p> <p>By design, a dependency calculator must answer what type of -dependency generation it will do. <font face="Arial">There are two major, +dependency generation it will do. There are two major, and multiple minor, modes of dependency calculation supported by the MBS. -The major modes are:</font></p> +The major modes are:</p> <ol> - <li><font face="Arial">The build file generator invokes tool integrator + <li>The build file generator invokes tool integrator provided methods that calculate all dependencies using whatever method the tool integrator wants. The build file generator then adds the dependencies to the build file using the appropriate build file syntax. This is a TYPE_CUSTOM dependency calculator as defined below. See the - </font><font face="Courier New">IManagedDependencyCalculator</font><font face="Arial"> - interface discussion below for more information. </font></li> - <li><font face="Arial">The build file generator and the tool-chain cooperate + <span style="font-family:Courier New">IManagedDependencyCalculator </span> + interface discussion below for more information. </li> + <li>The build file generator and the tool-chain cooperate in creating and using separate "dependency" files. In this case, dependency calculation is done at "build time", rather than at "build file generation time" as in mode #1. This currently supports the GNU concept of using .d files in GNU make. This is either a TYPE_BUILD_COMMANDS dependency calculator or a TYPE_PREBUILD_COMMANDS - dependency calculator as defined below. See the </font> - <font face="Courier New">IManagedDependencyCommands</font><font face="Arial"> - and </font><font face="Courier New">IManagedDependencyPreBuild</font><font face="Arial"> - interfaces discussion below for more information.</font></li> + dependency calculator as defined below. See the + <span style="font-family:Courier New">IManagedDependencyCommands </span> + and <span style="font-family:Courier New">IManagedDependencyPreBuild </span> + interfaces discussion below for more information.</li> </ol> -<p><font face="Courier New">public interface IManagedDependencyGeneratorType {<br> -<font color="#336699"> /**<br> +<p><span style="font-family:Courier New">public interface IManagedDependencyGeneratorType {<br> +<span style="color:#336699"> /**<br> * Constants returned by getCalculatorType<br> */<br> -</font> public int TYPE_NODEPS = 0; // Deprecated - use +</span> public int TYPE_NODEPS = 0; // Deprecated - use TYPE_NODEPENDENCIES<br> public int TYPE_COMMAND = 1; // Deprecated - use @@ -5405,8 +5405,8 @@ TYPE_BUILD_COMMANDS<br> public int TYPE_OLD_TYPE_LIMIT = 3;<br> <br> - <font color="#336699">// Use these types<br> - </font> + <span style="color:#336699">// Use these types<br> + </span> public int TYPE_NODEPENDENCIES = 4;<br> public int TYPE_BUILD_COMMANDS = 5;<br> @@ -5415,7 +5415,7 @@ TYPE_BUILD_COMMANDS<br> public int TYPE_CUSTOM = 7;<br> <br> -<font color="#336699"> /**<br> +<span style="color:#336699"> /**<br> * Returns the type of dependency generator that is implemented. <br> * <br> @@ -5463,25 +5463,25 @@ dependency files need to be re-generated.<br> * @return int<br> */<br> -</font> public int getCalculatorType();<br> -}</font></p> -<p><font face="Arial">After deciding upon the type of dependency calculator, you -must implement the methods in<code><font face="Arial"> </font> </code></font><code>IManagedDependencyGenerator2</code><font face="Arial"><code><font face="Arial">. -The method </font></code></font><font face="Courier New">getDependencySourceInfo</font><font face="Arial"> -returns an instance of the </font><font face="Courier New"> -IManagedDependencyInfo</font><font face="Arial"> interface. This can be -any one of the 3 interfaces that derive from </font><font face="Courier New"> -IManagedDependencyInfo</font><font face="Arial"> - </font> -<font color="#336699" face="Courier New">I</font><font face="Courier New">ManagedDependencyCalculator, -IManagedDependencyCommands</font><font face="Arial"> or </font> -<font face="Courier New">IManagedDependencyPreBuild </font><font face="Arial"> +</span> public int getCalculatorType();<br> +}</span></p> +<p>After deciding upon the type of dependency calculator, you +must implement the methods in<code> </code><code>IManagedDependencyGenerator2</code>. +The method <span style="font-family:Courier New">getDependencySourceInfo </span> +returns an instance of the <span style="font-family:Courier New"> +IManagedDependencyInfo</span> interface. This can be +any one of the 3 interfaces that derive from <span style="font-family:Courier New"> +IManagedDependencyInfo</span> - +<span style="font-family:Courier New">I</span><span style="font-family:Courier New">ManagedDependencyCalculator, +IManagedDependencyCommands </span>or +<span style="font-family:Courier New">IManagedDependencyPreBuild </span> which are discussed below. The returned interface is called to get the dependency information for a particular source file in the configuration. -See the descriptions of the other methods in<code><font face="Arial"> </font> </code></font><code>IManagedDependencyGenerator2</code><font face="Arial"> -in the code comments below.</font></p> +See the descriptions of the other methods in<code> </code><code>IManagedDependencyGenerator2</code> +in the code comments below.</p> <pre>public interface IManagedDependencyGenerator2 extends IManagedDependencyGeneratorType { -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns an instance of IManagedDependencyInfo for this source file. * IManagedDependencyCalculator, IManagedDependencyCommands * and IManagedDependencyPreBuild are all derived from @@ -5498,13 +5498,13 @@ in the code comments below.</font></p> * the working directory for the tool. This IPath is relative to the project directory. * @return IManagedDependencyInfo */ -</font> public IManagedDependencyInfo getDependencySourceInfo( +</span> public IManagedDependencyInfo getDependencySourceInfo( IPath source, IBuildObject buildContext, ITool tool, IPath topBuildDirectory); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the file extension used by dependency files created * by this dependency generator. * This is called when getCalculatorType returns TYPE_BUILD_COMMANDS or @@ -5515,11 +5515,11 @@ in the code comments below.</font></p> * * @return String */ -</font> public String getDependencyFileExtension( +</span> public String getDependencyFileExtension( IConfiguration buildContext, ITool tool); -<font color="#336699"> /** +<span style="color:#336699"> /** * Called to allow the dependency calculator to post-process dependency files. * This method is called after the build has completed for at least every * dependency file that has changed, and possibly for those that have not @@ -5539,20 +5539,20 @@ in the code comments below.</font></p> * * @return boolean True if the method modified the dependency (e.g., .d) file */ -</font> public boolean postProcessDependencyFile( +</span> public boolean postProcessDependencyFile( IPath dependencyFile, IConfiguration buildContext, ITool tool, IPath topBuildDirectory); }</pre> -<p class="subsection"><font face="Arial">7.3.1 TYPE_CUSTOM dependency calculator -</font></p> -<p><font face="Arial">A TYPE_CUSTOM dependency calculator must implement the -</font><font face="Courier New">IManagedDependencyCalculator</font><font face="Arial"> -interface.</font></p> +<p class="subsection">7.3.1 TYPE_CUSTOM dependency calculator +</p> +<p>A TYPE_CUSTOM dependency calculator must implement the +<span style="font-family:Courier New">IManagedDependencyCalculator </span> +interface.</p> <pre>public interface IManagedDependencyCalculator extends IManagedDependencyInfo { -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the list of source file specific dependencies. * * The paths can be either relative to the project directory, or absolute @@ -5560,9 +5560,9 @@ interface.</font></p> * * @return IPath[] */ -</font> public IPath[] getDependencies(); +</span> public IPath[] getDependencies(); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the list of source file specific additional targets that the * source file creates. Most source files will return null. An example * of where additional targets should be returned is for a Fortran 90 @@ -5578,7 +5578,7 @@ interface.</font></p> * * @return IPath[] */ -</font> public IPath[] getAdditionalTargets(); +</span> public IPath[] getAdditionalTargets(); }</pre> <p>An example TYPE_CUSTOM dependency calculator can be found in the MBS test suite - org.eclipse.cdt.managedbuilder.core.tests\DefaultFortranDependencyCalculator.</p> @@ -5592,76 +5592,76 @@ to complete its work before it will answer, so your build may take longer to complete. See the org.eclipse.cdt.managedbuilder.makegen.internal\DefaultIndexerDependencyCalculator class for an example of how this was implemented using the old, deprecated -<font face="Courier">IManagedDependencyGenerator</font><font face="Arial"> +<span style="font-family:Courier New">IManagedDependencyGenerator </span> interface. However, it doesn't seem as if it worked with CDT 3.0. Readers are encouraged to update this method to the new interfaces and -contribute the implementation to CDT.</font></p> -<p class="subsection"><font face="Arial">7.3.2 TYPE_BUILD_COMMANDS dependency -calculator </font></p> +contribute the implementation to CDT.</p> +<p class="subsection">7.3.2 TYPE_BUILD_COMMANDS dependency +calculator </p> When using a TYPE_BUILD_COMMANDS dependency calculator, the build file generator and the tool-chain cooperate in creating and using separate "dependency" files. The build file generator calls the dependency calculator to get the dependency file names and to get commands that need to be added to the build file. In this case, dependency calculation is done at "build time", rather than at "build file generation time" as with TYPE_CUSTOM. This currently supports the GNU concept of using .d files in GNU make.<p> -<font face="Arial">There are multiple ways that these separate dependency files can +There are multiple ways that these separate dependency files can be created by the tool-chain and used by the builder. In some cases (e.g., Fortran 90 using modules) the dependency files must be created/updated prior to invoking the build of the project artifact (e.g., an application). In this case, the dependency generation step must occur separately before the main build. See -</font>TYPE_PREBUILD_COMMANDS<font face="Arial"> for more information. In other cases (e.g., C/C++) the dependency files can be created as +TYPE_PREBUILD_COMMANDS for more information. In other cases (e.g., C/C++) the dependency files can be created as a side effect of the main build. This implies that the up to date dependency files are not required for the current build, but for the next build. C/C++ builds can be treated in this manner as is described in the following link: - <a href="http://sourceware.org/automake/automake.html#Dependency-Tracking-Evolution">http://sourceware.org/automake/automake.html#Dependency-Tracking-Evolution</a>. Use the IManagedDependencyCommands interface for this mode.</font></p> -<p><font face="Arial">Two sub-scenarios of this mode are to: - </font></p> + <a href="http://sourceware.org/automake/automake.html#Dependency-Tracking-Evolution">http://sourceware.org/automake/automake.html#Dependency-Tracking-Evolution</a>. Use the IManagedDependencyCommands interface for this mode.</p> +<p>Two sub-scenarios of this mode are to: + </p> <ol> - <li><font face="Arial">Create dependency files in the same invocation of the tool that + <li>Create dependency files in the same invocation of the tool that creates the tool's build artifact - by adding additional options - to the tool invocation command line.</font></li> - <li><font face="Arial">Create dependency files in a separate invocation of the tool, or - by the invocation of another tool</font></li> + to the tool invocation command line.</li> + <li>Create dependency files in a separate invocation of the tool, or + by the invocation of another tool</li> </ol> -<p><font face="Arial">MBS can also help in the generation of the dependency files. Prior to +<p>MBS can also help in the generation of the dependency files. Prior to CDT 3.1, MBS and gcc cooperated in generating dependency files using the - following steps:</font></p> + following steps:</p> <ol> - <li><font face="Arial">Gcc is invoked to perform the compilation that generates the object - file.</font></li> - <li><font face="Arial">An "echo" command creates the .d file, adding the name of the .d + <li>Gcc is invoked to perform the compilation that generates the object + file.</li> + <li>An "echo" command creates the .d file, adding the name of the .d file to the beginning of the newly created .d file. Note that this causes problems with some implementations of "echo" that don't work exactly the way that we want (e.g., it doesn't support the -n - switch).</font></li> - <li><font face="Arial">Gcc is invoked again with the appropriate additional command line + switch).</li> + <li>Gcc is invoked again with the appropriate additional command line options to append its dependency file information to the .d file - that was created by "echo".</font></li> - <li><font face="Arial">Steps 1 - 3 are invoked in the make file. Step 4 occurs after the + that was created by "echo".</li> + <li>Steps 1 - 3 are invoked in the make file. Step 4 occurs after the make invocation has finished. In step 4, MBS code post-processes the .d files to add a dummy dependency for each header file, for - the reason explained in the link above.</font></li> + the reason explained in the link above.</li> </ol> -<p><font face="Arial">This mode is no longer used by the default gcc implementation, but can - still be used by selecting the DefaultGCCDependencyCalculator3Commands class.</font></p> -<p><font face="Arial">Note for GNU make: these separate dependency files are "include"d by +<p>This mode is no longer used by the default gcc implementation, but can + still be used by selecting the DefaultGCCDependencyCalculator3Commands class.</p> +<p>Note for GNU make: these separate dependency files are "include"d by a main makefile. Therefore, if the dependency files are required to be up to date before the main build begins, they must be updated by a separate invocation of make. Also, the configuration "clean" step must be invoked by a separate invocation of make. This is so that we can exclude the dependency files for a "make clean" invocation - using syntax like:</font></p> -<p style="margin-bottom: 0"><font face="Arial">ifneq ($(MAKECMDGOALS), clean)</font></p> -<p style="margin-top: 0; margin-bottom: 0"><font face="Arial">-include $(DEPS)</font></p> -<p style="margin-top: 0; margin-bottom: 0"><font face="Arial">endif - </font></p> -<p><font face="Arial">Otherwise, because GNU make attempts to re-make make files, we + using syntax like:</p> +<p style="margin-bottom: 0">ifneq ($(MAKECMDGOALS), clean)</p> +<p style="margin-top: 0; margin-bottom: 0">-include $(DEPS)</p> +<p style="margin-top: 0; margin-bottom: 0">endif + </p> +<p>Otherwise, because GNU make attempts to re-make make files, we can end up with out of date or missing dependency files being - re-generated and then immediately "clean"ed.</font></p> -<p><font face="Arial">Examples of the use of </font>TYPE_BUILD_COMMANDS -<font face="Arial">can be found in org.eclipse.cdt.managedbuilder.makegen.gnu\DefaultGCCDependencyCalculator2Commands -and DefaultGCCDependencyCalculator3Commands.</font></p> + re-generated and then immediately "clean"ed.</p> +<p>Examples of the use of TYPE_BUILD_COMMANDS +can be found in org.eclipse.cdt.managedbuilder.makegen.gnu\DefaultGCCDependencyCalculator2Commands +and DefaultGCCDependencyCalculator3Commands.</p> <pre>public interface IManagedDependencyCommands extends IManagedDependencyInfo { -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the list of generated dependency files. * * The paths can be either relative to the top build directory, or absolute @@ -5669,9 +5669,9 @@ and DefaultGCCDependencyCalculator3Commands.</font></p> * * @return IPath[] */ -</font> public IPath[] getDependencyFiles(); +</span> public IPath[] getDependencyFiles(); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the command lines to be invoked before the normal tool invocation * to calculate dependencies. * @@ -5679,9 +5679,9 @@ and DefaultGCCDependencyCalculator3Commands.</font></p> * generation command needs to be invoked before the normal * tool invocation. */ -</font> public String[] getPreToolDependencyCommands(); +</span> public String[] getPreToolDependencyCommands(); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the command line options to be used to calculate dependencies. * The options are added to the normal tool invocation. * @@ -5689,9 +5689,9 @@ and DefaultGCCDependencyCalculator3Commands.</font></p> * arguments need to be added to the tool invocation. * SHOULD THIS RETURN AN IOption[]? */ -</font> public String[] getDependencyCommandOptions(); +</span> public String[] getDependencyCommandOptions(); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the command lines to be invoked after the normal tool invocation * to calculate dependencies. * @@ -5699,9 +5699,9 @@ and DefaultGCCDependencyCalculator3Commands.</font></p> * generation commands needs to be invoked after the normal * tool invocation */ -</font> public String[] getPostToolDependencyCommands(); +</span> public String[] getPostToolDependencyCommands(); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns true if the command lines and/or options returned by this interface * are not specific to the particular source file, but are only specific to, * at most, the configuration and tool. If the build context is a resource @@ -5712,10 +5712,10 @@ and DefaultGCCDependencyCalculator3Commands.</font></p> * * @return boolean */ -</font> public boolean areCommandsGeneric(); +</span> public boolean areCommandsGeneric(); }</pre> -<p class="subsection"><font face="Arial">7.3.3 TYPE_PREBUILD_COMMANDS dependency -calculator </font></p> +<p class="subsection">7.3.3 TYPE_PREBUILD_COMMANDS dependency +calculator </p> When using a TYPE_BUILD_PRECOMMANDS dependency calculator, the build file generator and the tool-chain cooperate in creating and using separate "dependency" files. For GNU make, these separate dependency files are "include"d by a main makefile. Make performs special processing on make files:<br> @@ -5740,10 +5740,10 @@ include $(DEPS)<br> endif<br> <p>The restriction with this is that it only works if "clean" is the only target specified on the make command line. Therefore, the build "clean" step must be -invoked separately.<p><font face="Arial">Examples of the use of </font>TYPE_PREBUILD_COMMANDS -<font face="Arial">can be found in org.eclipse.cdt.managedbuilder.makegen.gnu\DefaultGCCDependencyCalculatorPreBuildCommands.</font><pre>public interface IManagedDependencyPreBuild extends IManagedDependencyInfo { - -<font color="#336699"> /** +invoked separately.<p>Examples of the use of TYPE_PREBUILD_COMMANDS +can be found in org.eclipse.cdt.managedbuilder.makegen.gnu\DefaultGCCDependencyCalculatorPreBuildCommands.<pre>public interface IManagedDependencyPreBuild extends IManagedDependencyInfo { + +<span style="color:#336699"> /** * Returns the list of generated dependency files. * * The paths can be either relative to the top build directory, or absolute @@ -5751,9 +5751,9 @@ invoked separately.<p><font face="Arial">Examples of the use of </font>TYPE_PREB * * @return IPath[] */ -</font> public IPath[] getDependencyFiles(); +</span> public IPath[] getDependencyFiles(); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the name to be used in the build file to identify the separate * build step. Note that this name should be unique to the tool since * multiple tools in a tool-chain may be using this method of @@ -5761,17 +5761,17 @@ invoked separately.<p><font face="Arial">Examples of the use of </font>TYPE_PREB * * @return String */ -</font> public String getBuildStepName(); +</span> public String getBuildStepName(); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns the command line(s) to be invoked in the separate * dependencies pre-build step. * * @return String[] */ -</font> public String[] getDependencyCommands(); +</span> public String[] getDependencyCommands(); -<font color="#336699"> /** +<span style="color:#336699"> /** * Returns true if the command lines returned by this interface * are not specific to the particular source file, but are only specific to, * at most, the configuration and tool. If the build context is a resource @@ -5782,7 +5782,7 @@ invoked separately.<p><font face="Arial">Examples of the use of </font>TYPE_PREB * * @return boolean */ -</font> public boolean areCommandsGeneric(); +</span> public boolean areCommandsGeneric(); }</pre> <p class="subsection"><a name="_TocSectionDynamic_4">7.4 Replacing the Command Line Generator</a></p> <p>You can specify a replacement command line generator for a tool. You must specify and supply a class @@ -5849,7 +5849,7 @@ getInputResources();</span></p> <p class="MsoNormal" style="text-autospace: none">MBS calls IManagedCommandLineGenerator.generateCommandLineInfo to generate the command line information. The supplied IManagedCommandLineGenerator could modify the command line parts if necessary and then provide the modified values, as well as -the complete command line, in the <font face="Courier New">IManagedCommandLineInfo</font> interface. The +the complete command line, in the <span style="font-family:Courier New">IManagedCommandLineInfo</span> interface. The default MBS implementation does not modify any of the command line parts. It uses the parts and the pattern to generate the complete command line that can be retrieved using IManagedCommandLineInfo.getCommandLine.</p> @@ -5864,17 +5864,17 @@ given project type are not supported the project type is treated as unsupported. <p>In order to provide this functionality, the “isToolChainSupported” attribute in the toolChain definition must be specified. The value of this attribute should be set to the -name of the class which implements the <font face="Courier New">I</font><span style="font-family: Courier New"><font size="2">ManagedIsToolChainSupported</font></span> +name of the class which implements the <span style="font-family:Courier New">IManagedIsToolChainSupported</span> interface.</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">public interface -IManagedIsToolChainSupported{</font></p> +<span style="font-family:Courier New">public interface +IManagedIsToolChainSupported{</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> boolean +<span style="font-family:Courier New"> boolean isSupported(IToolChain toolChain, PluginVersionIdentifier version, String -instance);</font></p> +instance);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">}</font></p> +<span style="font-family:Courier New">}</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0">The version argument specifies the version of the ToolChain, or null if the ToolChain does @@ -5894,815 +5894,815 @@ Configuration-level environment variable suppliers separately: </p> <p class="MsoNormal" style="margin-left: 0in">To provide a Configuration-level supplier the “configurationEnvironmentSupplier” attribute in the toolChain definition must be specified. The value of this attribute should be set to the -name of the class which implements the <font face="Courier New">IConfigurationEnvironmentVariableSupplier</font> +name of the class which implements the <span style="font-family:Courier New">IConfigurationEnvironmentVariableSupplier </span> interface </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">public interface -IConfigurationEnvironmentVariableSupplier{</font></p> +<span style="font-family:Courier New">public interface +IConfigurationEnvironmentVariableSupplier{</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> *</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> *</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @variableName the variable mane</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @variableName the variable mane</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @param configuration configuration</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @param configuration configuration</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @param provider the instance of the -environment variable provider to be used for querying the</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @param provider the instance of the +environment variable provider to be used for querying the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * environment variables from within -the supplier. The supplier should use this provider to obtain</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * environment variables from within +the supplier. The supplier should use this provider to obtain</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * the already defined environment instead of using -the “default” provider returned by the</span></font></p> +the “default” provider returned by the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * -ManagedBuildManager.getEnvironmentVariableProvider().</span></font></p> +ManagedBuildManager.getEnvironmentVariableProvider().</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> * </font> -<font face="Courier New"><span style="color: #003366">The provider passed to a supplier will ignore -searching the variables for the levels </span></font></p> +<span style="font-family:Courier New; color:#003366"> * </span> +<span style="font-family:Courier New"><span style="color: #003366">The provider passed to a supplier will ignore +searching the variables for the levels </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * higher than the current supplier level, will -query only the lower-precedence suppliers </span></font></p> +query only the lower-precedence suppliers </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span> <span style="font-family:Courier New"> <span style="color: #003366"> * for the current level and will query all -suppliers for the lower levels. </span></font></p> +suppliers for the lower levels. </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span> <span style="font-family:Courier New"> <span style="color: #003366"> * This is done to avoid infinite loops that could -be caused if the supplier calls the provider </span></font></p> +be caused if the supplier calls the provider </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span> <span style="font-family:Courier New"> <span style="color: #003366"> * and the provider in turn calls that supplier -again. Also the supplier should not know anything </span></font></p> +again. Also the supplier should not know anything </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span> <span style="font-family:Courier New"> <span style="color: #003366"> * about the environment variables defined for the -higher levels.</span></font></p> +higher levels.</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @return the reference to the IBuildEnvironmentVariable interface representing </span> -</font></p> +</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> -<span style="color: #003366"> * the variable of a given name</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> +<span style="color: #003366"> * the variable of a given name</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> IBuildEnvironmentVariable getVariable(String variableName, -</font> </p> +<span style="font-family:Courier New"> IBuildEnvironmentVariable getVariable(String variableName, +</span> </p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 2.95in; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IConfiguration configuration,</font></p> +<span style="font-family:Courier New">IConfiguration configuration,</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 2.95in; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IEnvironmentVariableProvider provider);</font></p> +<span style="font-family:Courier New">IEnvironmentVariableProvider provider);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @param configuration configuration</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @param configuration configuration</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @param provider the instance of the -environment variable provider to be used for querying the</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @param provider the instance of the +environment variable provider to be used for querying the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * environment variables from within -the supplier. The supplier should use this provider to obtain</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * environment variables from within +the supplier. The supplier should use this provider to obtain</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> *</font><font face="Courier New"><span style="color: #003366"> the already defined environment instead of using -the “default” provider returned by the</span></font></p> +<span style="font-family:Courier New; color:#003366"> *</span><span style="font-family:Courier New"><span style="color: #003366"> the already defined environment instead of using +the “default” provider returned by the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* -ManagedBuildManager.getEnvironmentVariableProvider().</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* +ManagedBuildManager.getEnvironmentVariableProvider().</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * The provider passed to a supplier will ignore -searching the variables for the levels </span></font></p> +searching the variables for the levels </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * higher than the current supplier level, will -query only the lower-precedence suppliers </span></font></p> +query only the lower-precedence suppliers </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * for the current level and will query all -suppliers for the lower levels. </span></font></p> +suppliers for the lower levels. </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * This is done to avoid infinite loops that could -be caused if the supplier calls the provider </span></font></p> +be caused if the supplier calls the provider </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * and the provider in turn calls that supplier -again. Also the supplier should not know anything</span></font></p> +again. Also the supplier should not know anything</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * about the environment variables defined for the -higher levels.</span></font></p> +higher levels.</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @return the array of IBuildEnvironmentVariable that represents the environment variables</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @return the array of IBuildEnvironmentVariable that represents the environment variables</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> IBuildEnvironmentVariable[] getVariables (IConfiguration configuration,</font></p> +<span style="font-family:Courier New"> IBuildEnvironmentVariable[] getVariables (IConfiguration configuration,</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 2.95in; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IEnvironmentVariableProvider provider);</font></p> +<span style="font-family:Courier New">IEnvironmentVariableProvider provider);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">}</font></p> +<span style="font-family:Courier New">}</span></p> <p class="MsoNormal" style="margin-left: 0in">To provide a Project-level supplier the “projectEnvironmentSupplier” attribute in the projectType definition must be specified. The value of this attribute should be set to the -name of the class which implements the <font face="Courier New">IProjectEnvironmentVariableSupplier</font> +name of the class which implements the <span style="font-family:Courier New">IProjectEnvironmentVariableSupplier interface.</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">public interface -IProjectEnvironmentVariableSupplier{</font></p> +<span style="font-family:Courier New">public interface +IProjectEnvironmentVariableSupplier{</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @variableName the variable mane</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @variableName the variable mane</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @param project the managed project</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @param project the managed project</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @param provider the instance of the -environment variable provider to be used for querying the</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @param provider the instance of the +environment variable provider to be used for querying the</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * environment variables from within -the supplier. The supplier should use this provider to obtain</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * environment variables from within +the supplier. The supplier should use this provider to obtain</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* the already defined environment instead of using -the “default” provider returned by the</span></font></p> +<span style="font-family:Courier New; color:#003366"> +<span style="font-family:Courier New"><span style="color: #003366">* the already defined environment instead of using +the “default” provider returned by the</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* -ManagedBuildManager.getEnvironmentVariableProvider().</span></font></p> +<span style="font-family:Courier New; color:#003366"> +<span style="font-family:Courier New"><span style="color: #003366">* +ManagedBuildManager.getEnvironmentVariableProvider().</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * The provider passed to a supplier will ignore -searching the variables for the levels </span></font></p> +searching the variables for the levels </span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * higher than the current supplier level, will -query only the lower-precedence suppliers </span></font></p> +query only the lower-precedence suppliers </span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * for the current level and will query all -suppliers for the lower levels. </span></font></p> +suppliers for the lower levels. </span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * This is done to avoid infinite loops that could -be caused if the supplier calls the provider </span></font></p> +be caused if the supplier calls the provider </span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * and the provider in turn calls that supplier -again. Also the supplier should not know anything</span></font></p> +again. Also the supplier should not know anything</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * about the environment variables defined for the -higher levels.</span></font></p> +higher levels.</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @return the reference to the IBuildEnvironmentVariable interface representing </span> -</font></p> +</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> -<span style="color: #003366"> * the variable of a given name</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> +<span style="color: #003366"> * the variable of a given name</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> IBuildEnvironmentVariable getVariable(String variableName, -</font> </p> +<span style="font-family:Courier New"> IBuildEnvironmentVariable getVariable(String variableName, + </p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 177.0pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IManagedProject project,</font></p> +<span style="font-family:Courier New">IManagedProject project,</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 177.0pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IEnvironmentVariableProvider provider);</font></p> +<span style="font-family:Courier New">IEnvironmentVariableProvider provider);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> *</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> *</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> * @param project the managed project</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> * @param project the managed project</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @param provider the instance of the -environment variable provider to be used for querying the</span></font></p> +environment variable provider to be used for querying the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * environment variables from within -the supplier. The supplier should use this provider to obtain</span></font></p> +the supplier. The supplier should use this provider to obtain</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* the already defined environment instead of using -the “default” provider returned by the</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* the already defined environment instead of using +the “default” provider returned by the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* -ManagedBuildManager.getEnvironmentVariableProvider().</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* +ManagedBuildManager.getEnvironmentVariableProvider().</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * The provider passed to a supplier will ignore -searching the variables for the levels </span></font></p> +searching the variables for the levels </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * higher than the current supplier level, will -query only the lower-precedence suppliers </span></font></p> +query only the lower-precedence suppliers </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * for the current level and will query all -suppliers for the lower levels. </span></font></p> +suppliers for the lower levels. </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * This is done to avoid infinite loops that could -be caused if the supplier calls the provider </span></font></p> +be caused if the supplier calls the provider </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * and the provider in turn calls that supplier -again. Also the supplier should not know anything</span></font></p> +again. Also the supplier should not know anything</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font><font face="Courier New"> +<span style="font-family:Courier New; color:#003366"> </span><span style="font-family:Courier New"> <span style="color: #003366"> * about the environment variables defined for the -higher levels.</span></font></p> +higher levels.</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @return the array of IBuildEnvironmentVariable that represents the environment variables </span> -</font></p> +</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> IBuildEnvironmentVariable[] getVariables (IManagedProject project,</font></p> +<span style="font-family:Courier New"> IBuildEnvironmentVariable[] getVariables (IManagedProject project,</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 177.0pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IEnvironmentVariableProvider provider);</font></p> +<span style="font-family:Courier New">IEnvironmentVariableProvider provider);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">}</font></p> -<p class="MsoNormal">The <font face="Courier New">IBuildEnvironmentVariable</font> interface returns information regarding an +<span style="font-family:Courier New">}</span></p> +<p class="MsoNormal">The <span style="font-family:Courier New">IBuildEnvironmentVariable</span> interface returns information regarding an individual environment variable. </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">public interface -IBuildEnvironmentVariable{</font></p> +<span style="font-family:Courier New">public interface +IBuildEnvironmentVariable{</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -public static final int ENVVAR_REPLACE = 1;</font></p> +<span style="font-family:Courier New"> +public static final int ENVVAR_REPLACE = 1;</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -public static final int ENVVAR_REMOVE = 2;</font></p> +<span style="font-family:Courier New"> +public static final int ENVVAR_REMOVE = 2;</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -public static final int ENVVAR_PREPEND = 3;</font></p> +<span style="font-family:Courier New"> +public static final int ENVVAR_PREPEND = 3;</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -public static final int ENVVAR_APPEND = 4;</font></p> +<span style="font-family:Courier New"> +public static final int ENVVAR_APPEND = 4;</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> String getName();</font></p> +<span style="font-family:Courier New"> String getName();</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> String getValue();</font></p> +<span style="font-family:Courier New"> String getValue();</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> * @return one of the IBuildEnvironmentVariable.ENVVAR_* operation types</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> * @return one of the IBuildEnvironmentVariable.ENVVAR_* operation types</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> int -getOperation();</font></p> +<span style="font-family:Courier New"> int +getOperation();</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @return if the variable can hold the -list of values this method returns the String representing</span></font></p> +list of values this method returns the String representing</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * the delimiter that is used to separate values. -This information is used for the following:</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * the delimiter that is used to separate values. +This information is used for the following:</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> *</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> *</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * 1. in append and prepend operations:</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * 1. in append and prepend operations:</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * If the variable already exists and contains some -value the new </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * If the variable already exists and contains some +value the new </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * value will be calculated in the following way:</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * value will be calculated in the following way:</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * For the “prepend” operation:</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * For the “prepend” operation:</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * <New value> = <the value from the -getValue() method><delimiter><Old value></span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * <New value> = <the value from the +getValue() method><delimiter><Old value></span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * For the “append” operation:</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * For the “append” operation:</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * <New value> = <Old value><delimiter><the -value from the getValue() method></span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * <New value> = <Old value><delimiter><the +value from the getValue() method></span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * The Environment Variable Provider will also -remove the duplicates of “sub-values” </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * The Environment Variable Provider will also +remove the duplicates of “sub-values” </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * in the resulting value. </span> -</font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * in the resulting value. </span> +</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * For example:</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * For example:</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * If the current value is +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * If the current value is “string1:string2:string3”, the getDelimiter() method returns “:” </span> -</font></p> +</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * and getValue() method returns “string4:string2” -the new value will contain:</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * and getValue() method returns “string4:string2” +the new value will contain:</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * For the “prepend” operation: -“string4:string2:string1:string3”</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * For the “prepend” operation: +“string4:string2:string1:string3”</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * For the “append” operation: -“string1:string3:string4:string2”</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * For the “append” operation: +“string1:string3:string4:string2”</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * <br> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * <br> * 2. Since the environment variables are also -treated as build macros the delimiter is also used </span></font></p> +treated as build macros the delimiter is also used </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * by the BuildMacroProvider to determine the type -of the macro used to represent the</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * by the BuildMacroProvider to determine the type +of the macro used to represent the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * given environment variable. If the variable has -the delimiter it is treated as the Text-List macro</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * given environment variable. If the variable has +the delimiter it is treated as the Text-List macro</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * otherwise it is treated as the Text macro. (See -Build Macro design for more details)</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * otherwise it is treated as the Text macro. (See +Build Macro design for more details)</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * To specify that no delimiter should be used, the +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * To specify that no delimiter should be used, the getDelimiter() method should<br> - * return null or an empty string</span></font></p> + * return null or an empty string</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> String getDelimiter();</font></p> +<span style="font-family:Courier New"> String getDelimiter();</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">}</font></p> +<span style="font-family:Courier New">}</span></p> <p class="subsection"><a name="_TocSectionDynamic_7">7.7 Defining a Build Path Resolver</a> </p> <p class="MsoNormal" style="margin-left: 0in">To provide a build path resolver, the buildPathResolver attribute in the envVarBuildPath definition must be specified. The value of this attribute should be set to the -name of the class which implements the <font face="Courier New">IBuildPathResolver</font> interface. This +name of the class which implements the <span style="font-family:Courier New">IBuildPathResolver</span> interface. This allows the tool-integrator to provide his/her own logic for resolving the environment variable values to build paths.</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">public interface -IBuildPathResolver {</font></p> +<span style="font-family:Courier New">public interface +IBuildPathResolver {</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> *</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> *</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @param pathType one of the -IEnvVarBuildPath.BUILDPATH _xxx</span></font></p> +IEnvVarBuildPath.BUILDPATH _xxx</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * @param variableName represents the name of the -variable that holds the build paths</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * @param variableName represents the name of the +variable that holds the build paths</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * @param variableValue represents the value of the -value specified with the </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * @param variableValue represents the value of the +value specified with the </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * variableName argument</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * variableName argument</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * @param configuration represents configuration -for which the build paths are requested</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * @param configuration represents configuration +for which the build paths are requested</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -String[] resolveBuildPaths(</font></p> +<span style="font-family:Courier New"> +String[] resolveBuildPaths(</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> int pathType,</font></p> +<span style="font-family:Courier New"> int pathType,</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -String variableName, </font></p> +<span style="font-family:Courier New"> +String variableName, </span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -String variableValue,</font></p> +<span style="font-family:Courier New"> +String variableValue,</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -IConfiguration configuration);</font></p> +<span style="font-family:Courier New"> +IConfiguration configuration);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">}</font></p> +<span style="font-family:Courier New">}</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0">See org.eclipse.cdt.managedbuilder.gnu.cygwin.CygwinPathResolver for an example of a build path resolver. It converts Cygwin-style paths to Windows paths.</p> <p class="subsection"><a name="_TocSectionDynamic_8">7.8 Defining Build Macros</a></p> -<p class="MsoNormal">The <font face="Courier New">IConfigurationBuildMacroSupplier</font> interface and the -<font face="Courier New">IProjectBuildMacroSupplier</font> interface allow a tool-integrator to define build +<p class="MsoNormal">The <span style="font-family:Courier New">IConfigurationBuildMacroSupplier</span> interface and the +<span style="font-family:Courier New">IProjectBuildMacroSupplier</span> interface allow a tool-integrator to define build macros and their values.</p> -<p class="MsoNormal">All methods of the <font face="Courier New">IConfigurationBuildMacroSupplier</font> +<p class="MsoNormal">All methods of the <span style="font-family:Courier New">IConfigurationBuildMacroSupplier </span> interface MUST return macros ONLY for the configuration context, and MUST NOT search for macro values for contexts with lower precedence. This is up to BuildMacroProvider to query macro suppliers passing lower-precedence context if necessary in case the macro value was not found for some specified context</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">public interface -IConfigurationBuildMacroSupplier {</font></p> +<span style="font-family:Courier New">public interface +IConfigurationBuildMacroSupplier {</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> *</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> *</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> * @ macroName the macro name</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> * @ macroName the macro name</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> * @param configuration configuration</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> * @param configuration configuration</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @param provider the instance of the -build macro provider to be used for querying the</span></font></p> +build macro provider to be used for querying the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * build macros from within the -supplier. The supplier should use this provider to obtain</span></font></p> +supplier. The supplier should use this provider to obtain</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* the already defined build macros instead of using -the “default” provider returned by the</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* the already defined build macros instead of using +the “default” provider returned by the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* ManagedBuildManager.getBuildMacroProvider().</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* ManagedBuildManager.getBuildMacroProvider().</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * The provider passed to a supplier will ignore +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * The provider passed to a supplier will ignore searching macros for the levels <br> * higher than the current supplier level, will -query only the lower-precedence suppliers </span></font></p> +query only the lower-precedence suppliers </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * for the current level and will query all -suppliers for the lower levels. </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * for the current level and will query all +suppliers for the lower levels. </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * This is done to avoid infinite loops that could -be caused if the supplier calls the provider </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * This is done to avoid infinite loops that could +be caused if the supplier calls the provider </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * and the provider in turn calls that supplier +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * and the provider in turn calls that supplier again. Also the supplier should not know anything<br> * about the build macros defined for the higher -levels.</span></font></p> +levels.</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @return the reference to the IBuildMacro interface representing </span> -</font></p> +</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * the build macro of a given name or null if the -macro of that name is not defined</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * the build macro of a given name or null if the +macro of that name is not defined</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New">IBuildMacro getMacro(String macroName, </font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New">IBuildMacro getMacro(String macroName, </span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 70.8pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IConfiguration configuration, </font> </p> +<span style="font-family:Courier New">IConfiguration configuration, </span> </p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 70.8pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IBuildMacroProvider provider);</font></p> +<span style="font-family:Courier New">IBuildMacroProvider provider);</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> *</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> *</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> * @param configuration configuration</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> * @param configuration configuration</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @param provider the instance of the -build macro provider to be used for querying the</span></font></p> +build macro provider to be used for querying the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * build macros from within the -supplier. The supplier should use this provider to obtain</span></font></p> +supplier. The supplier should use this provider to obtain</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* the already defined build macros instead of using -the “default” provider returned by the</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* the already defined build macros instead of using +the “default” provider returned by the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* ManagedBuildManager.getBuildMacroProvider().</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* ManagedBuildManager.getBuildMacroProvider().</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* The provider passed to a supplier will ignore -searching macros for the levels </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* The provider passed to a supplier will ignore +searching macros for the levels </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* higher than the current supplier level, will -query only the lower-precedence suppliers </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* higher than the current supplier level, will +query only the lower-precedence suppliers </span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * for the current level and will query all -suppliers for the lower levels. </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * for the current level and will query all +suppliers for the lower levels. </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * This is done to avoid infinite loops that could -be caused if the supplier calls the provider </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * This is done to avoid infinite loops that could +be caused if the supplier calls the provider </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * and the provider in turn calls that supplier -again. Also the supplier should not know anything</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * and the provider in turn calls that supplier +again. Also the supplier should not know anything</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * about the build macros defined for the higher -levels.</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * about the build macros defined for the higher +levels.</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @return the IBuildMacro[] array -representing defined macros </span></font></p> +representing defined macros </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New">IBuildMacro[] getMacros(IConfiguration configuration,</font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New">IBuildMacro[] getMacros(IConfiguration configuration,</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 70.8pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IBuildMacroProvider provider);</font></p> +<span style="font-family:Courier New">IBuildMacroProvider provider);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">}</font></p> -<p class="MsoNormal">All methods of the <font face="Courier New">IProjectBuildMacroSupplier</font> interface +<span style="font-family:Courier New">}</span></p> +<p class="MsoNormal">All methods of the <span style="font-family:Courier New">IProjectBuildMacroSupplier</span> interface MUST return macros ONLY for the Project context, and MUST NOT search for macro values for contexts with lower precedence. This is up to the BuildMacroProvider to query macro suppliers passing lower-precedence context if necessary in case the macro value was not found for some specified context.</p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">public interface -IProjectBuildMacroSupplier {</font></p> +<span style="font-family:Courier New">public interface +IProjectBuildMacroSupplier {</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> *</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> *</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> * @ macroName the macro mane</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> * @ macroName the macro mane</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @param project the instance of the -managed project</span></font></p> +managed project</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @param provider the instance of the -build macro provider to be used for querying the</span></font></p> +build macro provider to be used for querying the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * build macros from within the -supplier. The supplier should use this provider to obtain</span></font></p> +supplier. The supplier should use this provider to obtain</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* the already defined build macros instead of using -the “default” provider returned by the</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* the already defined build macros instead of using +the “default” provider returned by the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* ManagedBuildManager.getBuildMacroProvider().</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* ManagedBuildManager.getBuildMacroProvider().</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * The provider passed to a supplier will ignore -searching macros for the levels </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * The provider passed to a supplier will ignore +searching macros for the levels </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * higher than the current supplier level, will -query only the lower-precedence suppliers </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * higher than the current supplier level, will +query only the lower-precedence suppliers </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * for the current level and will query all -suppliers for the lower levels. </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * for the current level and will query all +suppliers for the lower levels. </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * This is done to avoid infinite loops that could -be caused if the supplier calls the provider </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * This is done to avoid infinite loops that could +be caused if the supplier calls the provider </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * and the provider in turn calls that supplier -again. Also the supplier should not know anything</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * and the provider in turn calls that supplier +again. Also the supplier should not know anything</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * about the build macros defined for the higher -levels.</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * about the build macros defined for the higher +levels.</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @return the reference to the IBuildMacro interface representing </span> -</font></p> +</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * the build macro of a given name or null if the -macro of that name is not defined</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * the build macro of a given name or null if the +macro of that name is not defined</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New">IBuildMacro getMacro(String macroName, </font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New">IBuildMacro getMacro(String macroName, </span></span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 106.2pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IManagedProject project,</font></p> +<span style="font-family:Courier New">IManagedProject project,</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 106.2pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IBuildMacroProvider provider);</font></p> +<span style="font-family:Courier New">IBuildMacroProvider provider);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> *</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> *</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @param project the instance of the -managed project</span></font></p> +managed project</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @param provider the instance of the -build macro provider to be used for querying the</span></font></p> +build macro provider to be used for querying the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * build macros from within the -supplier. The supplier should use this provider to obtain</span></font></p> +supplier. The supplier should use this provider to obtain</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* the already defined build macros instead of using -the “default” provider returned by the</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* the already defined build macros instead of using +the “default” provider returned by the</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366">* ManagedBuildManager.getBuildMacroProvider().</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366">* ManagedBuildManager.getBuildMacroProvider().</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * The provider passed to a supplier will ignore -searching macros for the levels </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * The provider passed to a supplier will ignore +searching macros for the levels </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * higher than the current supplier level, will -query only the lower-precedence suppliers </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * higher than the current supplier level, will +query only the lower-precedence suppliers </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * for the current level and will query all -suppliers for the lower levels. </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * for the current level and will query all +suppliers for the lower levels. </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * This is done to avoid infinite loops that could -be caused if the supplier calls the provider </span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * This is done to avoid infinite loops that could +be caused if the supplier calls the provider </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * and the provider in turn calls that supplier -again. Also the supplier should not know anything</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * and the provider in turn calls that supplier +again. Also the supplier should not know anything</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New"><span style="color: #003366"> * about the build macros defined for the higher -levels.</span></font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New"><span style="color: #003366"> * about the build macros defined for the higher +levels.</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @return the IBuildMacro[] array -representing defined macros </span></font></p> +representing defined macros </span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New" color="#003366"> </font> -<font face="Courier New">IBuildMacro[] getMacros(IManagedProject project,</font></p> +<span style="font-family:Courier New; color:#003366"> </span> +<span style="font-family:Courier New">IBuildMacro[] getMacros(IManagedProject project,</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 106.2pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">IBuildMacroProvider provider);</font></p> +<span style="font-family:Courier New">IBuildMacroProvider provider);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">}</font></p> -<p class="MsoNormal">The <font face="Courier New">IBuildMacro</font> interface returns information regarding an +<span style="font-family:Courier New">}</span></p> +<p class="MsoNormal">The <span style="font-family:Courier New">IBuildMacro</span> interface returns information regarding an individual build macro. </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">public interface -IBuildMacro{</font></p> +<span style="font-family:Courier New">public interface +IBuildMacro{</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> public -static final int VALUE_TEXT = 1; //can hold any text string</font></p> +<span style="font-family:Courier New"> public +static final int VALUE_TEXT = 1; //can hold any text string</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> public -static final int VALUE_TEXT_LIST = 2; //can hold the array of text string values</font></p> +<span style="font-family:Courier New"> public +static final int VALUE_TEXT_LIST = 2; //can hold the array of text string values</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> public -static final int VALUE_PATH_FILE = 3; //can hold file path</font></p> +<span style="font-family:Courier New"> public +static final int VALUE_PATH_FILE = 3; //can hold file path</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> public +<span style="font-family:Courier New"> public static final int VALUE_PATH_FILE_LIST = 4; //can hold the array of file path -values</font></p> +values</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> public -static final int VALUE_PATH_DIR = 5; //can hold dir path</font></p> +<span style="font-family:Courier New"> public +static final int VALUE_PATH_DIR = 5; //can hold dir path</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> public +<span style="font-family:Courier New"> public static final int VALUE_PATH_DIR_LIST = 6; //can hold the array of dir path -values</font></p> +values</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> public -static final int VALUE_PATH_ANY = 7; //can hold both file and dir path</font></p> +<span style="font-family:Courier New"> public +static final int VALUE_PATH_ANY = 7; //can hold both file and dir path</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> public -static final int VALUE_PATH_ANY_LIST = 8; //can hold the array of PATH_ANY</font></p> +<span style="font-family:Courier New"> public +static final int VALUE_PATH_ANY_LIST = 8; //can hold the array of PATH_ANY</span></p> <p class="MsoNormal" style="text-indent: 35.4pt; margin-left: 283.2pt; margin-top: 0; margin-bottom: 0"> -<font face="Courier New">// values </font></p> +<span style="font-family:Courier New">// values </span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> String getName();</font></p> +<span style="font-family:Courier New"> String getName();</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -</font> </p> +<span style="font-family:Courier New"> +</span> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> * @returns IBuildMacro.VALUE_xxx</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> * @returns IBuildMacro.VALUE_xxx</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> int -getMacroValueType();</font></p> +<span style="font-family:Courier New"> int +getMacroValueType();</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> +<span style="font-family:Courier New"> <span style="color: #003366"> * @throws BuildMacroException if macro -holds StringList-type value</span></font></p> +holds StringList-type value</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -<span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"> +<span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> String getStringValue() throws BuildMacroException;</font></p> +<span style="font-family:Courier New"> String getStringValue() throws BuildMacroException;</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> </p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> /**</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> /**</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> * @throws BuildMacroException if macro -holds single String-type value</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> * @throws BuildMacroException if macro +holds single String-type value</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"><span style="color: #003366"> */</span></font></p> +<span style="font-family:Courier New"><span style="color: #003366"> */</span></span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New"> -String[] getStringListValue() throws BuildMacroException;</font></p> +<span style="font-family:Courier New"> +String[] getStringListValue() throws BuildMacroException;</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> -<font face="Courier New">}</font></p> +<span style="font-family:Courier New">}</span></p> <p class="subsection"><a name="_TocSectionDynamic_9">7.9 Defining a Configuration Name Provider</a></p> <p class="MsoNormal">All the configuration names must be unique within a project. You can provide unique configuration names in your build @@ -6721,14 +6721,14 @@ configurations. You can define unique names statically in your build definitions (for example, "Debug_1.0", "Debug_2.0", etc.) However, these names are not very "user-friendly", particularly for a user who intends to use a single version of your tool-chain. The alternative is to dynamically -assign unique configuration names using a configuration name provider (see the <font face="Courier New"> -getNewConfigurationName </font><font face="Arial">method below.) </font>The first configuration +assign unique configuration names using a configuration name provider (see the <span style="font-family:Courier New"> +getNewConfigurationName </span>method below.) The first configuration that is created gets to use the most “basic” name – for example, “Debug”. When another configuration is created that uses a different tool-chain version, it would see that “Debug” was already chosen, so it could return a more qualified name - for example, “Debug_2.0”. The same technique could be used when your tool-chain supports multiple host/target platforms.</p> -<p class="MsoNormal"><font face="Courier New">public interface +<p class="MsoNormal"><span style="font-family:Courier New">public interface IConfigurationNameProvider {<br> <br> /*<br> @@ -6741,12 +6741,12 @@ in the project.<br> <br> String getNewConfigurationName(IConfiguration configuration, String [] usedConfigurationNames );<br> -}</font></p> +}</span></p> <p class="subsection"><a name="_TocSectionDynamic_10">7.10 Defining an Output Name Provider</a></p> <p>You can specify an output name provider for an outputType. You must specify and supply a class that implements the <code>IManagedOutputNameProvider</code> interface shown below. The class name is assigned to the outputType element, -<b>nameProvider</b> attribute. </p> +<strong>nameProvider</strong> attribute. </p> <p class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier New">public interface IManagedOutputNameProvider{</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> @@ -6767,8 +6767,8 @@ corresponding to the primary input name(s)</span></p> getOutputPaths(ITool tool, IPath[] primaryInputs);</span></p> <p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"> <span style="font-size:10.0pt;font-family:Courier New">}</span></p> -<p class="MsoNormal" style="margin-top: 6px; margin-bottom: 0">When <b>multipleOfType</b> -is true, an output name provider, or the <b>outputNames</b> attribute, is required +<p class="MsoNormal" style="margin-top: 6px; margin-bottom: 0">When <strong>multipleOfType</strong> +is true, an output name provider, or the <strong>outputNames</strong> attribute, is required in order for MBS to know the names of the output files.</p> <p class="MsoNormal" style="margin-top: 6px; margin-bottom: 0">The returned paths must be relative to the top-level build directory. However, if only a file @@ -6779,10 +6779,10 @@ build directory, regardless of the source file directory structure, return "./path".</p> <p class="subsection"><a name="_TocSectionDynamic_11">7.11 Defining an Option Value Handler</a></p> <p>You can specify a value handler for an option. You must specify and -supply a class that implements the <font face="Courier New"> -IManagedOptionValueHandler</font> interface shown below. This interface is +supply a class that implements the <span style="font-family:Courier New"> +IManagedOptionValueHandler</span> interface shown below. This interface is used to dynamically manage the value of an option.</p> -<p><font face="Courier New">public interface IManagedOptionValueHandler{ <br> +<p><span style="font-family:Courier New">public interface IManagedOptionValueHandler{ <br> <br> public final int EVENT_OPEN = 1; /** The option is opened, i.e. its UI element <br> @@ -6902,18 +6902,18 @@ to <br> IOption option,<br> String extraArgument, <br> String enumValue);<br> -}</font></p> -<p><font face="Arial">See the Shared Tool Options design document in bugzilla #90481 -for additional information.</font></p> +}</span></p> +<p>See the Shared Tool Options design document in bugzilla #90481 +for additional information.</p> <p class="subsection"><a name="_TocSectionDynamic_12">7.12 Defining an Option Applicability Calculator</a></p> <p>You can specify an option applicability calculator for an option. You must specify and supply a -class that implements the <code><font face="Courier New">IManagedOutputNameProvider</font></code><font face="Arial"> +class that implements the <code><span style="font-family:Courier New">IManagedOutputNameProvider</code> interface shown below. The class name is assigned to the outputType element, -<b>nameProvider</b> attribute. You should implement this interface when an +<strong>nameProvider</strong> attribute. You should implement this interface when an option is not always applicable - for example, when an option is only used if -another option has a particular value.</font></p> -<p><font face="Courier New">public interface IOptionApplicability {<br> +another option has a particular value.</p> +<p><span style="font-family:Courier New">public interface IOptionApplicability {<br> /**<br> @@ -7008,7 +7008,7 @@ public boolean isOptionEnabled(<br> IHoldsOptions holder, <br> IOption option); <br> <br> -}</font></p> +}</span></p> <p class="subsection"><a name="_TocSectionDynamic_13">7.13 Defining a Dynamic Element Provider</a></p> <p>Tool integrators may supply a dynamic element provider to dynamically provide the definitions that are otherwise specified in the buildDefinitions extension point. To specify a dynamic element provider, your build @@ -7161,8 +7161,8 @@ Element Schema:</P> <P class="MsoNormal" style="margin-left:0cm">Specifies the Java class which implements the added page.<SPAN style="mso-spacerun:yes"> </SPAN>This class must implement the <A - name="OLE_LINK7"><SPAN style="mso-bookmark:OLE_LINK8"><FONT - face="Courier New">org.eclipse.jface.wizard.IWizardPage</FONT> + name="OLE_LINK7"><SPAN style="mso-bookmark:OLE_LINK8"><span style="font-family:Courier New"> + org.eclipse.jface.wizard.IWizardPage</span> </SPAN></A>interface</P> </TD> <TD width="81" valign="top" @@ -7189,7 +7189,7 @@ Element Schema:</P> which implements the operations associated with this page.<SPAN style="mso-spacerun:yes"> </SPAN>The class must implement the - <FONT face="Courier New">java.lang.Runnable</FONT> interface</P> + <span style="font-family:Courier New">java.lang.Runnable</span> interface</P> </TD> <TD width="81" valign="top" style="width:60.6pt;border-top:none;border-left:none; @@ -7639,9 +7639,9 @@ See the CDT 2.1 Gnu tool-chain definitions for an example of the new model.</p> information defined in a target element in a 2.0 manifest file has been split up into the ProjectType, ToolChain, Builder, and TargetPlatform elements in the new model.</p> -<p class="MsoNormal" style="margin-top:6.0pt">The Target attributes <i>name, id, -isTest </i>and<i> isAbstract</i> should be transferred to a new ProjectType -element in the new model. The <i>id</i> assigned to the Target must be +<p class="MsoNormal" style="margin-top:6.0pt">The Target attributes <em>name, id, +isTest </em>and<em> isAbstract</em> should be transferred to a new ProjectType +element in the new model. The <em>id</em> assigned to the Target must be transferred to the new ProjectType element without change. Otherwise, projects created using your integration with CDT 1.2 or 2.0.x will not be able to be converted. There is no tool integrator intervention into the conversion process @@ -7649,46 +7649,46 @@ yet, but this is a high priority for CDT 3.0.</p> <h3 class="subsection">8.1.3 MBS 2.0 Configuration Element</h3> <p class="MsoNormal" style="margin-top:6.0pt">The Configuration children of the Target element are made Configuration children of the new ProjectType element. -The Configuration <i>name </i>and <i> id</i> attributes should be transferred -with the Configuration. The <i>id</i> assigned to the Configuration must remain +The Configuration <em>name </em>and <em> id</em> attributes should be transferred +with the Configuration. The <em>id</em> assigned to the Configuration must remain unchanged in order to support the conversion of old model project files. The -Target attributes <i>artifactName, cleanCommand </i>and <i>errorParsers </i> -attributes should be transferred to the Configuration element. The Target <i> -defaultExtension </i>attribute should be transferred to the Configuration +Target attributes <em>artifactName, cleanCommand </em>and <em>errorParsers </em> +attributes should be transferred to the Configuration element. The Target <em> +defaultExtension </em>attribute should be transferred to the Configuration element -as the <i>artifactExtension </i>attribute (Note the name change).</p> +as the <em>artifactExtension </em>attribute (Note the name change).</p> <p class="MsoNormal" style="margin-top:6.0pt">A new ToolChain element should be -created as the child of each Configuration element. The <i>name</i> and <i>id</i> +created as the child of each Configuration element. The <em>name</em> and <em>id</em> of the ToolChain are not dependent upon the name of any of the old model objects. However, if you allow users to create CDT 2.1 projects using your CDT -2.0 manifest file, then the <i>id</i> of your new ToolChain must be the parent -Configuration <i>id, </i>appended with “.toolchain”. The Target <i>isAbstract, -osList, </i>a<i>rchList</i> and <i>scannerInfoCollector </i>attributes are +2.0 manifest file, then the <em>id</em> of your new ToolChain must be the parent +Configuration <em>id, </em>appended with “.toolchain”. The Target <em>isAbstract, +osList, </em>a<em>rchList</em> and <em>scannerInfoCollector </em>attributes are transferred to the ToolChain element.</p> <p class="MsoNormal" style="margin-top:6.0pt">A new Builder element can be -created as the child of each ToolChain element. The <i>name</i> and <i>id</i> of +created as the child of each ToolChain element. The <em>name</em> and <em>id</em> of the Builder are not dependent upon the name of any of the old model elements. However, if you allow users to create CDT 2.1 projects using your CDT 2.0 -manifest file, then the <i>id</i> of your new Builder must be the parent -Configuration <i>id, </i>appended with “.builder”. The target <i>isAbstract</i> -attribute is transferred to the Builder element. <i> </i>The target <i> -makeCommand</i> attribute should be transferred to the Builder element as the <i> -command </i>attribute (Note the name change).<i> </i>The target <i> -makeArguments </i>attribute should be transferred to the Builder element as the -<i>arguments </i>attribute (Note the name change).<i> </i>The target <i> -makefileGenerator </i>attribute should be transferred to the Builder element as -the <i>buildfileGenerator </i>attribute (Note the name change).</p> +manifest file, then the <em>id</em> of your new Builder must be the parent +Configuration <em>id, </em>appended with “.builder”. The target <em>isAbstract</em> +attribute is transferred to the Builder element. <em> </em>The target <em> +makeCommand</em> attribute should be transferred to the Builder element as the <em> +command </em>attribute (Note the name change).<em> </em>The target <em> +makeArguments </em>attribute should be transferred to the Builder element as the +<em>arguments </em>attribute (Note the name change).<em> </em>The target <em> +makefileGenerator </em>attribute should be transferred to the Builder element as +the <em>buildfileGenerator </em>attribute (Note the name change).</p> <p class="MsoNormal" style="margin-top:6.0pt">A new TargetPlatform element can be -created as the child of each ToolChain element. The <i>name</i> and <i>id</i> of +created as the child of each ToolChain element. The <em>name</em> and <em>id</em> of the TargetPlatform are not dependent upon the name of any of the old model elements. However, if you allow users to create CDT 2.1 projects using your CDT -2.0 manifest file, then the <i>id</i> of your new TargetPlatform must be the -parent Configuration <i>id, </i>appended with “.targetplatform”. The target <i> -isAbstract</i> and <i>binaryParser </i>attributes are transferred to the -TargetPlatform element. The TargetPlatform element contains <i>osList </i>and <i> -archList</i> attributes that specify the architecture(s) and operating system(s) +2.0 manifest file, then the <em>id</em> of your new TargetPlatform must be the +parent Configuration <em>id, </em>appended with “.targetplatform”. The target <em> +isAbstract</em> and <em>binaryParser </em>attributes are transferred to the +TargetPlatform element. The TargetPlatform element contains <em>osList </em>and <em> +archList</em> attributes that specify the architecture(s) and operating system(s) on which the Configuration’s build artifact(s) execute. You can transfer the -Target <i>osList </i>and <i>archList</i> attributes if appropriate.</p> +Target <em>osList </em>and <em>archList</em> attributes if appropriate.</p> <h3 class="subsection">8.1.4 MBS 2.0 Tool Element</h3> <p class="MsoNormal">The old model allows Tools to be defined at the top level scope in the manifest file. This is still true in the new model. In addition, @@ -7699,21 +7699,21 @@ also be specified as the children of Target elements. In the new model, To elements are children of ToolChain elements. Old model Tool elements need to be added as the child of each ToolChain that uses the Tool. All of the old model Tool attributes are supported by the new model.</p> -<p class="MsoNormal" style="margin-top:6.0pt">The <i>id</i> assigned to the Tool +<p class="MsoNormal" style="margin-top:6.0pt">The <em>id</em> assigned to the Tool must remain unchanged in order to support the conversion of old model project -files. The <i>outputs </i>attribute no longer defaults to an empty string. If +files. The <em>outputs </em>attribute no longer defaults to an empty string. If your Tool produces files by default with no extension, you must specify -‘outputs=””’ in the definition of the Tool or one of its ancestors (<i>superClass</i>).</p> +‘outputs=””’ in the definition of the Tool or one of its ancestors (<em>superClass</em>).</p> <h3 class="subsection">8.1.5 MBS 2.0 ToolReference Element</h3> <p class="MsoNormal">The new model does not define a ToolReference element. -Instead, a Tool element can specify the <i>superClass</i> attribute in order to +Instead, a Tool element can specify the <em>superClass</em> attribute in order to provide the same functionality. That is, specifying a Tool that inherits attributes from another Tool and can override one or more attributes.</p> <p class="MsoNormal" style="margin-top:6.0pt">The old model uses ToolReferences in two ways. They can be specified as the child of a Configuration element. In this case, the ToolReference should be converted a Tool element child of the -Configuration’s ToolChain, transferring the value of the <i>id </i>attribute to -the Tool <i>superClass </i>attribute.</p> +Configuration’s ToolChain, transferring the value of the <em>id </em>attribute to +the Tool <em>superClass </em>attribute.</p> <p class="MsoNormal" style="margin-top:6.0pt">A ToolReference can also be specified as the child of a Target element. In this case, the ToolReference applies to all of the Configuration children of the Target. These ToolReference @@ -7721,17 +7721,17 @@ elements need to be converted to Tool elements and added as the child of each To <h3 class="subsection">8.1.6 MBS 2.0 Option Element</h3> <p class="MsoNormal" style="margin-top:6.0pt">All of the old model Option attributes are supported by the new model.</p> -<p class="MsoNormal" style="margin-top:6.0pt">The <i>id</i> assigned to the +<p class="MsoNormal" style="margin-top:6.0pt">The <em>id</em> assigned to the Option must remain unchanged in order to support the conversion of old model project files.</p> <h3 class="subsection">8.1.7 MBS 2.0 OptionReference Element</h3> <p class="MsoNormal">The new model does not define an OptionReference element. -Instead, an Option element can specify the <i>superClass</i> attribute in order +Instead, an Option element can specify the <em>superClass</em> attribute in order to provide the same functionality. That is, specifying an Option that inherits attributes from another Option and can override one or more attributes.</p> <p class="MsoNormal" style="margin-top:6.0pt">All OptionReference elements should -be converted to Option elements, transferring the value of the <i>id </i> -attribute to the Option <i>superClass </i>attribute.</p> +be converted to Option elements, transferring the value of the <em>id </em> +attribute to the Option <em>superClass </em>attribute.</p> <h3 class="subsection">8.1.8 MBS 2.0 OptionCategory, EnumeratedOptionValue, ListOptionValue Elements</h3> <p class="MsoNormal">There are no changes to these elements.</p> diff --git a/doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtodeveloptemplates.html b/doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtodeveloptemplates.html index 4976df14e8e..d18706f98a5 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtodeveloptemplates.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtodeveloptemplates.html @@ -447,7 +447,7 @@ The following is a list of process types provided by the Template Engine: <!--<ul> <li> <p> -<b>NewProject</b>: It defines all the parameters required for a +<strong>NewProject</strong>: It defines all the parameters required for a new C/C++ project and provides the fully qualified name of the class, which processes these parameters. </p> @@ -484,7 +484,7 @@ configurations for the project. It is of type <code>simple</code>. </ul> --> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>NewManagedProject</b>: It defines all the parameters +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>NewManagedProject</strong>: It defines all the parameters required for a new managed project and provides the fully qualified name of the class, which processes these parameters. </p> @@ -521,7 +521,7 @@ configurations for the managed project. It is of type <code>simple</code>. </ul> <li> <p> -<i>org.eclipse.cdt.core.</i><b>Copy</b>: It defines all the parameters required to copy +<em>org.eclipse.cdt.core.</em><strong>Copy</strong>: It defines all the parameters required to copy files and provides the fully qualified name of the class, which processes these parameters. </p> @@ -559,14 +559,14 @@ location. </ul> <li> <p> -<i>org.eclipse.cdt.core.</i><b>Append</b>: It defines all the parameters required to append +<em>org.eclipse.cdt.core.</em><strong>Append</strong>: It defines all the parameters required to append files to a project and provides the fully qualified name of the class, which processes these parameters. For more information about the parameters, refer to the <code>Copy</code> process type described above. </p> <li> <p> -<i>org.eclipse.cdt.core.</i><b>AddFile</b>: It defines all the parameters required to add a +<em>org.eclipse.cdt.core.</em><strong>AddFile</strong>: It defines all the parameters required to add a file to the project and provides the fully qualified name of the class, which processes these parameters. </p> @@ -591,7 +591,7 @@ process type described above. </ul> <li> <p> -<i>org.eclipse.cdt.core.</i><b>AddFiles</b>: It defines all the parameters required to add +<em>org.eclipse.cdt.core.</em><strong>AddFiles</strong>: It defines all the parameters required to add files to a project and provides the fully qualified name of the class, which processes these parameters. </p> @@ -616,7 +616,7 @@ process type described above. </ul> <li> <p> -<i>org.eclipse.cdt.core.</i><b>CreateSourceFolder</b>: It defines all the parameters +<em>org.eclipse.cdt.core.</em><strong>CreateSourceFolder</strong>: It defines all the parameters required to create a folder for the source files in a project and provides the fully qualified name of the class, which processes these parameters. </p> @@ -640,7 +640,7 @@ created. It is of <code>simple</code> type. </ul> <li> <p> -<i>org.eclipse.cdt.core.</i><b>AddLink</b>: It defines all the parameters required to +<em>org.eclipse.cdt.core.</em><strong>AddLink</strong>: It defines all the parameters required to create a linked file and provides the fully qualified name of the class, which processes these parameters. </p> @@ -670,7 +670,7 @@ file should be created. It is of <code>simple</code> type. </ul> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>CreateIncludeFolder</b>: It defines all the parameters +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>CreateIncludeFolder</strong>: It defines all the parameters required to create a folder for the header files in a project and provides the fully qualified name of the class, which processes these parameters. For information about the parameters, refer to the <code>CreateSourceFolder</code> @@ -678,7 +678,7 @@ process type described above. </p> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>ExcludeResources</b>: It defines all the parameters +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>ExcludeResources</strong>: It defines all the parameters required to exclude resources from a CDT project and provides the fully qualified name of the class, which processes these parameters. </p> @@ -696,7 +696,7 @@ type. <p> <em>configIdPattern</em>: Use this parameter to specify a regular expression of <code>java.util.regex.Pattern</code> syntax for matching against project configuration ids. -The resources that match any of the regular expressions given in the <i>filePatterns</i> argument +The resources that match any of the regular expressions given in the <em>filePatterns</em> argument will be excluded from all matching project configurations. It is of <code>simple</code> type. </p> <li> @@ -706,7 +706,7 @@ will be excluded from all matching project configurations. It is of <code>simple will be matched against are workspace relative (include the project folder) and use forward slash as the file separator. That this argument is an array is purely to allow logically separate patterns to be given separately rather than as one big string. If any of the regular expressions matches then the resource in question will be excluded for the matching configuration(s). -The resources that match any of the regular expressions given in the <i>filePatterns</i> argument +The resources that match any of the regular expressions given in the <em>filePatterns</em> argument will be excluded for all matching project configurations. It is of <code>simple-array</code> type. <li> <p> @@ -719,7 +719,7 @@ files should not be excluded for without having to know what other configuration </p> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>SetMBSStringOptionValue</b>: It defines all the parameters +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>SetMBSStringOptionValue</strong>: It defines all the parameters required to create a string option value and provides the fully qualified name of the class, which processes these parameters. </p> @@ -762,7 +762,7 @@ the resource. It is of <code>simple</code> type. </ul> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>SetMBSStringListOptionValues</b>: It defines all the +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>SetMBSStringListOptionValues</strong>: It defines all the parameters required to create a string list of option values and provides the fully qualified name of the class, which processes these parameters. The parameters required are similar to that of <code>SetMBSStringOptionValue</code> @@ -772,7 +772,7 @@ option values. For information about the parameters, refer to the </p> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>SetMBSBooleanOptionValue</b>: It defines all the parameters +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>SetMBSBooleanOptionValue</strong>: It defines all the parameters required to create a boolean option value and provides the fully qualified name of the class, which processes these parameters. The parameters required are similar to that of <code>SetMBSStringOptionValue</code> process type, only @@ -782,7 +782,7 @@ For information about the parameters, refer to the </p> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>AppendToMBSStringOptionValue</b>: It defines all the +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>AppendToMBSStringOptionValue</strong>: It defines all the parameters required to append a string option value to an existing string option. It also provides the fully qualified name of the class, which processes these parameters. For information about the parameters, refer to the @@ -790,21 +790,21 @@ these parameters. For information about the parameters, refer to the </p> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>AppendToMBSStringListOptionValues</b>: It defines all the +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>AppendToMBSStringListOptionValues</strong>: It defines all the parameters required to append a string list of option values to an existing string list of option value. It also provides the fully qualified name of the class, which processes these parameters. For information about the parameters, refer to the <code>SetMBSStringListOptionValues</code> process type described above. </p> <li> <p> -<i>org.eclipse.cdt.core.</i><b>AppendCreate</b>: It defines all the parameters required to +<em>org.eclipse.cdt.core.</em><strong>AppendCreate</strong>: It defines all the parameters required to append or create a file in a project. It also provides the fully qualified name of the class, which processes these parameters. For information about the parameters, refer to the <code>AddFiles</code> process type described above. </p> <li> <p> -<i>org.eclipse.cdt.core.</i><b>CreateResourceIdentifier</b>: It defines all the parameters +<em>org.eclipse.cdt.core.</em><strong>CreateResourceIdentifier</strong>: It defines all the parameters required to append or create a resource identifier. It also provides the fully qualified name of the class, which processes these parameters. </p> @@ -827,7 +827,7 @@ type. </ul> <li> <p> -<i>org.eclipse.cdt.managedbuilder.core.</i><b>GenerateMakefileWithBuildDescription</b>: +<em>org.eclipse.cdt.managedbuilder.core.</em><strong>GenerateMakefileWithBuildDescription</strong>: </p> <ul> <li> diff --git a/doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtoregistertemplates.html b/doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtoregistertemplates.html index 393eef136bf..845ef76bf14 100644 --- a/doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtoregistertemplates.html +++ b/doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtoregistertemplates.html @@ -59,9 +59,9 @@ header files, source files, resource files etc. <p> Open the plug-in manifest editor and select the <code class="ProgramOutput">Dependencies</code> page. For more information on plug-in manifest -editor, refer to <i>PDE +editor, refer to <em>PDE Guide > Getting Started > Basic Plug-in Tutorial -> Plug-in manifest editor</i>. +> Plug-in manifest editor</em>. </p> <li> <p> |