mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-04-21 21:52:10 +02:00
Code Issues Wiki Activity

Bug 307593 - [Accessibility] CDT documentation has accessibility issues

Browse source
This commit is contained in:
Vivian Kong 2010-03-31 01:34:27 +00:00
parent 6d33ab23a6
commit d8c47d612a
202 changed files with 2905 additions and 2895 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/org.eclipse.cdt.doc.isv/book.css
View file

@ -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 }
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;}

2
doc/org.eclipse.cdt.doc.isv/cdtOptions
View file

@ -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.*"

12
doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/migration_guides/4.0/migration_guide_40.html
View file

@ -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 &quot;What's New in the CDT Build System&quot; 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>&nbsp;&nbsp;&nbsp;
Example:</b> to illustrate the above requirement here is how this is handled
<p class="MsoNormal" style="margin-top:0; margin-bottom:0"><strong>&nbsp;&nbsp;&nbsp;
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">&nbsp;&nbsp;&nbsp;
The gnu plug-in contains the gcc linker tool on Linux is defined as</p>

120
doc/org.eclipse.cdt.doc.isv/guide/cdt_build_system/whats_new/4.0/whats_new_CBS_40.html
View file

@ -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&quot; user description for more detail on the New Project Wizard
type and tool-chain(s) to be used with the project type.</p>
<p>&nbsp;</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>&nbsp; The new New Project Wizard now
<p><strong><span style="color:#FF0000">NOTE:</span></strong>&nbsp; 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>&nbsp;&nbsp;&nbsp;
Example:</b> to illustrate the above requirement here is how this is handled
<p class="MsoNormal" style="margin-top:0; margin-bottom:0"><strong>&nbsp;&nbsp;&nbsp;
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">&nbsp;&nbsp;&nbsp;
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=&quot;%ToolName.linker.cygwin.gnu.c&quot; 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
&quot;name&quot; 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 &quot;Toolchain:&quot;
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 &quot;general project types&quot; 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
&quot;ToolChains:&quot; 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 &quot;buildArtefactType&quot; property which represents the build
@ -308,7 +308,7 @@ shared library</p>
org.eclipse.cdt.managedbuilder.core.buildProperties extension point.</p>
<p>See the &quot;Build Properties&quot; 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 &quot;buildArtefact&quot; 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">&quot;cdt.managedbuild.tool.gnu.builder.mingw.base&quot;</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</font><span style="font-size: 10.0pt; color: navy">&nbsp;...</span></span></p>
<span style="font-family: Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<span style="font-size: 10.0pt; color: navy">&nbsp;...</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </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">&nbsp;</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 &quot;Build Properties
mechanism&quot; section for detail on the Build Properties mechanism)</p></li>
</ol>
<p><font color="#FF0000"><b>NOTE: </b></font>&nbsp;In order to function properly
<p><span style="color:#FF0000"><strong>NOTE: </strong></span>&nbsp;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>&nbsp;&nbsp;&nbsp;
Example:</b> to illustrate the above requirement here is how this is handled
<p class="MsoNormal" style="margin-top:0; margin-bottom:0"><strong>&nbsp;&nbsp;&nbsp;
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">&nbsp;&nbsp;&nbsp;
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">&nbsp;</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">
&nbsp;</span></p>
<p class="MsoNormal" style="margin-top: 0; margin-bottom: 0">&nbsp;</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">&nbsp;</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:&quot;Courier New&quot;;color:navy">&lt;/option&gt;</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">&nbsp;</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">&nbsp;</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">&nbsp;&nbsp;&nbsp;&nbsp;</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">&nbsp;</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 &quot;buildArtefactType&quot; 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 &quot;buildProperties&quot; 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">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .......</span><span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: navy">&gt;</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">
&lt;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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
...</span></font></p>
<span style="font-family: Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
...</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">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
@ -1138,8 +1138,8 @@ color:navy">&gt;</span></p>
<span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: black">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .....</span><span lang="EN-US" style="font-size: 10.0pt; font-family: Courier New; color: navy">&gt;</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">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
...</span></font></p>
<span style="font-family: Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
...</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">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
@ -1172,9 +1172,9 @@ font-family:&quot;Courier New&quot;;color:navy">&nbsp;&lt;/toolChain&gt;</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>

36
doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltIndexes.html
View file

@ -541,8 +541,8 @@ table.MsoTableGrid
<p class=MsoTitle style='text-align:justify'><o:p>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</o:p></b></p>
<span class=MsoNormal style='text-align:justify;text-indent:36.0pt'><strong
style='mso-bidi-font-weight:normal'><o:p>&nbsp;</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

4
doc/org.eclipse.cdt.doc.isv/guide/dom/index/prebuiltVersioning.html
View file

@ -167,7 +167,7 @@ another.
<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.
</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>&nbsp;</b></p>
<span class=MsoNormal><strong>&nbsp;</strong></span>
</td>
</tr>
<tr style='mso-yfti-irow:1'>

2128
doc/org.eclipse.cdt.doc.isv/guide/mbs/extensibilityGuide/Managed_Build_Extensibility.html
View file

File diff suppressed because it is too large Load diff

40
doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtodeveloptemplates.html
View file

@ -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>

4
doc/org.eclipse.cdt.doc.isv/guide/projectTemplateEngine/Howtoregistertemplates.html
View file

@ -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 &gt; Getting Started &gt; Basic Plug-in Tutorial
&gt; Plug-in manifest editor</i>.
&gt; Plug-in manifest editor</em>.
</p>
<li>
<p>

107
doc/org.eclipse.cdt.doc.user/book.css
View file

@ -1,51 +1,56 @@
/* following font face declarations need to be removed for DBCS */
body, h1, h2, h3, h4, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, 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, 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 { font-size: 10pt; }
pre { margin-left: 6; font-size: 9pt }
a:link { color: #006699 }
a:visited { color: #996699 }
a:hover { color: #006699 }
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 }
/* Mike Behm's addition to the style sheet */
.userinput { font-family: monospace; }
.guitab, .important, .guibutton, .selectblue, .guimenu, .guilabel,
.notetitle {
color: #000000;
font-family: helvetica, arial, sans-serif;
font-weight: bold;
}
div.linux {display:none;}
.firsterm {font-style:italic;}
/* following font face declarations need to be removed for DBCS */
body, h1, h2, h3, h4, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, 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, 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 { font-size: 10pt; }
pre { margin-left: 6; font-size: 9pt }
a:link { color: #006699 }
a:visited { color: #996699 }
a:hover { color: #006699 }
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 }
/* Mike Behm's addition to the style sheet */
.userinput { font-family: monospace; }
.guitab, .important, .guibutton, .selectblue, .guimenu, .guilabel,
.notetitle {
color: #000000;
font-family: helvetica, arial, sans-serif;
font-weight: bold;
}
div.linux {display:none;}
.firsterm {font-style:italic;}
.typewriter {font-family:monospace;}
.bold {font-weight:600;}
.linethrough {text-decoration: line-through;}
.underline {text-decoration: underline;}

6
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_before_you_begin.htm
View file

@ -28,7 +28,7 @@ For instructions about installing the GNU toolchain for Linux, see the instructi
<h3>Windows</h3>
<p>For windows, MinGW, and Cygwin are the two main choices for acquiring the GNU toolchain:</p>
<ul>
<li><a href="http://www.cygwin.com"><b>Cygwin</b></a> is a port of the Linux environment to Windows.
<li><a href="http://www.cygwin.com"><strong>Cygwin</strong></a> is a port of the Linux environment to Windows.
It provides a compatibility layer in a set of DLLs. These DLLs are
<a href="http://www.gnu.org/copyleft/gpl.html">GPL licensed</a>,
making any code that links to them also subject to the GPL.
@ -38,7 +38,7 @@ Note: currently Cygwin &gt;= version 3.4.4-999 is not supported since gcc and g+
be launched from the windows' native shell.
<p> <br></p>
</li>
<li><p><a href="http://www.mingw.org"><b>MinGW</b></a> is a port of the GNU toolchain to the Windows platform.
<li><p><a href="http://www.mingw.org"><strong>MinGW</strong></a> is a port of the GNU toolchain to the Windows platform.
The biggest difference over Cygwin is that MinGW uses the Windows C runtime libraries (mscvrt) instead
of GNU's libc. As a result, a compatibility layer is not required, thus avoiding the GPL issues
with Cygwin. There are differences, though, between the Windows and GNU C runtime libraries that will make
@ -59,7 +59,7 @@ MinGW File Release</a> section for the latest versions.</p>
<li>Select download and install the MinGW base tools and the g++ compiler.
You may select the Current or Candidate version of these tools.
You may also install any of the other available compilers as well.
<p><b>Do not install the MinGW Make feature</b> as the MSYS version of make from step 5
<p><strong>Do not install the MinGW Make feature</strong> as the MSYS version of make from step 5
is a more complete implementation of make.</p></li>
<li>The MinGW setup program currently does not install the gdb debugger.
To install the debugger, download the file from the following location:

14
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_brkpnts.htm
View file

@ -13,13 +13,13 @@
<p>A breakpoint suspends the execution of a program at the location where the breakpoint is set.
To set a line breakpoint, right-click in the marker bar area on the left side of an editor beside
the line where you want the program to be suspended, then choose <b>Toggle Breakpoint</b>. You can
the line where you want the program to be suspended, then choose <strong>Toggle Breakpoint</strong>. You can
also double-click on the marker bar next to the source code line. A new breakpoint marker appears
on the marker bar, directly to the left of the line where you added the breakpoint. Also, the new
breakpoint appears in the Breakpoints view list.
</p>
<p>Once set, a breakpoint can be enabled and disabled by right-clicking on its icon or by
right-clicking on its description in the <b>Breakpoints</b> view.
right-clicking on its description in the <strong>Breakpoints</strong> view.
</p>
<ul>
@ -37,11 +37,11 @@ Disabled breakpoints are indicated with a white
<p><b>Note: </b>Execution will also suspend
if <b>Stop at main() on startup</b> is enabled
on the <b>Launch Configuration</b> dialog.
To access the <b>Launch Configuration</b> dialog,
from the menu bar choose <b>Run > Debug</b>.
<p><strong>Note: </strong>Execution will also suspend
if <strong>Stop at main() on startup</strong> is enabled
on the <strong>Launch Configuration</strong> dialog.
To access the <strong>Launch Configuration</strong> dialog,
from the menu bar choose <strong>Run > Debug</strong>.
</p>
<hr>

74
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_build_over.htm
View file

@ -21,13 +21,13 @@ project and providing the makefile yourself.</p>
<li>Compile (e.g. gcc).</li>
<li>Debug (e.g. gdb).</li>
</ul>
<b>Note: </b> while make, gcc and gdb are the examples used in the
<strong>Note: </strong> while make, gcc and gdb are the examples used in the
documentation, virtually any similar set of tools or utilities could be
used.
<p></p>
<p><b>Tip: </b>Cygwin contains these utilities (make, gcc and gdb) for
<p><strong>Tip: </strong>Cygwin contains these utilities (make, gcc and gdb) for
a Windows environment.&nbsp; While running the cygwin installation,
ensure <tt>gcc</tt> and <tt>make</tt> are selected since they are not
ensure <span class="typewriter">gcc</span> and <span class="typewriter">make</span> are selected since they are not
installed by default. For more information, see <a
href="http://www.cygwin.com">http://www.cygwin.com</a>. If you are a
Red Hat user, all that you need to do to build your project is included
@ -46,8 +46,8 @@ particular project are built.</p>
modified since the last build. A rebuild is a clean followed by a build.</p>
<p>For more information on builds, see:</p>
<ul>
<li><b>Workbench User Guide &gt; Concepts &gt; Workbench &gt; Builds</b></li>
<li><b>Workbench User Guide &gt; Tasks &gt; Building resources</b></li>
<li><strong>Workbench User Guide &gt; Concepts &gt; Workbench &gt; Builds</strong></li>
<li><strong>Workbench User Guide &gt; Tasks &gt; Building resources</strong></li>
</ul>
<p>Build-related information is displayed as follows:</p>
<ul>
@ -57,67 +57,67 @@ related to your projects.</li>
<li>For Standard Make projects, the Makefile targets are displayed in
the Make Targets view.</li>
</ul>
<p>For more information about the Tasks view, see <b>Workbench User
<p>For more information about the Tasks view, see <strong>Workbench User
Guide &gt; Reference &gt; User interface information &gt; Views and
editors &gt; Tasks view</b>.</p>
editors &gt; Tasks view</strong>.</p>
<h2>Getting a makefile</h2>
<p>You can either create a C/C++ project for which you supply the <b>makefile</b>
<p>You can either create a C/C++ project for which you supply the <strong>makefile</strong>
or create a C/C++ project for which the CDT generates makefiles
automatically.</p>
<p>To create a new project, from the menu bar choose <b>File &gt; New
&gt; Project</b>. In the dialog that appears, expand the C/C++ group
<p>To create a new project, from the menu bar choose <strong>File &gt; New
&gt; Project</strong>. In the dialog that appears, expand the C/C++ group
and choose e.g. C Project</p>
<ul>
<li>In the resulting wizard page, to create a project for which you supply the <b>makefile</b>,
select <b>Makefile project</b> and choose one of the alternatives under that.
<li>In the resulting wizard page, to create a project for which you supply the <strong>makefile</strong>,
select <strong>Makefile project</strong> and choose one of the alternatives under that.
An empty project, or a simple "Hello World" can be created.
You edit and manage the makefile yourself.
<p>&nbsp;</p>
</li>
<li>To create a project for which the CDT supplies a basic <b>makefile</b>,
select another project type, e.g. <b>Executable</b> and choose one of the examples
under that, or choose <b>Empty Project</b>.
<li>To create a project for which the CDT supplies a basic <strong>makefile</strong>,
select another project type, e.g. <strong>Executable</strong> and choose one of the examples
under that, or choose <strong>Empty Project</strong>.
</li>
</ul>
<h2>Setting build preferences</h2>
<p>You can set build preferences in Eclipse:</p>
<dl>
<dt>Build order</dt>
<dd>If certain projects must be built before others, you can set the <i>build
order</i>. If your project refers to another project, the CDT must
<dd>If certain projects must be built before others, you can set the <em>build
order</em>. If your project refers to another project, the CDT must
build the other project first. To set the build order, from the menu
bar select <b>Window &gt; Preferences</b> and choose <b> General > Preferences > Build Order</b>.
bar select <strong>Window &gt; Preferences</strong> and choose <strong> General > Preferences > Build Order</strong>.
<p>When you set the build order, the CDT does not rebuild projects
that depend on a project; you must rebuild all projects to ensure all
changes are propagated.</p>
</dd>
<dt>Automatic save</dt>
<dd>You can set the CDT to perform an <i>automatic save</i> of all
<dd>You can set the CDT to perform an <em>automatic save</em> of all
modified resources when you perform a manual build. In the preferences dialog,
select <b>General > Workspace</b> and check <b>Save automatically before build</b>.
select <strong>General > Workspace</strong> and check <strong>Save automatically before build</strong>.
By default,
this feature is <i>not</i> enabled.</dd>
this feature is <em>not</em> enabled.</dd>
</dl>
<h2>Controlling the building of your project</h2>
<p>For a Makefile project, the C/C++ compiler that a project uses
is controlled by the project's <b>Properties</b> setting.
To view a project's properties, right-click on the project and select <b>Properties</b>.
In the dialog that appears, the <b>C/C++ Build</b>
is controlled by the project's <strong>Properties</strong> setting.
To view a project's properties, right-click on the project and select <strong>Properties</strong>.
In the dialog that appears, the <strong>C/C++ Build</strong>
page enables you to control a variety of settings, including:</p>
<dl>
<dt>Build Command</dt>
<dd>On the <b>Builder Settings</b> tab, this controls which <code>make</code> is used. To change it, uncheck <b>Use
default build command</b> and change it or add arguments to the make command.</dd>
<dd>On the <strong>Builder Settings</strong> tab, this controls which <code>make</code> is used. To change it, uncheck <strong>Use
default build command</strong> and change it or add arguments to the make command.</dd>
<dt>Build Setting</dt>
<dd>On the <b>Behaviour</b> tab, this controls whether the compiler will <b>Stop on first build error</b> or not
(keep going). Unchecking <b>Stop on first build error</b> will force the compiler to attempt to build all referenced
<dd>On the <strong>Behaviour</strong> tab, this controls whether the compiler will <strong>Stop on first build error</strong> or not
(keep going). Unchecking <strong>Stop on first build error</strong> will force the compiler to attempt to build all referenced
projects even if the current project has errors.</dd>
<dt>Workbench Build Behavior</dt>
<dd>On the <b>Behaviour </b> tab, this controls which makefile target will be built depending on the scope of the
<dd>On the <strong>Behaviour </strong> tab, this controls which makefile target will be built depending on the scope of the
build, e.g. <code>all</code> or <code>clean</code>.</dd>
</dl>
<p>For a standard (non-Makefile) project (often called "Managed Build" or "Managed Make" project from
@ -125,19 +125,19 @@ earlier CDT version), the project properties dialog enables
you to manage the build configurations of your project. For additional
information see:</p>
<ul>
<li><b>Reference &gt; C/C++ Properties &gt; C/C++ Project Properties &gt; Managed Make
Projects</b></li>
<li><b>Reference &gt; C/C++ Properties &gt; C/C++ Project Properties &gt; Managed Make File
Properties</b></li>
<li><strong>Reference &gt; C/C++ Properties &gt; C/C++ Project Properties &gt; Managed Make
Projects</strong></li>
<li><strong>Reference &gt; C/C++ Properties &gt; C/C++ Project Properties &gt; Managed Make File
Properties</strong></li>
</ul>
<h2>Viewing build information</h2>
<p>Build-related information is displayed as follows: </p>
<ul>
<li>The <b>Console</b> view displays the output of the make utility.</li>
<li>The <b>Tasks</b> view displays a list of compiler errors and
<li>The <strong>Console</strong> view displays the output of the make utility.</li>
<li>The <strong>Tasks</strong> view displays a list of compiler errors and
warnings related to your projects. </li>
<li>For a Standard Make project, build actions display in the <b>Make
Targets</b> view.</li>
<li>For a Standard Make project, build actions display in the <strong>Make
Targets</strong> view.</li>
</ul>
<p><img border="0" src="../images/ngconcepts.gif" alt="Related concepts"
width="143" height="21">

10
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_comments.htm
View file

@ -21,18 +21,18 @@ Two styles of comments are supported by current C/C++ compilers:</p>
<h3>Comment</h3>
<p>You can quickly comment out one or more lines of code by inserting the leading
characters <samp>//</samp> at the beginning of the line. To do so, select the line
(or lines) of code you want to comment out and press <b>CTRL+/</b> (slash).</p>
(or lines) of code you want to comment out and press <strong>CTRL+/</strong> (slash).</p>
<h3>Uncomment</h3>
<p>To uncomment select the line (or lines) of code, and press <b>CTRL+\</b>
<p>To uncomment select the line (or lines) of code, and press <strong>CTRL+\</strong>
(backslash).
<p><b>Tip:</b> The characters <samp>/* */</samp> on lines that are
<p><strong>Tip:</strong> The characters <samp>/* */</samp> on lines that are
already commented out, are not affected when you comment and uncomment code.</p>
<h3>Multiline comment</h3>
<p>You can use the Content Assist feature to insert a multi-line comment before a function.
Type <tt>com+Ctrl+Space</tt>, and the following code is entered at the cursor location:
Type <span class="typewriter">com+Ctrl+Space</span>, and the following code is entered at the cursor location:
<br><pre>
/*
* author userid
@ -42,7 +42,7 @@ Type <tt>com+Ctrl+Space</tt>, and the following code is entered at the cursor lo
*/
</pre>
To change the default comment click <b>Window > Preferences > C > Templates</b>. For more information see the
To change the default comment click <strong>Window > Preferences > C > Templates</strong>. For more information see the
<a href="cdt_c_content_assist.htm">Content Assist</a> section.
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">

8
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_content_assist.htm
View file

@ -34,8 +34,8 @@ the relevance of each proposal is determined in the following order:</p>
<li>Enumerations</li>
</ul>
You trigger the Code completion feature when you call Content Assist (such as when you type <tt>Ctrl+Space</tt>), but it is auto-activated when you type
&quot;<b>.</b>&quot;, &quot;<b>-></b>&quot; or &quot;<b>::</b>&quot;.</p>
You trigger the Code completion feature when you call Content Assist (such as when you type <span class="typewriter">Ctrl+Space</span>), but it is auto-activated when you type
&quot;<strong>.</strong>&quot;, &quot;<strong>-></strong>&quot; or &quot;<strong>::</strong>&quot;.</p>
<p><img src="../images/contentAssist_example.png" alt="C++ example showing Code Assist popup"></p>
@ -46,7 +46,7 @@ You trigger the Code completion feature when you call Content Assist (such as wh
<p>You can create and save templates for frequently used sections of code, which will be inserted according to scope. The Content Assist feature also provides quick access to code
templates.</p>
<p>When you enter a letter combination in the C/C++ editor, and type <tt>CTRL+SPACE</tt> (or right-click and click <b>Content Assist</b>), a
<p>When you enter a letter combination in the C/C++ editor, and type <span class="typewriter">CTRL+SPACE</span> (or right-click and click <strong>Content Assist</strong>), a
list of code elements and templates that start with the letter combination that you typed is displayed.</p>
<p>You can then select a template from the list and it is inserted directly into your code.</p>
@ -64,7 +64,7 @@ list of code elements and templates that start with the letter combination that
<p>If the completion engine finds only one proposal in your templates, that proposal is inserted at the current cursor position.
For example if you create a new .cpp file and type <tt>mai+CTRL+SPACE</tt> the following code is inserted at the cursor location:</p>
For example if you create a new .cpp file and type <span class="typewriter">mai+CTRL+SPACE</span> the following code is inserted at the cursor location:</p>
<p><pre>int
main(int argc, char **argv) {

8
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_dbg_info.htm
View file

@ -14,11 +14,11 @@
<h1>Debug information</h1>
<p>The <b>Debug</b> perspective lets you manage the debugging or running of a program
<p>The <strong>Debug</strong> perspective lets you manage the debugging or running of a program
in the Workbench. You can control the execution of your program by setting
breakpoints, suspending launched programs, stepping through your code, and
examining the contents of variables.</p>
<p>&nbsp;The <b>Debug</b> perspective displays the following information:</p>
<p>&nbsp;The <strong>Debug</strong> perspective displays the following information:</p>
<ul>
<li>The stack frame for the suspended threads
@ -26,8 +26,8 @@ for each target that you are debugging</li>
<li>Each thread in your program represented as a node in the tree</li>
<li>The process for each program that you are running</li>
</ul>
<p>The <b>Debug</b> perspective also drives the <b>C/C++ Editor</b>. As you step
through your program, the <b>C/C++ Editor</b> highlights the location of the
<p>The <strong>Debug</strong> perspective also drives the <strong>C/C++ Editor</strong>. As you step
through your program, the <strong>C/C++ Editor</strong> highlights the location of the
execution pointer. </p>
<h2>Variables</h2>

6
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_discovery_options.htm
View file

@ -13,13 +13,13 @@
<p>For projects where the IDE generates a makefile to build the project automatically, the IDE has more information about the internal build state of the make project compared to those projects where you provide a makefile to build the project.
<p>For example, a makefile includes build information and other settings, such as include file paths (-I) and macro definitions (-D), which are standard to the build tools (such as the compiler and linker). When the makefile is automatically created for you, this information is known to Eclipse to a greater extent then when you create and manage the makefile for a project yourself. The type of information affects the search capabilities and Code Assist abilities of Eclipse. Therefore, in this example, the purpose of Discovery Options is for improved search and Code Assist capability for projects where Eclipse does not manage the makefile for you. For example, in an open source file of an editor view, to see the declaration for a function that the code calls, you select the function, right click, and select <b>Open Declaration</b> from the context menu. If the location of the include file (that was coded in the makefile for the project) containing the function declaration was in some directory, the CDT would not find the declaration because it has no visibility for that include path. Consequently, you can use Discovery Options in the CDT to enhance the IDE build state by parsing the build process output to extract build path information that the CDT searching mechanism uses to locate and open the include file. By default, the CDT uses GNU* tools (gcc, etc.). If you want to build your projects using another compiler, use the settings described here.</p>
<p>For example, a makefile includes build information and other settings, such as include file paths (-I) and macro definitions (-D), which are standard to the build tools (such as the compiler and linker). When the makefile is automatically created for you, this information is known to Eclipse to a greater extent then when you create and manage the makefile for a project yourself. The type of information affects the search capabilities and Code Assist abilities of Eclipse. Therefore, in this example, the purpose of Discovery Options is for improved search and Code Assist capability for projects where Eclipse does not manage the makefile for you. For example, in an open source file of an editor view, to see the declaration for a function that the code calls, you select the function, right click, and select <strong>Open Declaration</strong> from the context menu. If the location of the include file (that was coded in the makefile for the project) containing the function declaration was in some directory, the CDT would not find the declaration because it has no visibility for that include path. Consequently, you can use Discovery Options in the CDT to enhance the IDE build state by parsing the build process output to extract build path information that the CDT searching mechanism uses to locate and open the include file. By default, the CDT uses GNU* tools (gcc, etc.). If you want to build your projects using another compiler, use the settings described here.</p>
<p>Scanner configuration discovery is tightly linked to project's build process. The first part of scanner discovery begins during the make build for make projects where you provide the makefile. The Eclipse CDT parses the build output for compiler commands with options that specify the definition of the preprocessor symbols and include search paths (for the gcc compiler, -D and -I), and then it stores the information as the project's discovered scanner configuration.
<p>Next, after the build process completes, it is implemented as a separate Eclipse builder where it runs a generate scanner info command, and then parses the output (properties specified on the Discover Options tab for Builds in the Project Properties window).
<p>For C++, the default generate scanner information command is <b>gcc -E -P -v myfile.c | myfile.cpp</b>. This command reads the compiler's configuration file and prints the information that includes compiler's internally defined preprocessor symbols and include search paths.
<p>For C++, the default generate scanner information command is <strong>gcc -E -P -v myfile.c | myfile.cpp</strong>. This command reads the compiler's configuration file and prints the information that includes compiler's internally defined preprocessor symbols and include search paths.
<p>A single scanner configuration is applicable to all the files in a project. Although Eclipse discovers the information for each compilation unit, it stores the scanner configuration on a per project basis. This means that Eclipse applies a single, cumulative scanner configuration to all files in a project.
@ -31,7 +31,7 @@
</ul>
</p>
<p><b>Note:</b> Only basic command line options are supported. In addition, only basic scanner configuration related command line options are recognized (for example, -D and -I for gcc). For some of the commands, their relative position in the command line is important. For information about these options, see the documentation for the utilities you are using.
<p><strong>Note:</strong> Only basic command line options are supported. In addition, only basic scanner configuration related command line options are recognized (for example, -D and -I for gcc). For some of the commands, their relative position in the command line is important. For information about these options, see the documentation for the utilities you are using.
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br><a href="cdt_c_over_cdt.htm">CDT Overview</a>

2
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_editor.htm
View file

@ -21,7 +21,7 @@ This C/C++ editor is invoked automatically when you edit a C/C++ source file.</p
<li>Integrated debugging features</li>
</ul>
<p>You can customize some of the operation of the Editor view from the <b>Window &gt; Preferences &gt; C/C++ &gt; Editor</b> preferences dialog.</p>
<p>You can customize some of the operation of the Editor view from the <strong>Window &gt; Preferences &gt; C/C++ &gt; Editor</strong> preferences dialog.</p>

14
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_makefile.htm
View file

@ -102,7 +102,7 @@ Test2.o : Test2.h
<h2>Frequently Asked Questions:</h2>
Your Console view can be very useful for debugging a build.
<p><font size="+1"><b>Q1</b>. My Console view says <tt>"Error launching builder"</tt>. What does that mean?<p></font>
<p><h5><strong>Q1</strong>. My Console view says <span class="typewriter">"Error launching builder"</span>. What does that mean?<p></h5>
<pre>
Error launching builder (make -k clean all )
(Exec error:Launching failed)
@ -111,7 +111,7 @@ Error launching builder (make -k clean all )
<p>Most probably, the build command (by default "make") is not on your path. You can put it on your path and restart Eclipse.<br>
You can also change the build command to something that is on your path. If you are using MinGW tools to compile, you should replace the build command with "mingw32-make".</p>
<p><font size="+1"><b>Q2</b>. My Console view says <tt>"No rule to make target 'X'"</tt>.</p></font>
<p><h5><strong>Q2</strong>. My Console view says <span class="typewriter">"No rule to make target 'X'"</span>.</p></h5>
<pre>
make -k clean all
make: *** No rule to make target 'clean'.
@ -124,11 +124,11 @@ contain rules for the command line goals ("clean" and "all" in this case), it wi
with an error message similar to those shown. </p>
<p>If you already have a valid Makefile, you may need to change the working directory of your build. The default working directory for the build command is the project's root directory. You can change this by specifying an alternate Build Directory in the Make Project properties.
Or, if your Makefile is named something else (eg. <tt>buildFile.mk</tt>), you can specify the name by setting the default Build command to <tt>make -f buildFile.mk</tt>.</p>
Or, if your Makefile is named something else (eg. <span class="typewriter">buildFile.mk</span>), you can specify the name by setting the default Build command to <span class="typewriter">make -f buildFile.mk</span>.</p>
<p>If you do not have a valid Makefile, create a new file named Makefile in the root directory. You can then add the contents of the sample Makefile (above), and modify it as appropriate.</p>
<p><font size="+1"><b>Q3</b>. My Console view says <tt>"missing separator"</tt>.</p></font>
<p><h5><strong>Q3</strong>. My Console view says <span class="typewriter">"missing separator"</span>.</p></h5>
<pre>
make -k clean all
makefile:12: *** missing separator. Stop.
@ -138,7 +138,7 @@ This Tab character is often accidentally replaced with spaces, and because both
this problem is easily overlooked. In the sample provided, the error message can be pinpointed to line 12 of the
file "makefile"; to fix the problem, insert a tab at the beginning of that line.</p>
<p><font size="+1"><b>Q4</b>. My Console view says <tt>"Target 'all' not remade because of errors"</tt>.</p></font>
<p><h5><strong>Q4</strong>. My Console view says <span class="typewriter">"Target 'all' not remade because of errors"</span>.</p></h5>
<pre>
make -k clean all
make: *** [clean] Error 255
@ -155,13 +155,13 @@ make: Target 'all' not remade because of errors.
<p>The Error 255 is produced by make as a result of its command shell not being able to find a command for a particular rule.<br>
Messages from the standard error stream (the lines saying Error 255) and standard output stream (all the other lines) are merged in the Console view here.</p>
<p><font size="+1"><b>Q5</b>. What's with the -k flag?</p></font>
<p><h5><strong>Q5</strong>. What's with the -k flag?</p></h5>
<p>The -k flag tells make to continue making other independent rules even when one rule fails.
This is helpful for build large projects.</p>
<p>You can remove the -k flag by turning on Project Properties > C/C++ Make Project > Make Builder > Stop on first build error</p>
<p><font size="+1"><b>Q6</b>. My Console view looks like:</p></font>
<p><h5><strong>Q6</strong>. My Console view looks like:</p></h5>
<pre>
mingw32-make clean all
process_begin: CreateProcess((null), rm -f Test1.o Test2.o Main.o test_me.exe, ...) failed.

8
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_outlineview.htm
View file

@ -47,8 +47,8 @@ editor highlights both the selected item and the marker bar (left margin). For e
to the start of main() in the C/C++ editor, click <samp>main()</samp> in the Outline
view.</p>
<p>For more information about the marker bar, see <b>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Views and editors &gt; Editor area</b>.</p>
<p>For more information about the marker bar, see <strong>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Views and editors &gt; Editor area</strong>.</p>
<h2>Filtering the Outline View</h2>
@ -91,8 +91,8 @@ items:</p>
</tr>
</table></p>
<p>For more information about the Eclipse workbench, see <b>Workbench User Guide &gt; Tasks &gt; Upgrading Eclipse</b>.</p>
<p>For more information about Working sets, see <b>Workbench User Guide &gt; Concepts &gt; Working sets</b>.</p>
<p>For more information about the Eclipse workbench, see <strong>Workbench User Guide &gt; Tasks &gt; Upgrading Eclipse</strong>.</p>
<p>For more information about Working sets, see <strong>Workbench User Guide &gt; Concepts &gt; Working sets</strong>.</p>
</ul>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">

12
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_over_cdt.htm
View file

@ -11,7 +11,7 @@
<h1>CDT Overview</h1>
<p>The C/C++ Development Toolkit (CDT) is a set of Eclipse plug-ins that provide
C and C++ extensions to the Eclipse workbench. For more information about
Eclipse, see <b>Workbench User Guide &gt; Concepts &gt; Workbench</b>.</p>
Eclipse, see <strong>Workbench User Guide &gt; Concepts &gt; Workbench</strong>.</p>
<p>The CDT provides a C/C++ IDE that simplifies many of the same tools that you can use from the command line. The CDT can also communicate with many external utilities and interpret their responses, for example:
<ul>
@ -19,7 +19,7 @@ Eclipse, see <b>Workbench User Guide &gt; Concepts &gt; Workbench</b>.</p>
<li>Compile (such as gcc). For more information, see <a href="http://gcc.gnu.org">http://gcc.gnu.org</a>.</li>
<li>Debug (such as gdb). For more information, see <a href="http://sources.redhat.com/gdb/">http://sources.redhat.com/gdb/</a>.</li>
</ul>
<b>Note: </b> while make, gcc and gdb are the examples used in the documentation, virtually any similar set of tools or utilities could be used.</p>
<strong>Note: </strong> while make, gcc and gdb are the examples used in the documentation, virtually any similar set of tools or utilities could be used.</p>
<p>The CDT opens as the C/C++ perspective of the Eclipse workbench. The
@ -36,15 +36,15 @@ views:</p>
<dt>Search</dt><dd>Shows the results of searches for files or text.</dd>
<dt>Tasks</dt> <dd>Lists tasks that you want to keep track of, either as a schedule of things to do or a history of things that have been done.</dd>
</dl>
<p>For more information, see <b>Workbench User Guide &gt; Concepts &gt; Perspectives</b>.</p>
<p>For more information, see <strong>Workbench User Guide &gt; Concepts &gt; Perspectives</strong>.</p>
<h3>CDT updates</h3>
<p>The <b>Install/Update</b> wizard provides information about your current Eclipse installation and provides the framework to manage your updates.
For more information, see <b>Workbench User Guide &gt; Tasks &gt; Updating and installing software</b>.</p>
<p>The <strong>Install/Update</strong> wizard provides information about your current Eclipse installation and provides the framework to manage your updates.
For more information, see <strong>Workbench User Guide &gt; Tasks &gt; Updating and installing software</strong>.</p>
<p>To view a list of the updates available for the toolsets that you
installed, click <b>Help &gt; Check for Updates</b>.</p>
installed, click <strong>Help &gt; Check for Updates</strong>.</p>
<h3>Additional information</h3>

2
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_over_dbg.htm
View file

@ -23,7 +23,7 @@ generated from that original source.</p>
<p>The CDT debugger uses GDB as the underlying debug engine. It translates each
user interface action into a sequence of GDB commands and processes the output from GDB to
display the current state of the program being debugged. </p>
<p><b>Tip:</b> Editing the source after compiling causes the line numbering to be out of
<p><strong>Tip:</strong> Editing the source after compiling causes the line numbering to be out of
step because the debug information is tied directly to the source. Similarly,
debugging optimized binaries can also cause unexpected jumps in the execution
trace.</p>

8
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_perspectives.htm
View file

@ -14,16 +14,16 @@
<p>A perspective is a layout of <a href="cdt_c_views.htm">views</a> (development tools) in the Workbench window.
Each type of perspective is a combination of views, menus, and toolbars that enable you to perform a particular task.
For example, the C/C++ perspective has views that are organized to help you develop C/C++ programs;
the <b>Debug</b> perspective has views that enable you to debug those programs.
the <strong>Debug</strong> perspective has views that enable you to debug those programs.
</p>
<p>To Open the C/C++ Perspective, select Window > Open Perspective > Other... and select C/C++</p>
<div class="note">
<b>Selecting / Opening Views:</b>
<strong>Selecting / Opening Views:</strong>
<ul>
<li>You can add views to a perspective. From the menu bar choose <b>Window &gt; Show View &gt; Other</b> and select a new view from the <b>Show View</b> dialog.</li>
<li>To reset the current perspective to its original layout, from the menu bar choose <b>Window &gt; Reset Perspective</b>.</li>
<li>You can add views to a perspective. From the menu bar choose <strong>Window &gt; Show View &gt; Other</strong> and select a new view from the <strong>Show View</strong> dialog.</li>
<li>To reset the current perspective to its original layout, from the menu bar choose <strong>Window &gt; Reset Perspective</strong>.</li>
</ul>
</div>

26
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_projects.htm
View file

@ -15,7 +15,7 @@
source code, makefiles, binaries, and related files. C/C++ projects are displayed
in the C/C++ Projects view.</p>
<p><b>Tip:</b> Nested projects are not supported. Each project must be organized as a
<p><strong>Tip:</strong> Nested projects are not supported. Each project must be organized as a
discrete entity. Project dependencies are supported by allowing a project
to reference other projects that reside in your workspace. For more information,
see <a href="../reference/cdt_u_prop_general_pns_ref.htm">Selecting referenced projects</a>.</p>
@ -23,8 +23,8 @@ see <a href="../reference/cdt_u_prop_general_pns_ref.htm">Selecting referenced p
<p>For more information about projects and where they are stored, see:</p>
<ul>
<li> <b>Workbench User Guide &gt; Tasks &gt; Resources</b></li>
<li> <b>Workbench User Guide &gt; Tasks &gt; Running Eclipse</b></li>
<li> <strong>Workbench User Guide &gt; Tasks &gt; Resources</strong></li>
<li> <strong>Workbench User Guide &gt; Tasks &gt; Running Eclipse</strong></li>
</ul>
<h2>Project types</h2>
@ -39,22 +39,22 @@ at any time for existing project. Use <a href="../reference/cdt_o_proj_prop_page
<p>When you create a new project, you are required to specify the project type. This project type will determine the toolchain and data, and tabs that the CDT uses. In the New CDT Project Wizard, you can choose from the following project types:</p>
<ul>
<li><b>Executable</b> - Provides an executable application. This project type folder contains three templates.</p>
<li><strong>Executable</strong> - Provides an executable application. This project type folder contains three templates.</p>
<ul>
<li><b>Hello World C++ Example</b> provides a simple C++ Hello World application with main().
<li><b>Hello World ANSI C Example</b> provides a simple C Hello World application with main().<li><b>Empty Project</b> provides a single source project folder that contains no files.
<li><strong>Hello World C++ Example</strong> provides a simple C++ Hello World application with main().
<li><strong>Hello World ANSI C Example</strong> provides a simple C Hello World application with main().<li><strong>Empty Project</strong> provides a single source project folder that contains no files.
</ul>
<p>After you select a template, the result is a project with only the meta-data files required for the project type. You are expected to modify these source files, as required, and provide source files for the project's target.</p><p>The makefile for the <b>Executable</b> project type is automatically created by the CDT.</p>
<li><b>Shared Library</b> - An executable module that is compiled and linked separately. When you create a project that uses a shared library (libxx.so), you define your shared library's project as a Project Reference for your application. For this project type, the CDT combines object files together and joins them so they're relocatable and can be shared by many processes. Shared libraries are named using the format
<p>After you select a template, the result is a project with only the meta-data files required for the project type. You are expected to modify these source files, as required, and provide source files for the project's target.</p><p>The makefile for the <strong>Executable</strong> project type is automatically created by the CDT.</p>
<li><strong>Shared Library</strong> - An executable module that is compiled and linked separately. When you create a project that uses a shared library (libxx.so), you define your shared library's project as a Project Reference for your application. For this project type, the CDT combines object files together and joins them so they're relocatable and can be shared by many processes. Shared libraries are named using the format
libxx.so.<var>version</var>, where
<var>version</var> is a number with a default of 1. The
libxx.so file usually is a symbolic link to the
latest version.</p><p>The makefile for this project type is automatically created by the CDT.
<li><b>Static Library</b> - A collection of object files that you can link into another application (libxx.a). The CDT combines object files (i.e. *.o)
<li><strong>Static Library</strong> - A collection of object files that you can link into another application (libxx.a). The CDT combines object files (i.e. *.o)
into an archive (*.a) that is directly linked into an
executable.</p><p>The makefile for this project type is automatically created by the CDT.
<li><b>Makefile Project</b> - Creates an empty project without the meta-data files. This selection is useful for importing and modifying existing makefile-based projects; a new makefile is not created for this project type.
<li><strong>Makefile Project</strong> - Creates an empty project without the meta-data files. This selection is useful for importing and modifying existing makefile-based projects; a new makefile is not created for this project type.
</ul>
<h2>Project conversion</h2>
@ -69,8 +69,8 @@ resolves any source control issues.</p>
<ul>
<li>When you create a file within a project, a record (local history) of
every change is created. For more information about local history, see
<b>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Development environment &gt; Local history</b>.</li>
<strong>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Development environment &gt; Local history</strong>.</li>
<li>Spaces in projects and filenames can cause problems with some
tools, such as the make utility or the compiler.</li>
<li>Be careful when you use only case to distinguish files and projects. UNIX-based
@ -79,7 +79,7 @@ hello.c are separate files in UNIX but overwrite each other in Windows.</li>
</ul>
<p>For more information about projects, see <b>Workbench User Guide &gt; Concepts &gt; Workbench &gt; Resources</b>.</p>
<p>For more information about projects, see <strong>Workbench User Guide &gt; Concepts &gt; Workbench &gt; Resources</strong>.</p>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">

24
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_search.htm
View file

@ -32,7 +32,7 @@ through the use of search delimiters, correct syntax, and wildcards.</p>
</ul>
</p>
For information on working sets, see <b>Workbench User Guide &gt; Concepts &gt; Workbench &gt; Working sets</b><br>
For information on working sets, see <strong>Workbench User Guide &gt; Concepts &gt; Workbench &gt; Working sets</strong><br>
<h2>What you can search for</h2>
@ -42,8 +42,8 @@ For information on working sets, see <b>Workbench User Guide &gt; Concepts &gt;
specify. If you choose to search for matching elements, all types, macros, and typdefs are included in the search.</p>
<table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="60%">
<tr>
<td width="19%"><b>Element</b></td>
<td width="81%"><b>Note</b></td>
<td width="19%"><strong>Element</strong></td>
<td width="81%"><strong>Note</strong></td>
</tr>
<tr>
<td width="19%">&nbsp;Class/Struct</td>
@ -119,13 +119,13 @@ is to be searched:</p>
<p>You can use wildcard characters to further refine your search.</p>
<table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="60%">
<tr>
<td width="49%"><b>Use this wildcard character</b></td>
<td width="51%"><b>To search for this</b></td>
<td width="49%"><strong>Use this wildcard character</strong></td>
<td width="51%"><strong>To search for this</strong></td>
</tr>
<tr>
<td width="49%">&nbsp;<samp>*</samp></td>
<td width="51%">Any string<p><b>Tip:<br>
</b> Use the character sequence <samp>\*</samp> to search for
<td width="51%">Any string<p><strong>Tip:<br>
</strong> Use the character sequence <samp>\*</samp> to search for
operators that begin with *. See syntax examples in the table below.</td>
</tr>
<tr>
@ -138,7 +138,7 @@ is to be searched:</p>
</tr>
</table>
<!-- no support for function parameters
<p><b>Tip: </b>Do not use wild cards between the brackets of a function or
<p><strong>Tip: </strong>Do not use wild cards between the brackets of a function or
method pattern. For example, the search
string <samp>f( * )</samp> is an invalid search that results in a search for any function <samp>f</samp>
because
@ -149,8 +149,8 @@ the asterisk is interpreted as a pointer rather than a wild card.</p>
to help you conduct an effective search.</p>
<table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="60%" height="400">
<tr>
<td width="64%" height="16"><b>Syntax</b></td>
<td width="36%" height="16"><b>Searches for this</b></td>
<td width="64%" height="16"><strong>Syntax</strong></td>
<td width="36%" height="16"><strong>Searches for this</strong></td>
</tr>
<tr>
<td width="64%" height="17">&nbsp; <samp>::*::*::A</samp></td>
@ -251,8 +251,8 @@ your last search.</p>
<p>For more information, see:<ul>
<li> <b>Workbench User Guide &gt; Concepts &gt; Views &gt; Search view</b></li>
<li> <b>Workbench User Guide &gt; Tasks &gt; Navigating and finding resources</b></li>
<li> <strong>Workbench User Guide &gt; Concepts &gt; Views &gt; Search view</strong></li>
<li> <strong>Workbench User Guide &gt; Tasks &gt; Navigating and finding resources</strong></li>
</ul>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21"><br>
<a href="../concepts/cdt_c_indexer.htm">C/C++ Indexer</a><br>

8
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_templates.htm
View file

@ -13,15 +13,15 @@
<p>Templates are sections of code that occur frequently enough that you would like
to be able to insert them with a few keystrokes.
This function is known as <b>Content Assist</b>; the sections of code that are
inserted are known as <b>templates</b>.
This function is known as <strong>Content Assist</strong>; the sections of code that are
inserted are known as <strong>templates</strong>.
</p>
<p>To input an existing Content Assist template into a file, such as one for an
<b>if</b> statement, type the initial character ("<tt>i</tt>" in this case), then press <b>Ctrl+Space</b>.
<strong>if</strong> statement, type the initial character ("<span class="typewriter">i</span>" in this case), then press <strong>Ctrl+Space</strong>.
The templates that begin with that character appear. Double-click on a template to insert it into a file.</p>
<p>You can edit existing Code/Content Assist templates or create new ones. From the menu bar choose
<b>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Templates</b>.</p>
<strong>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Templates</strong>.</p>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br><a href="cdt_c_over_cdt.htm">CDT Overview</a>

10
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_views.htm
View file

@ -12,15 +12,15 @@
<h1>Views in the C/C++ perspective</h1>
<p>The C/C++ views are panels that help you perform the tasks involved in creating C/C++ programs.
The <b>C/C++</b> perspective displays these panels in a single Eclipse window. </p>
The <strong>C/C++</strong> perspective displays these panels in a single Eclipse window. </p>
<b>Changing Views:</b>
<strong>Changing Views:</strong>
<ul>
<li>You can add views to a perspective. From the menu bar choose <b>Window > Show View > Other</b> and select a new view from the <b>Show View</b> dialog.</li>
<li>To reset the current perspective to its original layout, from the menu bar choose <b>Window > Reset Perspective</b>.</li>
<li>You can add views to a perspective. From the menu bar choose <strong>Window > Show View > Other</strong> and select a new view from the <strong>Show View</strong> dialog.</li>
<li>To reset the current perspective to its original layout, from the menu bar choose <strong>Window > Reset Perspective</strong>.</li>
</ul>
<p>The following views are commonly used in the <b>C/C++</b> perspective:</p>
<p>The following views are commonly used in the <strong>C/C++</strong> perspective:</p>
<dl>
<dt>Project Explorer</dt><dd>Shows all of the file system's files under your workspace directory.</dd>

52
doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew.htm
View file

@ -35,7 +35,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Rename in File</b></p>
<p align="right"><span class="bold">Rename in File</span></p>
</td>
<td>To make rename refactoring work interactively in the editor,
position the cursor on an identifier in the editor and hit Ctrl-1
@ -47,7 +47,7 @@ may contain other information.
<tr>
<td>
<p align="right"><b>Refactoring</b></p>
<p align="right"><span class="bold">Refactoring</span></p>
</td>
<td>"Extract local variable" is added via editor context menu.
Select an expression in the editor and select Refactor > Extract local variable
@ -63,7 +63,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Add Include </b></p>
<p align="right"><span class="bold">Add Include </span></p>
</td>
<td>Add Include significantly improved.
<ul>
@ -82,7 +82,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Outline View</b></p>
<p align="right"><span class="bold">Outline View</span></p>
</td>
<td>
<ul>
@ -108,7 +108,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b> Macro Exploration </b></p>
<p align="right"><span class="bold"> Macro Exploration </span></p>
</td>
<td>Improved Macro Exploration control.
<ul>
@ -121,7 +121,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Block selection mode </b></p>
<p align="right"><span class="bold">Block selection mode </span></p>
</td>
<td>Block selection mode now works in the CDT editor.
<p><img src="../images/60/CDT6.0_block_mode.png" alt="Block selection mode in editor">
@ -129,7 +129,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>C style block commenting</b></p>
<p align="right"><span class="bold">C style block commenting</span></p>
</td>
<td>C style block commenting (Ctrl-Shift-/) improved
<!-- <p><img src="../images/60/image.png" alt="alternate text for image for accessibility"> -->
@ -144,7 +144,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Implicit references and overloaded operators</b></p>
<p align="right"><span class="bold">Implicit references and overloaded operators</span></p>
</td>
<td>
<p></p>
@ -179,7 +179,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>System Includes</b></p>
<p align="right"><span class="bold">System Includes</span></p>
</td>
@ -197,7 +197,7 @@ may contain other information.
</tr>
<td>
<p align="right"><b>Indexer Accuracy</b></p>
<p align="right"><span class="bold">Indexer Accuracy</span></p>
</td>
<td>
<ul>
@ -219,7 +219,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Open Declaration</b></p>
<p align="right"><span class="bold">Open Declaration</span></p>
</td>
<td>Open Declaration (F3) improved, particularly for unresolved symbols.
<p>Open Declaration is capable of detecting potential matches.</p>
@ -237,7 +237,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Converters</b></p>
<p align="right"><span class="bold">Converters</span></p>
</td>
<td>
<ul>
@ -250,7 +250,7 @@ may contain other information.
<tr>
<tr>
<td>
<p align="right"><b>Working Sets</b></p>
<p align="right"><span class="bold">Working Sets</span></p>
</td>
<td>
<ul>
@ -274,7 +274,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Make Targets View</b></p>
<p align="right"><span class="bold">Make Targets View</span></p>
</td>
<td>
<ul>
@ -295,7 +295,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Error and Problem management</b></p>
<p align="right"><span class="bold">Error and Problem management</span></p>
</td>
<td>ErrorParserManager has been significantly simplified and improved. See <a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=264715">bug 264715 </a>and its subtasks.
@ -307,25 +307,25 @@ may contain other information.
<li>Improved performance.</li>
</ul>
<p><img src="../images/60/EPM-multi.png" alt="More accurate algorithm for associating errors/warnings from build output with files in the workspace">
<p>In the <b>Problems View</b>, external file locations (outside of the workspace) have been moved to the Location
<p>In the <strong>Problems View</strong>, external file locations (outside of the workspace) have been moved to the Location
column and associated with "Open External Location" menu.
<p><img src="../images/60/PV-extloc.png" alt="Open External Location from context menu in Problems View">
<ul>
<li>Remote Project Support
<ul>
<li>New <b>ICommandLauncher interface</b> supports overriding how build commands are launched.</li>
<li><b>EFS resources</b> now supported with Managed Build.</li>
<li>New <strong>ICommandLauncher interface</strong> supports overriding how build commands are launched.</li>
<li><strong>EFS resources</strong> now supported with Managed Build.</li>
</ul>
</li>
<li>XL C/C++ Compiler Support
<ul>
<li>The <b>XL C/C++ Error Parser</b> has been modernized. It can handle compiler errors/warnings better and
<li>The <strong>XL C/C++ Error Parser</strong> has been modernized. It can handle compiler errors/warnings better and
now also xlC linker warnings.</li>
<li><b>XL C/C++ v10.1 option support</b> in Managed Build</li>
<li><b>XL UPC compiler</b> support added.</li>
<li><strong>XL C/C++ v10.1 option support</strong> in Managed Build</li>
<li><strong>XL UPC compiler</strong> support added.</li>
</ul>
</li>
<li><b>Headless Build</b> You can now Import and Build CDT Projects without starting the IDE.</li>
<li><strong>Headless Build</strong> You can now Import and Build CDT Projects without starting the IDE.</li>
</ul>
</td>
@ -339,14 +339,14 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>DSF Integration</b></p>
<p align="right"><span class="bold">DSF Integration</span></p>
</td>
<td>DSF (Eclipse Debugger Services Framework) integrated. See <a
href="http://www.eclipse.org/dsdp/dd/development/relnotes/dd_news-1.1.html">DSF features</a> for more information.</td>
</tr>
<tr>
<td>
<p align="right"><b>Launch Group</b></p>
<p align="right"><span class="bold">Launch Group</span></p>
</td>
<td>
<p>New "Launch Group" launch configuration. Allows to launch several processes at once.</p>
@ -361,7 +361,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>Bugs fixed</b></p>
<p align="right"><span class="bold">Bugs fixed</span></p>
</td>
<td>Bugs fixed in this release:
<a href="http://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=CDT&target_milestone=6.0&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=exact&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
@ -379,7 +379,7 @@ may contain other information.
</tr>
<tr>
<td>
<p align="right"><b>texthere</b></p>
<p align="right"><span class="bold">texthere</span></p>
</td>
<td>text here.
<p><img src="../images/image.png" alt="alternate text for image for accessibility">

52
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_basic.htm
View file

@ -26,43 +26,43 @@ Now with CDT, you now select a project type, and that determines what build syst
<h3> Step 1: Creating a project</h3>
<ol>
<li>Select <b>File &gt; New &gt; Project</b>.</p>
<li>Select <strong>File &gt; New &gt; Project</strong>.</p>
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic02.png')">Click here to see an illustration (displayed in a separate window)</a>.</p><br></li>
<li>Select the type of project to create. For this tutorial, expand the <b>C++</b> folder and select <b>C++ Project</b> and click <b>Next</b>.
<li>Select the type of project to create. For this tutorial, expand the <strong>C++</strong> folder and select <strong>C++ Project</strong> and click <strong>Next</strong>.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic03a.png')">Click here to see an illustration.</a><br></p>
<p><br>The <b>C++ Project</b> wizard opens.</p>
<p><br>The <strong>C++ Project</strong> wizard opens.</p>
<a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic04.png')">Click here to see an illustration.</a><br></p>
<p><br>By default, the CDT filters the <b>Toolchain</b> and <b>Project types</b> that it displays in those lists based on the language support for the C++ Project wizard you selected for this tutorial.</p>
<p><br>By default, the CDT filters the <strong>Toolchain</strong> and <strong>Project types</strong> that it displays in those lists based on the language support for the C++ Project wizard you selected for this tutorial.</p>
</li><br>
<li><p>In the <b>Project name</b> field, type a name for the project, such as <b>Hello World</b>.</p>
<li><p>In the <strong>Project name</strong> field, type a name for the project, such as <strong>Hello World</strong>.</p>
<br>
<li><p>From the <b>Project types</b> list, expand <b>Executable</b> and select <b>Hello World C++ Project</b>. This project type provides a simple Hello World application in C++, and the makefile is automatically created by the CDT.</p>
<li><p>From the <strong>Project types</strong> list, expand <strong>Executable</strong> and select <strong>Hello World C++ Project</strong>. This project type provides a simple Hello World application in C++, and the makefile is automatically created by the CDT.</p>
<br>
<li><p>Select a required toolchain from the <b>Toolchain</b> list.</p>
<li><p>Select a required toolchain from the <strong>Toolchain</strong> list.</p>
<br>
<p>A toolchain is a set of tools (such as a compiler, linker, and assembler) intended to build your project.
Additional tools, such as a debugger, can be associated with a toolchain.
There can be several toolchains available, depending on the compilers installed on your system.</p>
<br>
<li><p>Click <b>Next</b>.</p>
<li><p>Click <strong>Next</strong>.</p>
<br>
<p>The Select Configurations window displays a list of configurations based on the project type and toolchain(s) you selected earlier.
<br>
<a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic07.png')">Click here to see an illustration.</a></p>
<br>
<li><p>Optional: If you want to change the default project settings, click <b>Advanced Settings</b>.</p>
<li><p>Optional: If you want to change the default project settings, click <strong>Advanced Settings</strong>.</p>
<br>
<p>This opens the project properties dialog for your new project allowing you change any of the project specific settings,
such as includes paths, compiler options, and libraries.</p>
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic21.png')">Click here to see an illustration.</a></p>
<br>
<li>If you clicked <b>Next</b> at Step 6, you can specify the basic properties for the new project, such as your name, copyright, and source information.</p>
<li>If you clicked <strong>Next</strong> at Step 6, you can specify the basic properties for the new project, such as your name, copyright, and source information.</p>
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic22.png')">Click here to see an illustration.</a></p>
<br>
<li><p>Click <b>Finish</b>.</p>
<li><p>Click <strong>Finish</strong>.</p>
<br>
<li><p>If the <b>C++ perspective</b> is not currently set as the default, you are prompted to determined if you would like to this project to be associated with the C/C++ perspective. Click <b>Yes</b>.
<li><p>If the <strong>C++ perspective</strong> is not currently set as the default, you are prompted to determined if you would like to this project to be associated with the C/C++ perspective. Click <strong>Yes</strong>.
<br><p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_cpp_perspectx.png')">Click here to see an illustration.</a></p>
<br>
<p>A project is created with the default settings and a full set of configurations based on the project type and toolchain you selected.
@ -73,24 +73,24 @@ Now with CDT, you now select a project type, and that determines what build syst
<h3>Step 2: Reviewing the code and building the project</h3>
<ol>
<li>From the Project Explorer in the C++ Projects View, double-click the .cpp file that was created for your project, for example, <tt>Hello World.cpp</tt>.
<li>From the Project Explorer in the C++ Projects View, double-click the .cpp file that was created for your project, for example, <span class="typewriter">Hello World.cpp</span>.
<p>Note that the file may be within a folder inside the project, e.g. the "src" folder.</p>
<p>This file opens in a default editor. It contains C++ template code for the Hello World example project you selected earlier.</p>
<br>
<p><b>Note:</b> You can specify a different editor, and add or modify existing code templates in <b>Window &gt; Preferences</b>.</p><p>In addition, the <b>Outline</b> view has also been populated
<p><strong>Note:</strong> You can specify a different editor, and add or modify existing code templates in <strong>Window &gt; Preferences</strong>.</p><p>In addition, the <strong>Outline</strong> view has also been populated
with objects created from your code.</p> <p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic13.png')">Click here to see an illustration.</a></p>
</li>
<li>Optional: You can type additional code in this file, and then save the changes by clicking <span
style="font-weight: bold;">File &gt; Save</span>, or pressing <b>CTRL+S</b>.
style="font-weight: bold;">File &gt; Save</span>, or pressing <strong>CTRL+S</strong>.
<p><br>Next, you will need to build your project before you can run it.</p><br></li>
<li>Build your project by pressing <b>CTRL+B</b>, or select the project from the Project Explorer tab in the C++ Projects view and select <b>File &gt; Build Project</b>.</p>
<p><br><b>Note:</b> If a build generates any errors or warnings, you can see those in the Problems view. If you encounter difficulty, see the topics <a href="../concepts/cdt_c_build_over.htm">Building C/C++ projects</a> and <a href="../concepts/cdt_c_before_you_begin.htm">Before you begin</a><br>.</p></li>
<li>Read through the build messages in the <b>Console</b> view.
<li>Build your project by pressing <strong>CTRL+B</strong>, or select the project from the Project Explorer tab in the C++ Projects view and select <strong>File &gt; Build Project</strong>.</p>
<p><br><strong>Note:</strong> If a build generates any errors or warnings, you can see those in the Problems view. If you encounter difficulty, see the topics <a href="../concepts/cdt_c_build_over.htm">Building C/C++ projects</a> and <a href="../concepts/cdt_c_before_you_begin.htm">Before you begin</a><br>.</p></li>
<li>Read through the build messages in the <strong>Console</strong> view.
The project should build successfully.</p>
<br>
<p>You will also see the <b>Outline</b> view has also been populated
with objects created from your code. If you select an item from the <b>Outline</b> view, the
<p>You will also see the <strong>Outline</strong> view has also been populated
with objects created from your code. If you select an item from the <strong>Outline</strong> view, the
corresponding text in the editor is highlighted.</p><br>
</ol>
@ -98,16 +98,16 @@ corresponding text in the editor is highlighted.</p><br>
<p>To run your application:</p>
<ol>
<li>Within the C/C++ Perspective, click <b>Run &gt; Run Configurations...</b>.<p><br></p></li>
<li>Select <b>C/C++ Application</b>.<p><br></p></li>
<li>Click <b>New</b>.<p><br></p></li>
<li>Within the C/C++ Perspective, click <strong>Run &gt; Run Configurations...</strong>.<p><br></p></li>
<li>Select <strong>C/C++ Application</strong>.<p><br></p></li>
<li>Click <strong>New</strong>.<p><br></p></li>
<p>A new Run Configuration is created. Its name and path to the executable are provided by the project ('Hello World' in our case).
<li>Click <b>Run</b>.<p><br></p>
<li>Click <strong>Run</strong>.<p><br></p>
<p>Now, you should see the Hello World application running in the <b>Console</b> view.
The <b>Console</b> also shows which application is running in a title bar.</p><br></li>
<p>Now, you should see the Hello World application running in the <strong>Console</strong> view.
The <strong>Console</strong> also shows which application is running in a title bar.</p><br></li>
<li>You can click the other views to see the information that they contain.
</ol>

16
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_build.htm
View file

@ -19,16 +19,16 @@ Console view. The Make Targets view displays makefile actions, and the
Tasks view displays compile warnings or errors.</p>
<p>To build a project:</p>
<ol>
<li>In the <b>Project Explorer</b> view, select your project. For the tutorial, you can select the <b>HelloWorld</b> project you created earlier. <p><br></p></li>
<li>Click <b>Project &gt; Build Project</b>.
<br>You can also hit the hammer icon <img src="../images/hammer-icon.png"> on the toolbar.
<li>In the <strong>Project Explorer</strong> view, select your project. For the tutorial, you can select the <strong>HelloWorld</strong> project you created earlier. <p><br></p></li>
<li>Click <strong>Project &gt; Build Project</strong>.
<br>You can also hit the hammer icon <img src="../images/hammer-icon.png" alt="build icon"> on the toolbar.
</li>
<p>If you see an error message, such as:</p>
<p><samp>&nbsp;&nbsp;&nbsp;(Cannot run program "make": Launching failed)</samp></p>
<p>then CDT cannot locate the build command, usually <samp>make</samp>.
Either your path is not configured correctly, or you do not have <samp>make</samp>
installed on your system.</p>
<li>You can see the output and results of the build command in the <b>Console</b> view.
<li>You can see the output and results of the build command in the <strong>Console</strong> view.
Click on its tab to bring the view forward if it is not currently visible.
If for some reason it's not present, you can open it by selecting Window > Show View > Console.
<p> <br>
@ -57,11 +57,11 @@ If for some reason it's not present, you can open it by selecting Window > Show
C/C++ Properties window</a><br>
</p>
<p> <a href="cdt_w_debug.htm">
<img border="0" src="../images/ngnext.gif" width="16" height="16" alt="Next icon"></a> <b><a
href="cdt_w_debug.htm">Next: Debugging a project</a></b></p>
<img border="0" src="../images/ngnext.gif" width="16" height="16" alt="Next icon"></a> <strong><a
href="cdt_w_debug.htm">Next: Debugging a project</a></strong></p>
<p align="left"> <a href="cdt_w_newmake.htm">
<img border="0" src="../images/ngback.gif" width="16" height="16" alt="Previous icon"></a> <b><a
href="cdt_w_newmake.htm">Back: Creating a makefile</a></b></p>
<img border="0" src="../images/ngback.gif" width="16" height="16" alt="Previous icon"></a> <strong><a
href="cdt_w_newmake.htm">Back: Creating a makefile</a></strong></p>
<p>
<img src="../images/ng00_04a.gif" alt="QNX Copyright Statement"></p>
</body>

30
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_creating_cpp_file.html
View file

@ -13,50 +13,50 @@
The .cpp file that you create will be saved in the project folder you just created in
<a href="creating_a_remote_project.html">Creating a remote project</a>.</p>
<p>Files are edited in the <b>Remote C/C++ Editor</b> located to the right of
the <b>Project Explorer</b> view. The left margin of the <b>Remote C/C++ Editor</b>, called the marker
<p>Files are edited in the <strong>Remote C/C++ Editor</strong> located to the right of
the <strong>Project Explorer</strong> view. The left margin of the <strong>Remote C/C++ Editor</strong>, called the marker
bar, displays icons for items such as bookmarks, breakpoints, and compiler errors and warnings.</p>
<p>For more information about:</p>
<ul>
<li>The marker bar, see <b>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Icons and buttons &gt; Editor area marker bar</b></li>
<li>The editor area, see <b>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Views and editors &gt; Editor area</b></li>
<li>The marker bar, see <strong>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Icons and buttons &gt; Editor area marker bar</strong></li>
<li>The editor area, see <strong>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Views and editors &gt; Editor area</strong></li>
</ul>
<p>To create a C++ file:</p>
<ol>
<li>In the <b>Project Explorer</b> view, right-click a project, and
select <b>New &gt; File &gt; Other</b>.<br>
<li>In the <strong>Project Explorer</strong> view, right-click a project, and
select <strong>New &gt; File &gt; Other</strong>.<br>
<img src="../images/create_c_file_01.png"
alt="New &gt; File &gt; Other in Projects View"></li>
<li>Select <b>Source file</b> under <b>C++</b>.<br>
<li>Select <strong>Source file</strong> under <strong>C++</strong>.<br>
<img src="../images/create_c_file_02.png"
alt="New Source file in New Wizard Dialog"></li>
<li>In the <b>Source File</b> box, type a name followed by the
<li>In the <strong>Source File</strong> box, type a name followed by the
appropriate extension. Select a template.</li>
<li>Click <b>Finish</b>.<br>
<li>Click <strong>Finish</strong>.<br>
<img src="../images/create_c_file_03.png" alt="New Source File Wizard"></li>
<p>The file will open in the Remote C/C++ editor.</p>
<li>Enter your code in the editor view.<br>
<img src="../images/create_c_file_04.png"
alt="Editor view with a sample code"></li>
<li>Type <b>CTRL+S</b> to save the file.</li>
<li>Type <strong>CTRL+S</strong> to save the file.</li>
</ol>
<p>Your new .cpp file is displayed in the <b>Project Explorer</b> view. Before you
<p>Your new .cpp file is displayed in the <strong>Project Explorer</strong> view. Before you
can build your newly created project, you must create a makefile.
See <a href="creating_your_makefile.html">Creating your makefile</a>.</p>
<br>
<b>Related tasks</b>
<strong>Related tasks</strong>
<br>
<a href="../tasks/creating_c_file.html">Creating a C/C++ file</a>
<br>
<b>Related reference</b>
<strong>Related reference</strong>
<br>
<a href="../reference/remote_c_editor.html">Remote C/C++ Editor</a>
<br>

32
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_debug.htm
View file

@ -17,15 +17,15 @@ breakpoints, suspending executed programs, stepping through your code, and
examining the contents of variables.</p>
<p>To debug a project:</p>
<ol>
<li>Click <b>Run &gt; Debug Configurations...</b>.<p>The Debug Configurations dialog opens.</li>
<li>Double-click <b>C/C++ Application</b>.</li>
<li>In the <b>Name</b> field, type <b>Hello World</b>.</li>
<li>Click <strong>Run &gt; Debug Configurations...</strong>.<p>The Debug Configurations dialog opens.</li>
<li>Double-click <strong>C/C++ Application</strong>.</li>
<li>In the <strong>Name</strong> field, type <strong>Hello World</strong>.</li>
<p>You can now select this debug launch configuration by name the next time
that you debug this project.</p>
<li>In the <b>Project</b> box, type or choose your project, e.g. <b>HelloWorld</b>.
<li>In the <strong>Project</strong> box, type or choose your project, e.g. <strong>HelloWorld</strong>.
<br>
Your executable should be selected under "C/C++ Application."
<br>If not, the <b>Search Project</b> button should find the executable in the project.
<br>If not, the <strong>Search Project</strong> button should find the executable in the project.
<p>&nbsp;</p>
</li>
<ul>
@ -33,8 +33,8 @@ examining the contents of variables.</p>
and choose a valid debugger for your platform (e.g. gdb/mi).
</li>
</ul>
<li>Click <b>Debug</b>.</li>
<p>You will be prompted to switch to the Debug Perspective. Click <b>Yes</b></p>
<li>Click <strong>Debug</strong>.</li>
<p>You will be prompted to switch to the Debug Perspective. Click <strong>Yes</strong></p>
<p>You will now see the debug perspective with the hello.exe application window open.
The C/C++ editor repositions in the perspective.</p>
<ul>
@ -47,19 +47,19 @@ examining the contents of variables.</p>
&nbsp;cout &lt;&lt; &quot;You just entered&quot;
<br>You'll see an icon there indicating the breakpoint is set.</br>
</li>
<li>Click <b>Run &gt; Resume</b>.
<br>Or, you can use the <b>Resume</b> button (green arrow) on the toolbar <i>of the Debug View</i>
<li>Click <strong>Run &gt; Resume</strong>.
<br>Or, you can use the <strong>Resume</strong> button (green arrow) on the toolbar <em>of the Debug View</em>
</li>
<li>When prompted, in the Console view, type a value other than 'm', and hit Enter/Return.<br>
The breakpoint will be hit.</li>
<li>In the <b>Variables</b> view, verify that the variable is not 'm'.</li>
<li>Click <b>Run &gt; Resume</b>.</li>
<li>In the <strong>Variables</strong> view, verify that the variable is not 'm'.</li>
<li>Click <strong>Run &gt; Resume</strong>.</li>
<li>When prompted, again type a value other than 'm' in the Console view, and press Enter/Return.</li>
<p>The breakpoint will be hit.</p>
<li>In the <b>Variables</b> view, verify that the variable is not 'm'.</li>
<li>In the <b>Variables</b> view, right-click the input variable, and select <b>Change Value...</b>
and type <b>'m'</b> <i>between the single quotes</i> and hit <b>OK</b>.</li>
<li>Click <b>Run &gt; Resume</b>.</li>
<li>In the <strong>Variables</strong> view, verify that the variable is not 'm'.</li>
<li>In the <strong>Variables</strong> view, right-click the input variable, and select <strong>Change Value...</strong>
and type <strong>'m'</strong> <em>between the single quotes</em> and hit <strong>OK</strong>.</li>
<li>Click <strong>Run &gt; Resume</strong>.</li>
<p>The output in the hello.exe application window is:<br>
&nbsp;&quot;You just entered m, you need to enter m to exit.&quot;
<li>The application terminates and the debug session ends. The debug
@ -69,7 +69,7 @@ examining the contents of variables.</p>
<p>To learn more about debugging, see the related debug conceptual topics.</p>
<p align="left"> <a href="cdt_w_build.htm">
<img border="0" src="../images/ngback.gif" width="16" height="16" alt="Back icon"></a><b> <a href="cdt_w_build.htm">Back: Building a project</a></b>&nbsp;&nbsp;&nbsp; </p>
<img border="0" src="../images/ngback.gif" width="16" height="16" alt="Back icon"></a><strong> <a href="cdt_w_build.htm">Back: Building a project</a></strong>&nbsp;&nbsp;&nbsp; </p>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>

24
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_existing_code.htm
View file

@ -50,7 +50,7 @@ you're importing:
<h3>Importing a C/C++ project from CVS</h3>
<p>
To check out an existing C/C++ project from the CVS repository into your workspace, right-click the project in the CVS Repositories view, and select <b>Check Out</b> from the menu. A project with the same name as the CVS module is checked out in to your workspace.
To check out an existing C/C++ project from the CVS repository into your workspace, right-click the project in the CVS Repositories view, and select <strong>Check Out</strong> from the menu. A project with the same name as the CVS module is checked out in to your workspace.
</p>
@ -63,7 +63,7 @@ To check out existing C/C++ code that is not part of a project:
<ol>
<li>
Right-click the module or directory in the CVS
Repositories view and choose <b>Check Out As&hellip;</b>
Repositories view and choose <strong>Check Out As&hellip;</strong>
from the menu.
<p>
@ -103,10 +103,10 @@ To check out existing C/C++ code that is not part of a project:
<p>
Choose the workspace location for this project, then the CVS
tag to check out.
<li>Click <b>Finish</b> to exit the <b>Check Out As</b> dialog.
<li>Click <strong>Finish</strong> to exit the <strong>Check Out As</strong> dialog.
</p>
<li>Click <b>Next</b> to continue.
<li>Click <strong>Next</strong> to continue.
</ol>
<h3>Importing C/C++ code into an existing project</h3>
@ -118,22 +118,22 @@ To import a directory full of C/C++ code into an existing project:
<ol>
<li>
Right-click the module or directory in the CVS
Repositories view and choose <b>Check Out As</b>
Repositories view and choose <strong>Check Out As</strong>
from the menu.
<p>
The IDE displays the Check Out As dialog.
</p>
<li>Choose <b>Check out into an existing project</b>, and then click
<b>Next</b>.
<li>Choose <strong>Check out into an existing project</strong>, and then click
<strong>Next</strong>.
The IDE displays the Check Out Into dialog:
</li>
<li>
Select an existing project from the list, and then
click <b>Finish</b> to add the code from CVS to the selected
click <strong>Finish</strong> to add the code from CVS to the selected
project.
</li>
</ol>
@ -163,7 +163,7 @@ not in the workspace folder for Eclipse. However, your existing folder structure
is displayed in the C/C++ Projects view. Meta data for the project, such as the
index for the project and the link to the existing source, is stored in the metadata
directory in the workspace folder. For more information on the workspace folder,
see <b>Workbench User Guide &gt; Tasks &gt; Upgrading Eclipse</b>.</p>
see <strong>Workbench User Guide &gt; Tasks &gt; Upgrading Eclipse</strong>.</p>
After you create a CDT project, you cannot easily move it or redefine its root folders.
If you need to, you can delete the CDT project (without deleting its contents) and then
@ -174,8 +174,8 @@ recreate it specifying a different non-default location.
<p>Another approach would be to create a C/C++ Project and then import your
existing file system.
For more information about importing, see <b>Workbench User Guide &gt; Tasks &gt; Importing &gt;
Importing resources from the file system</b>.</p>
For more information about importing, see <strong>Workbench User Guide &gt; Tasks &gt; Importing &gt;
Importing resources from the file system</strong>.</p>
<p>This approach copies the files from your file system to an Eclipse Workbench
project or folder. Your original source files remain unchanged and it is the
@ -184,7 +184,7 @@ When you have successfully imported your existing file system, the folder
structure is displayed in the C/C++ Projects view. Again, you should identify an
appropriate "root folder" to import from.</p>
<p><b>Tip:</b>
<p><strong>Tip:</strong>
<ul>
<li>Importing your existing file system can consume significant disk space

68
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_import.htm
View file

@ -20,15 +20,15 @@ function newWin(url) {
<p>Step 1: You want to create a single project that will reflect all of the components for the existing source tree.<br></p>
<ol>
<li>Select <b>File &gt; New &gt; Project</b>.
<li>For this tutorial, expand <b>C/C++</b> and select <b>C++ project</b>.
<li>Select <strong>File &gt; New &gt; Project</strong>.
<li>For this tutorial, expand <strong>C/C++</strong> and select <strong>C++ project</strong>.
<p><br>
The <b>New Project</b> wizard displays.
The <strong>New Project</strong> wizard displays.
<a href="javascript:void(0)" onClick="newWin('../images/cdt_w_import02.png')">Click
here to see an illustration (displayed in a separate window)</a>.</p>
<br>
<li>In the <b>Project name</b> field, type a name for the project.
<li>Ensure that the <b>Use default location</b> option is not selected because here we will specify where the
<li>In the <strong>Project name</strong> field, type a name for the project.
<li>Ensure that the <strong>Use default location</strong> option is not selected because here we will specify where the
resources reside in the file system, in a location other than your workspace. <br>
We assume this directory location already exists, and contains e.g. source files and makefile. If it does not exist, it
will be created.
@ -39,19 +39,19 @@ function newWin(url) {
here to see an illustration (displayed in a separate window)</a>.</p>
</p>
<li>In the <b>Location</b> field, specify the path to the existing files for your project.
<li>From the <b>Project types</b> list, expand <b>Makefile Project</b> and select <b>Empty Project.</b>.
<li>In the <strong>Location</strong> field, specify the path to the existing files for your project.
<li>From the <strong>Project types</strong> list, expand <strong>Makefile Project</strong> and select <strong>Empty Project.</strong>.
<ul>
<li>To have sample source and a makefile created in your existing directory, select <b>Hello World C++ Project</b></li>
<li>To have sample source and a makefile created in your existing directory, select <strong>Hello World C++ Project</strong></li>
</ul>
<li>Make sure a toolchain is selected.</li>
<li>Click <b>Next</b>.
<li>Click <strong>Next</strong>.
<p>&nbsp;
<li>(Optional) On the <b>Select Configurations</b> page, select only the configurations you want created. Configurations
<li>(Optional) On the <strong>Select Configurations</strong> page, select only the configurations you want created. Configurations
display for each toolchain selected on the previous page of the wizard.
<li>Click <b>Finish</b> to close the dialog box.
<li>Click <strong>Finish</strong> to close the dialog box.
<p>You will see the new project in the Project Explorer view. In addition, new 'dot' files have been created in
your legacy project's root directory, these are CDT project files.</p>
<ul>
@ -61,45 +61,45 @@ function newWin(url) {
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_viewMenu.png')">Click here to see an
illustration (displayed in a separate window)</a>.</p>
<br>
<li>In the <b>Available Customizations</b> window, on the <b>Filters</b> tab, uncheck ".* resources."
<li>In the <strong>Available Customizations</strong> window, on the <strong>Filters</strong> tab, uncheck ".* resources."
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_viewMenuFilters.png')">Click here to see an
illustration (displayed in a separate window)</a>.</p>
<br>
<li>The formerly hidden 'dot' files are now shown in the <b>Project Explorer</b>.
<li>The formerly hidden 'dot' files are now shown in the <strong>Project Explorer</strong>.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_viewMenuFilters2.png')">Click here to see an
illustration (displayed in a separate window)</a>.</p>
<br>
</li>
<li>Hit <b>OK</b> to close the dialog.</li>
<li>Hit <strong>OK</strong> to close the dialog.</li>
</ul>
</ol>
<p>Step 2: You are now ready to build your project.<br></p>
<ol>
<li>To build your project, select <b>Project</b> &gt; <b>Build Project</b>.
<br>You can also hit the hammer icon <img src="../images/hammer-icon.png"> on the toolbar to
<li>To build your project, select <strong>Project</strong> &gt; <strong>Build Project</strong>.
<br>You can also hit the hammer icon <img src="../images/hammer-icon.png" alt="build icon"> on the toolbar to
build the selected project.
<br>&nbsp;</br>
<li>You may see an error e.g. <code> "make: *** no rule to make target 'all'.</code>
<p>This is because, in our case, we didn't tell it where the makefile is, or its name.</p>
<ul>
<li>Open the project properties (right mouse on project name in the <b>Project Explorer</b> view
and select <b>Properties</b> at the bottom on the context menu).</li>
<li>On the C/C++ Build Page, on its <b>Builder Settings</b> tab, uncheck "Use default build command"
<li>Open the project properties (right mouse on project name in the <strong>Project Explorer</strong> view
and select <strong>Properties</strong> at the bottom on the context menu).</li>
<li>On the C/C++ Build Page, on its <strong>Builder Settings</strong> tab, uncheck "Use default build command"
and change the <code>make</code> command to <code>make -f hello.mak</code>
since our makefile is not named the default <code>makefile</code>.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_importBrandon02.png')">Click
here to see an illustration (displayed in a separate window)</a>.</p>
</li>
<li>Click <b>OK</b> to close the <b>Project Properties</b> window.
<li>Click <strong>OK</strong> to close the <strong>Project Properties</strong> window.
</li>
<li>Your project will probably rebuild. If not you can force a build via
<b>Project</b> &gt; <b>Build Project</b>
or use the hammer icon <img src="../images/hammer-icon.png">.
<strong>Project</strong> &gt; <strong>Build Project</strong>
or use the hammer icon <img src="../images/hammer-icon.png" alt="build icon">.
</li>
</ul>
</li>
<p>After the project build completes, the results display in the <b>Console</b> view and new objects, such as binaries and includes, show in the <b>Project Explorer</b> view.</p>
<p>After the project build completes, the results display in the <strong>Console</strong> view and new objects, such as binaries and includes, show in the <strong>Project Explorer</strong> view.</p>
<p>&nbsp;
<a href="javascript:void(0)" onClick="newWin('../images/cdt_w_importBrandon03.png')">Click
here to see an illustration (displayed in a separate window)</a>.</p>
@ -107,7 +107,7 @@ function newWin(url) {
<p>&nbsp;
<p></p>
<b>Note:</b> By default, the indexer is set to <b>Fast indexer</b> for the project to parse your project in the same way that a compiler does; beginning with each compilation unit and parsing that file and all files that it includes, except that it parses each header file included in a project only once. This method provides the most accurate index information. For large projects using complex C++ code, this indexer can be slow. For example, if a header file is included and takes two compilation units, the parsing of the second unit reuses the results of parsing the first unit. This is similar to how precompiled headers work. The indexing of large projects using the Fast indexer uses fewer resources than the Full indexer, but the resulting index is not quite as accurate.
<strong>Note:</strong> By default, the indexer is set to <strong>Fast indexer</strong> for the project to parse your project in the same way that a compiler does; beginning with each compilation unit and parsing that file and all files that it includes, except that it parses each header file included in a project only once. This method provides the most accurate index information. For large projects using complex C++ code, this indexer can be slow. For example, if a header file is included and takes two compilation units, the parsing of the second unit reuses the results of parsing the first unit. This is similar to how precompiled headers work. The indexing of large projects using the Fast indexer uses fewer resources than the Full indexer, but the resulting index is not quite as accurate.
<br>To change indexer settings, bring up the Indexer page in the Project Properties.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_indexer.png')">Click here to see an illustration (displayed in a separate window)</a>.</p> <br>
@ -117,16 +117,16 @@ function newWin(url) {
<p>Step 3: You are now ready to run your application.</p>
<ol>
<li>To run your application within the C/C++ Perspective, click <b>Run &gt; Run Configurations...</b><p>
<p>The <b>Run Configurations</b> dialog displays.</p>
<li>To create a run configuration, select <b>C/C++ Application</b> and click the <b>New</b> icon.
<li>Give your run configuration a name by entering a new name in the <b>Name</b> field at the top.
<li>On the <b>Main</b> tab, select the project by clicking <b>Browse</b> opposite the <b>Project</b> field.
<li>To run your application within the C/C++ Perspective, click <strong>Run &gt; Run Configurations...</strong><p>
<p>The <strong>Run Configurations</strong> dialog displays.</p>
<li>To create a run configuration, select <strong>C/C++ Application</strong> and click the <strong>New</strong> icon.
<li>Give your run configuration a name by entering a new name in the <strong>Name</strong> field at the top.
<li>On the <strong>Main</strong> tab, select the project by clicking <strong>Browse</strong> opposite the <strong>Project</strong> field.
<ul>
<li>From the Project Selection window, select the project and click <b>OK</b>.
</ul><li>Select the new <b>C/C++ Application</b> you want to execute by clicking <b>Search</b>.
<li>From the Project Selection window, select the project and click <strong>OK</strong>.
</ul><li>Select the new <strong>C/C++ Application</strong> you want to execute by clicking <strong>Search</strong>.
<p>In our case it didn't find the file because it's in a nonstandard location.
Use the <b>Browse</b> button to select the executable. In our case also it's a nonstandard
Use the <strong>Browse</strong> button to select the executable. In our case also it's a nonstandard
name, <code>hello.e</code> because that's what our makefile <code>hello.mak</code> built.</p>
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_importBrandon04run.png')">Click
here to see an illustration (displayed in a separate window)</a>.</p>
@ -137,10 +137,10 @@ name, <code>hello.e</code> because that's what our makefile <code>hello.mak</cod
</ul>
<li>Click <b>Run</b> to save the run configuration and run it.
<li>Click <strong>Run</strong> to save the run configuration and run it.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_importBrandon04run2.png')">Click
here to see an illustration (displayed in a separate window)</a>.</p>
<p>The application runs in the <b>Console</b> view. The <b>Console</b> also shows which application it is currently running in the title bar. You can configure the view to display different elements, such as user input elements using different colors.</p>
<p>The application runs in the <strong>Console</strong> view. The <strong>Console</strong> also shows which application it is currently running in the title bar. You can configure the view to display different elements, such as user input elements using different colors.</p>
</ol>
<img src="../images/ng00_04a.gif" ALT="QNX Copyright Statement" >
</body>

22
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_install_cdt.htm
View file

@ -29,46 +29,46 @@ function newWin(url) {
<p>To obtain the latest CDT features:</p>
<ol>
<li>Select <b>Help &gt; Software Updates &gt; Find and Install</b>.
<li>Select <strong>Help &gt; Software Updates &gt; Find and Install</strong>.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_find-install.png')">Click here to see an illustration (displayed in a separate window)</a>.</p>
<br></li>
<li>In the <b>Feature Updates</b> window, select <b>Search for new features to install</b> and click <b>Next</b>.<br><p>Note: If you want to search for updates on features that you currently have installed, you can select the option <b>Search for updates of the currently installed features</b>, and then follow the steps to update using that method.</p><p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_install_new.png')">Click here to see an illustration</a>.</p>
<li>In the <strong>Feature Updates</strong> window, select <strong>Search for new features to install</strong> and click <strong>Next</strong>.<br><p>Note: If you want to search for updates on features that you currently have installed, you can select the option <strong>Search for updates of the currently installed features</strong>, and then follow the steps to update using that method.</p><p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_install_new.png')">Click here to see an illustration</a>.</p>
<br></li>
<li>If you have not updated previously, you will have to enter the location of the Eclipse CDT Install site. Click <b>New Remote Site...</b>.
<li>If you have not updated previously, you will have to enter the location of the Eclipse CDT Install site. Click <strong>New Remote Site...</strong>.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_install_sites.png')">Click here to see an illustration</a>.</p>
<br></li>
<li>In the New Update Site dialog box, type the name and URL for the Eclipse update site.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_install_new_sites.png')">Click here to see an illustration</a>.</p><br></li>
<li>Click <b>OK</b>.<p><br></p></li>
<li>From the <b>Sites to include in search</b> list, select the update site you just created by clicking the appropriate check box, and click <b>Finish</b>.
<li>Click <strong>OK</strong>.<p><br></p></li>
<li>From the <strong>Sites to include in search</strong> list, select the update site you just created by clicking the appropriate check box, and click <strong>Finish</strong>.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_install_cdt_site.png')">Click here to see an illustration</a>.</p>
<br></li>
<li>The Search Results dialog shows the features available to install from the update site. Expand and select any additional features that you require. De-select any options that do not apply to you.<p><br></p></li>
<li>Click <b>Next</b>.
<li>Click <strong>Next</strong>.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_search_results.png')">Click here to see an illustration</a>.</p><br>
</li>
<li>You must accept the Eclipse.org Software User Agreement to continue installing the CDT update. If you accept the terms, select <b>I accept the terms in the license agreement</b> and then click <b>Next</b>.
<li>You must accept the Eclipse.org Software User Agreement to continue installing the CDT update. If you accept the terms, select <strong>I accept the terms in the license agreement</strong> and then click <strong>Next</strong>.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_license_agreement.png')">Click here to see an illustration</a>.</p>
<br></li>
<p>You can review the summary list of the features you selected to install.<br></p><br></li>
<li>Optional: Click <b>Change Location</b> to select the location you would like the updates installed. Typically, this is the directory where you installed Eclipse.<p><br></p></li>
<li>Click <b>Finish</b>.<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_location.png')">Click here to see an illustration</a>.</p>
<li>Optional: Click <strong>Change Location</strong> to select the location you would like the updates installed. Typically, this is the directory where you installed Eclipse.<p><br></p></li>
<li>Click <strong>Finish</strong>.<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_location.png')">Click here to see an illustration</a>.</p>
<br></li>
<li>You will now start downloading the CDT components. You will have to verify that you want the features installed by clicking
<b>Install</b> for each feature you selected.
<strong>Install</strong> for each feature you selected.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_update_jar_verification.png')">Click here to see an illustration</a>.</p>
<br><p>Now, you have to restart Eclipse. </p><br></li>
<li>Select <b>Yes</b> to complete the feature installation process.
<li>Select <strong>Yes</strong> to complete the feature installation process.
<p><a href="javascript:void(0)" onClick="newWin('../images/cdt_restart.png')">Click here to see an illustration</a>.</p>
</ol>

26
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_newcpp.htm
View file

@ -23,20 +23,20 @@ bar, displays icons for items such as bookmarks, breakpoints, and compiler erro
<p>For more information about:</p>
<ul>
<li>The editor area and marker bar, see <b>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Views and editors &gt; Editor area</b></li>
<li>The marker bar icons, see <b>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Icons and buttons &gt; Editor area marker bar</b></li>
<li>The editor area and marker bar, see <strong>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Views and editors &gt; Editor area</strong></li>
<li>The marker bar icons, see <strong>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Icons and buttons &gt; Editor area marker bar</strong></li>
</ul>
<p>To create a C++ file:</p>
<ol>
<li>In the <b>Project Explorer</b> view, right-click the <b>HelloWorld</b> project
folder, and select <b>New &gt; Source File</b>.</li>
<li>In the <b>Source file: </b> field, type <b>main.cpp</b>.
<li>In the <strong>Project Explorer</strong> view, right-click the <strong>HelloWorld</strong> project
folder, and select <strong>New &gt; Source File</strong>.</li>
<li>In the <strong>Source file: </strong> field, type <strong>main.cpp</strong>.
<br>By default the source folder should be your project folder.
<br>The template selected is probably "Default C/C++ Source Template."
</li>
<li>Click <b>Finish</b>.</li>
<li>Click <strong>Finish</strong>.</li>
<li>A Comment template probably appears at the top of an otherwise empty file.
Type the code, exactly as it appears below, in the editor.
Or you can paste it in from this help file.
@ -61,20 +61,20 @@ int main () {
</pre>
<li>Click <b>File &gt;
Save</b>.</li>
<li>Click <strong>File &gt;
Save</strong>.</li>
</ol>
<p>Your new .cpp file is displayed in the <b>Project Explorer</b> view. Your project now contains main.cpp. Before you
<p>Your new .cpp file is displayed in the <strong>Project Explorer</strong> view. Your project now contains main.cpp. Before you
can build your HelloWorld project, you must create a makefile.</p>
<p>
<a href="cdt_w_newmake.htm" style="text-decoration: none">
<img border="0" src="../images/ngnext.gif" width="16" height="16" alt="Next icon"></a> <b><a href="cdt_w_newmake.htm">Next: Creating your makefile </a> </b>
<img border="0" src="../images/ngnext.gif" width="16" height="16" alt="Next icon"></a> <strong><a href="cdt_w_newmake.htm">Next: Creating your makefile </a> </strong>
</p>
<p align="left"><a href="cdt_w_newproj.htm" style="text-decoration: none">
<img border="0" src="../images/ngback.gif" width="16" height="16" alt="Back icon"></a> <b><a href="cdt_w_newproj.htm">Back: Creating your project</a></b></p>
<img border="0" src="../images/ngback.gif" width="16" height="16" alt="Back icon"></a> <strong><a href="cdt_w_newproj.htm">Back: Creating your project</a></strong></p>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>

18
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_newmake.htm
View file

@ -21,10 +21,10 @@ function newWin(url) {
<p>To create a makefile:</p>
<ol>
<li>In the <b>Project Explorer</b> view, right-click the <b>HelloWorld</b> project
folder and select <b>New &gt; File</b>.
<li>In the <b>File name</b> box, type <b>makefile</b>.</li>
<li>Click <b>Finish</b>.</li>
<li>In the <strong>Project Explorer</strong> view, right-click the <strong>HelloWorld</strong> project
folder and select <strong>New &gt; File</strong>.
<li>In the <strong>File name</strong> box, type <strong>makefile</strong>.</li>
<li>Click <strong>Finish</strong>.</li>
<li>Type the gnu make instructions below in the editor. Lines are
indented with tab characters, not with spaces.</li>
@ -43,8 +43,8 @@ function newWin(url) {
&nbsp;&nbsp;&nbsp; g++ -c -g main.cpp<br>
&nbsp;</p>
</blockquote>
<li>Click <b>File &gt;
Save</b>.</li></ol>
<li>Click <strong>File &gt;
Save</strong>.</li></ol>
<p>Your new makefile, along with your main.cpp file are
displayed in the Project Explorer view. Your project now
@ -56,13 +56,13 @@ contains main.cpp and makefile. You can now build your HelloWorld project.</p>
<p>
<a href="cdt_w_build.htm" style="text-decoration: none">
<img border="0" src="../images/ngnext.gif" width="16" height="16" alt="Next icon"></a>
<b><a href="cdt_w_build.htm">
Next: Building your project</a><a href="cdt_w_build.htm" style="text-decoration: none"> </a> </b>
<strong><a href="cdt_w_build.htm">
Next: Building your project</a><a href="cdt_w_build.htm" style="text-decoration: none"> </a> </strong>
</p>
<p align="left">
<a href="cdt_w_newcpp.htm">
<img border="0" src="../images/ngback.gif" width="16" height="16" alt="Back icon"></a> <b><a href="cdt_w_newcpp.htm">Back: Creating your C++ file</a></b> </p>
<img border="0" src="../images/ngback.gif" width="16" height="16" alt="Back icon"></a> <strong><a href="cdt_w_newcpp.htm">Back: Creating your C++ file</a></strong> </p>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="../concepts/cdt_o_projects.htm">Project</a><br>

64
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_newproj.htm
View file

@ -23,56 +23,56 @@ that can incrementally compile source files as they are changed.</p>
<p>To create a project:</p>
<ol>
<li>Select <b>File &gt; New &gt; Project</b>.
<li>Select <strong>File &gt; New &gt; Project</strong>.
<p><br>When you create a new project, you are required to specify the project type. This project type will determine the toolchain, data, and tabs that the CDT uses/displays.</p><br>
<li>Select the type of project to create. For this tutorial, expand the <b>C/C++</b> folder and select <b>C++ Project</b>.
<br><p>The <b>C++ Project</b> wizard opens. <a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic19.png')">Click here to see an illustration.</a></p><br>
<p>By default, the CDT filters the <b>Toolchain</b> and <b>Project types</b> that currently display in those lists are based on the language support for the C++ Project wizard you selected for this tutorial.</p><br>
<li>In the <b>Project name</b> field, type HelloWorld.
<li>Leave the <b>Use Default Location</b> option selected.
<li>Select the type of project to create. For this tutorial, expand the <strong>C/C++</strong> folder and select <strong>C++ Project</strong>.
<br><p>The <strong>C++ Project</strong> wizard opens. <a href="javascript:void(0)" onClick="newWin('../images/cdt_w_basic19.png')">Click here to see an illustration.</a></p><br>
<p>By default, the CDT filters the <strong>Toolchain</strong> and <strong>Project types</strong> that currently display in those lists are based on the language support for the C++ Project wizard you selected for this tutorial.</p><br>
<li>In the <strong>Project name</strong> field, type HelloWorld.
<li>Leave the <strong>Use Default Location</strong> option selected.
<p><br>Next, you want to select the type of project to create. In the New CDT Project Wizard, you can choose from the following project types:</p>
<ul>
<li><b>Executable</b> - Provides an executable application. This project type folder contains three templates.</p>
<li><strong>Executable</strong> - Provides an executable application. This project type folder contains three templates.</p>
<ul>
<li><b>Hello World C++ Example</b> provides a simple C++ Hello World application with main().
<li><b>Hello World ANSI C Example</b> provides a simple C Hello World application with main().
<li><b>Empty Project</b> provides a single source project folder that contains no files.
<li><strong>Hello World C++ Example</strong> provides a simple C++ Hello World application with main().
<li><strong>Hello World ANSI C Example</strong> provides a simple C Hello World application with main().
<li><strong>Empty Project</strong> provides a single source project folder that contains no files.
<p>After you select this template, the result is a project with only the meta-data files required for the project type.
You are expected to provide source files for the project's target.</p>
</ul>
<p>The makefile for the <b>Executable</b> project type is automatically created by the CDT.</p>
<p>The makefile for the <strong>Executable</strong> project type is automatically created by the CDT.</p>
<p>&nbsp;</p>
<li><b>Shared Library</b> - An executable module that is compiled and linked separately. When you create a project that uses a shared library (libxx.so), you define your shared library's project as a Project Reference for your application. For this project type, the CDT combines object files together and joins them so they're relocatable and can be shared by many processes. Shared libraries are named using the format
<li><strong>Shared Library</strong> - An executable module that is compiled and linked separately. When you create a project that uses a shared library (libxx.so), you define your shared library's project as a Project Reference for your application. For this project type, the CDT combines object files together and joins them so they're relocatable and can be shared by many processes. Shared libraries are named using the format
libxx.so.<var>version</var>, where
<var>version</var> is a number with a default of 1. The
libxx.so file usually is a symbolic link to the
latest version. The makefile for this project type is automatically created by the CDT.
<li><b>Static Library</b> - A collection of object files that you can link into another application (libxx.a). The CDT combines object files (i.e. *.o)
<li><strong>Static Library</strong> - A collection of object files that you can link into another application (libxx.a). The CDT combines object files (i.e. *.o)
into an archive (*.a) that is directly linked into an
executable. The makefile for this project type is automatically created by the CDT.
<li><b>Makefile Project</b> - Creates an empty project without the meta-data files. This selection is useful for importing and modifying existing makefile-based projects; a new makefile is not created for this project type.
<li><strong>Makefile Project</strong> - Creates an empty project without the meta-data files. This selection is useful for importing and modifying existing makefile-based projects; a new makefile is not created for this project type.
</ul>
<p>By default, the CDT filters the <b>Toolchain</b> and <b>Project types</b> that currently display in those lists based on the language support for the C++ Project wizard you selected for this tutorial.
<p>By default, the CDT filters the <strong>Toolchain</strong> and <strong>Project types</strong> that currently display in those lists based on the language support for the C++ Project wizard you selected for this tutorial.
<p>&nbsp;</p>
<li>From the <b>Project types</b> list, expand <b>Makefile project</b> and select <b>Empty Project</b>.
<li>From the <strong>Project types</strong> list, expand <strong>Makefile project</strong> and select <strong>Empty Project</strong>.
This project lets you enter the source file and the makefile yourself.
<li>Select a required toolchain from the <b>Toolchain</b> list.
<li>Select a required toolchain from the <strong>Toolchain</strong> list.
<p>A toolchain is a set of tools (such as a compiler, linker, and assembler) intended to build your project.
Additional tools, such as a debugger, can be associated with a toolchain.<br>
There can be several toolchains available, depending on the compilers installed on your system.
</p>
</li>
<li>Click <b>Next</b>.
<li>(Optional) On the <b>Select Configurations</b> page, Click <b>Advanced Settings</b>.
<li>Click <strong>Next</strong>.
<li>(Optional) On the <strong>Select Configurations</strong> page, Click <strong>Advanced Settings</strong>.
<ul>
<li>Expand <b>C/C++Build > Settings</b>. Click the <b>Binary Parsers</b> tab.
<li>Expand <strong>C/C++Build > Settings</strong>. Click the <strong>Binary Parsers</strong> tab.
<p><br><a href="javascript:void(0)" onClick="newWin('../images/cdt_w_binparser01.png')">Click here to see an illustration.</a></p><br>
</p>
</li>
<li>In the <b>Binary Parser</b> list, select the error parser that is appropriate for your platform.
<li>In the <strong>Binary Parser</strong> list, select the error parser that is appropriate for your platform.
Other project settings can be modified here as well. The default selection is probably OK.
</li>
@ -81,11 +81,11 @@ run and debug your programs, selecting the correct parser is important. After
you select the correct parser for your development environment and build your
project, you can view the components of the .o file in the C/C++ Projects
view. You can also view the contents of the .o file in the C/C++ editor.
<p></p>Click <b>OK</b> to close the Project Properties window.
<p></p>Click <strong>OK</strong> to close the Project Properties window.
</ul>
</p>
<li>Click <b>Finish</b>.</li>
<li>If a message box prompts you to change perspectives, click <b>Yes</b>.
<li>Click <strong>Finish</strong>.</li>
<li>If a message box prompts you to change perspectives, click <strong>Yes</strong>.
</li>
</ol>
@ -96,16 +96,16 @@ You may see an error since there is nothing to build yet for your project.
You can now start writing the code for your HelloWorld
program.</p>
<p><b>Tip:</b> You can view and modify the properties of your
HelloWorld project at any time by right-clicking on the project in the <b>Project Explorer</b>
<p><strong>Tip:</strong> You can view and modify the properties of your
HelloWorld project at any time by right-clicking on the project in the <strong>Project Explorer</strong>
view and clicking Properties.</p> <p><a style="text-decoration: none" href="cdt_w_newcpp.htm"><img
src="../images/ngnext.gif" height="16" width="16" border="0" alt="Next Icon"></a> <a href="cdt_w_newcpp.htm"><b>
Next: Creating your C++ file</b></a></p> <p align="left">For more information
src="../images/ngnext.gif" height="16" width="16" border="0" alt="Next Icon"></a> <a href="cdt_w_newcpp.htm"><strong>
Next: Creating your C++ file</strong></a></p> <p align="left">For more information
about:</p> <ul>
<li>Projects, see <b>Workbench User Guide > Concepts > Workbench > Resources
</b></li>
<li>The workspace, see <b>Workbench User Guide > Tasks > Upgrading Eclipse
</b></li>
<li>Projects, see <strong>Workbench User Guide > Concepts > Workbench > Resources
</strong></li>
<li>The workspace, see <strong>Workbench User Guide > Tasks > Upgrading Eclipse
</strong></li>
</ul> <p><img src="../images/ngconcepts.gif" alt="Related concepts" height="21" width="143"
border="0"> <br> <a href="../concepts/cdt_c_over_cdt.htm">CDT overview</a><br> <a href="../concepts/cdt_c_projects.htm">
CDT projects</a><br> <a href="../concepts/cdt_c_proj_file_views.htm">Project file views

16
doc/org.eclipse.cdt.doc.user/getting_started/cdt_w_prepare_workbench.htm
View file

@ -22,7 +22,7 @@ function newWin(url) {
<ul>
<li>Your Workbench has its default settings.
To reset the current perspective to its original layout, from the menu bar select
<b>Window &gt; Reset Perspective</b>.</li>
<strong>Window &gt; Reset Perspective</strong>.</li>
<li>You are familiar with the basic Workbench features, such as
<a href="../concepts/cdt_c_views.htm">views</a> and
<a href="../concepts/cdt_c_perspectives.htm">perspectives</a>.
@ -32,23 +32,23 @@ To reset the current perspective to its original layout, from the menu bar selec
<h2>Setting the operation and appearance of the C/C++ Editor</h2>
<ol>
<br><li>To open the Workbench preferences, from the menu bar, select <b>Window &gt; Preferences</b>.</li>
<br><li>Expand <b>C/C++</b> and select <b>Editor</b>.
<br><li>To open the Workbench preferences, from the menu bar, select <strong>Window &gt; Preferences</strong>.</li>
<br><li>Expand <strong>C/C++</strong> and select <strong>Editor</strong>.
<p><br><a href="javascript:void(0)" onClick="newWin('../images/editor_general_preferences.png')">Click here to see an illustration (displayed in a separate window).</a></p></li>
<br><li>Make any changes that you require to be comfortable editing files.
For example, you might want to enable <b>Show line numbers</b> or change the <b>Problem indicator color</b> to a different shade of red. For more information about setting preferences in the editor, see <a href="../reference/cdt_u_c_editor_gen.htm">General page Preferences window</a> in the reference section.</li>
For example, you might want to enable <strong>Show line numbers</strong> or change the <strong>Problem indicator color</strong> to a different shade of red. For more information about setting preferences in the editor, see <a href="../reference/cdt_u_c_editor_gen.htm">General page Preferences window</a> in the reference section.</li>
<br><li>On the Preferences C/C++ Editor dialog, click the <b>Colors</b> tab. The <b>Colors</b> tab for the C/C++ Editor preferences dialog displays.</p><p><br><a href="javascript:void(0)" onClick="newWin('../images/editor_color_preferences.png')">Click here to see an illustration.</a></p>
<br><li>On the Preferences C/C++ Editor dialog, click the <strong>Colors</strong> tab. The <strong>Colors</strong> tab for the C/C++ Editor preferences dialog displays.</p><p><br><a href="javascript:void(0)" onClick="newWin('../images/editor_color_preferences.png')">Click here to see an illustration.</a></p>
<br>Again, make any changes that will be useful for your working habits and click <b>OK</b>. For more information see the <a href="../reference/cdt_u_c_editor_color.htm">Color page Preferences window</a> in the reference section.</li>
<br>Again, make any changes that will be useful for your working habits and click <strong>OK</strong>. For more information see the <a href="../reference/cdt_u_c_editor_color.htm">Color page Preferences window</a> in the reference section.</li>
<br><li>On the <b>Preferences C/C++ Editor</b> dialog, click the <b>Content Assist</b> tab. The <b>Preferences C/C++ Editor</b> dialog's <b>Content Assist</b> tab appears.<br>
<br><li>On the <strong>Preferences C/C++ Editor</strong> dialog, click the <strong>Content Assist</strong> tab. The <strong>Preferences C/C++ Editor</strong> dialog's <strong>Content Assist</strong> tab appears.<br>
<p><br><a href="javascript:void(0)" onClick="newWin('../images/contentAssist_preferences.png')">Click here to see an illustration.</a></p>
<p><br>If you want to set an auto-activation delay or change the background for completion proposals, do so now. For more information see the <a href="../reference/cdt_u_c_editor_con_assist.htm">Content Assist page Preferences window</a> in the reference section.</p></li>
<br><li>Leave the preferences by clicking <b>OK</b>.</li>
<br><li>Leave the preferences by clicking <strong>OK</strong>.</li>
</ol>

2
doc/org.eclipse.cdt.doc.user/getting_started/hw_example.htm
View file

@ -6,7 +6,7 @@
<title>C++ Hello World example</title>
</head>
<body bgcolor="#ffffcc">
<font color="#0066ff">Copy the code below and paste it into the <b>main.cpp</b> file in the Editor view:</font>
<p style="color:#0066ff">Copy the code below and paste it into the <strong>main.cpp</strong> file in the Editor view:</p>
<pre>
#include &#60iostream&#62

2
doc/org.eclipse.cdt.doc.user/getting_started/make_example.htm
View file

@ -6,7 +6,7 @@
<title>C++ Makefile example</title>
</head>
<body bgcolor="#ffffcc">
<font color="#0066ff">Copy the script below and paste it into the <b>makefile</b> file in the Editor view:</font>
<p style="color:#0066ff">Copy the script below and paste it into the <strong>makefile</strong> file in the Editor view:</p>
<pre>
all: hello

5
doc/org.eclipse.cdt.doc.user/help.css
View file

@ -17,6 +17,7 @@ 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 }
h5 { font size: 13.5pt; }
p { font-size: 10pt; }
pre { margin-left: 6; font-size: 9pt }
@ -49,3 +50,7 @@ th { font-weight: bold }
div.linux {display:none;}
.firsterm {font-style:italic;}
.typewriter {font-family:monospace;}
.bold {font-weight:600;}
.linethrough {text-decoration: line-through;}
.underline {text-decoration: underline;}

18
doc/org.eclipse.cdt.doc.user/reference/cdt_o_mproj_pref_macro.htm
View file

@ -16,16 +16,16 @@
<img border="0" src="../images/mpref_macro.PNG" width="580" height="525" alt="Managed Build Macros Preference page"></p>
<p>You can add, remove and edit build macros that apply to all managed make projects in the workspace.&nbsp;
Two tables are displayed - one for user-defined build macros and one for non user-defined build macros.&nbsp;
Each table contains three columns<b>:</b></p>
<p><b>Name</b> of the build macro</p>
<p><b>Type </b>of value contained in the build macro (see below)</p>
<p><b>Value </b>of the build macro.&nbsp; </p>
<p>You can view all build macros that are not user-defined in the <b>System
Macros</b> table.</p>
<p class="MsoNormal">You can view all user-defined macros in the <b>User
Macros</b> table. A user-defined macro overrides a non user-defined macro of the same
Each table contains three columns<strong>:</strong></p>
<p><strong>Name</strong> of the build macro</p>
<p><strong>Type </strong>of value contained in the build macro (see below)</p>
<p><strong>Value </strong>of the build macro.&nbsp; </p>
<p>You can view all build macros that are not user-defined in the <strong>System
Macros</strong> table.</p>
<p class="MsoNormal">You can view all user-defined macros in the <strong>User
Macros</strong> table. A user-defined macro overrides a non user-defined macro of the same
name.&nbsp; Overridden macros are displayed in bold in
the <b>System Macros</b> table.</p>
the <strong>System Macros</strong> table.</p>
<p class="MsoNormal">For more detailed information about managed make project build macros
settings, see the description in the <a href="cdt_u_mprop_macros.htm">Build Macros Property Pages</a>.</p>
<p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21"></p>

2
doc/org.eclipse.cdt.doc.user/reference/cdt_o_new_mproj.htm
View file

@ -11,7 +11,7 @@
<body>
<h1>C/C++ New Project Wizard, Managed Make Project</h1>
<p>This section describes properties for creating a Managed make project in the <b>C/C++ New Project Wizard</b>.</p>
<p>This section describes properties for creating a Managed make project in the <strong>C/C++ New Project Wizard</strong>.</p>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_u_new_proj_wiz_m_name.htm">Name</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_u_new_proj_wiz_m_target.htm">Select a
Project Type</a><br>

2
doc/org.eclipse.cdt.doc.user/reference/cdt_o_new_sproj.htm
View file

@ -11,7 +11,7 @@
<body>
<h1>C/C++ New Project Wizard, Standard Make Project</h1>
<p>This section describes properties for creating a Standard make project in the <b>C/C++ New Project Wizard</b>.</p>
<p>This section describes properties for creating a Standard make project in the <strong>C/C++ New Project Wizard</strong>.</p>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_u_new_proj_wiz_s_name.htm">Name</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_u_new_proj_wiz_s_proj.htm">Referenced Projects</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_u_new_proj_wiz_s_mbuilder.htm">Make Builder</a><br>

2
doc/org.eclipse.cdt.doc.user/reference/cdt_o_prop_proj.htm
View file

@ -12,7 +12,7 @@
<h1>Project Properties</h1>
<p>This section describes C/C++ Project Properties.
To select project properties, right click a project and select <b>Properties</b>.</p>
To select project properties, right click a project and select <strong>Properties</strong>.</p>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21"> <br>
<a href="../concepts/cdt_c_projects.htm">CDT projects</a></p>

16
doc/org.eclipse.cdt.doc.user/reference/cdt_u_appearance_pref.htm
View file

@ -12,12 +12,12 @@
<h1>Appearance preferences</h1>
<p>Use the <b>Appearance</b> panel of the Preferences window to customize the appearance of C elements in the viewers.</p>
<p>Use the <strong>Appearance</strong> panel of the Preferences window to customize the appearance of C elements in the viewers.</p>
<p><img src="../images/view_appearance_prefs.png" alt="Appearance Preference"></p>
<table width="700px" cellpadding="5" cellspacing="0" border="1" >
<caption>
<b>Appearance Options</b>
<strong>Appearance Options</strong>
</caption>
<colgroup>
<col width="30%" valign="top" >
@ -25,27 +25,27 @@
</colgroup>
<tbody>
<tr>
<td width="241" valign="top"><b>Show translation unit members </b></td>
<td width="241" valign="top"><strong>Show translation unit members </strong></td>
<td width="433" valign="top">Select this option to show translation unit members in Project Explorer and C/C++ Projects view. </td>
</tr>
<tr>
<td valign="top"><b>Group include directives in Project Explorer and C/C++ Projects view </b></td>
<td valign="top"><strong>Group include directives in Project Explorer and C/C++ Projects view </strong></td>
<td valign="top">Select this option to group include directives in Project Explorer and C/C++ Projects view. </td>
</tr>
<tr>
<td valign="top"><b>Group include directives in the Outline view </b></td>
<td valign="top"><strong>Group include directives in the Outline view </strong></td>
<td valign="top">Select this option to group include directives in the Outline view. </td>
</tr>
<tr>
<td valign="top"><b>Group namespaces in the Outline view </b></td>
<td valign="top"><strong>Group namespaces in the Outline view </strong></td>
<td valign="top">Select this option to group namespace declarations in the Outline view. </td>
</tr>
<tr>
<td valign="top"><b>Group method definitions in the Outline view </b></td>
<td valign="top"><strong>Group method definitions in the Outline view </strong></td>
<td valign="top">Select this option to group method definitions for the same type in the Outline view. </td>
</tr>
<tr>
<td valign="top"><b>Sort header files before source files in Project Explorer and C/C++ Projects view </b></td>
<td valign="top"><strong>Sort header files before source files in Project Explorer and C/C++ Projects view </strong></td>
<td valign="top">Select this option to separate header and source files in Project Explorer and C/C++ Projects view. </td>
</tr>
</tbody>

20
doc/org.eclipse.cdt.doc.user/reference/cdt_u_build_pref.htm
View file

@ -12,46 +12,46 @@
<h1>Build Console preferences</h1>
<p>You can customize the appearance of the <b>Build Console</b> view.</p>
<p>You can customize the appearance of the <strong>Build Console</strong> view.</p>
<p><img src="../images/cdt_pref_build_console.png" alt="Build Console Preferences Dialog Box"></p>
<table width="700px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Build Console Preference Options</b></caption>
<caption><strong>Build Console Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Always clear console before building</b></td>
<td><strong>Always clear console before building</strong></td>
<td>Select this option to clear the contents of the Console view every time you perform a build.</td>
</tr>
<tr>
<td><b>Open console when building</b></td>
<td><strong>Open console when building</strong></td>
<td>Select this option to open the Console view when you perform a build.</td>
</tr>
<tr>
<td><b>Bring console to top when building (if present)</b></td>
<td><strong>Bring console to top when building (if present)</strong></td>
<td>Select this option to make the Console view the active window when you perform a build.</td>
</tr>
<tr>
<td><b>Limit console output (#lines)</b></td>
<td><strong>Limit console output (#lines)</strong></td>
<td>Specify the maximum number of lines that can display in the Console view.</td>
</tr>
<tr>
<td><b>Display tab width</b></td>
<td><strong>Display tab width</strong></td>
<td>Specify the number of spaces for a tab.</td>
</tr>
<tr>
<td><b>Output text color</b></td>
<td><strong>Output text color</strong></td>
<td>Customize the color of text in the Console view.</td>
</tr>
<tr>
<td><b>Information message text color</b></td>
<td><strong>Information message text color</strong></td>
<td>Customize the color of information text messages in the Console view.</td>
</tr>
<tr>
<td><b>Error message text color</b></td>
<td><strong>Error message text color</strong></td>
<td>Customize the color of error messages in the Console view.</td>
</tr>
</tbody>

2
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_code_style_pref.htm
View file

@ -11,7 +11,7 @@
<h1>Code Style preferences</h1>
<p>Use the <b>Code Style</b> preference panel to configure you code style profiles for smart typing features, like auto-indentation and formatting. Click <b>Window &gt; Preferences &gt; C/C++ &gt; Code Style</b> to make changes.</p>
<p>Use the <strong>Code Style</strong> preference panel to configure you code style profiles for smart typing features, like auto-indentation and formatting. Click <strong>Window &gt; Preferences &gt; C/C++ &gt; Code Style</strong> to make changes.</p>
<p><img src="../images/code_style_preferences.png" alt="Code Style Preferences"></p>
<table border="1" cellspacing="0" cellpadding="5" width="600" summary="All options">
<thead>

16
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_code_templates_pref.htm
View file

@ -16,7 +16,7 @@
<p>The
<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferences.CodeTemplatePreferencePage)")'>
<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Code Templates preference page">
<b>C/C++ &gt; Code Style &gt; Code Templates</b></a> preference page
<strong>C/C++ &gt; Code Style &gt; Code Templates</strong></a> preference page
lets you configure the format of newly generated code stubs, comments and files.</p>
<p>The code templates page contains templates that are used by actions that generate code and/or source files.
@ -106,7 +106,7 @@ Templates contain variables that are substituted when the template is applied. S
</td>
<td valign="top">
<p>Header comment for new source or header files.</p>
<p>Note that this template can be referenced in source and header file templates with <b>${filecomment}</b>.</p>
<p>Note that this template can be referenced in source and header file templates with <strong>${filecomment}</strong>.</p>
</td>
</tr>
<tr>
@ -115,7 +115,7 @@ Templates contain variables that are substituted when the template is applied. S
</td>
<td valign="top">
<p>The comment for new types.</p>
<p>Note that this template can be referenced in source and header file templates with <b>${typecomment}</b>.</p>
<p>Note that this template can be referenced in source and header file templates with <strong>${typecomment}</strong>.</p>
</td>
</tr>
<tr>
@ -217,7 +217,7 @@ The New File from Template wizard can be used to create new files based on one o
</td>
<td valign="top">
<p>Used by the New Class wizard and the New Source File wizard when a new C++ source file is created.</p>
<p>The template can specify where comments are added. Note that the template can contain the variable <b>${typecomment}</b> and <b>${filecomment}</b> that will be substituted by the evaluation of the <b>Types</b> respectively <b>Files</b> comment template.</p>
<p>The template can specify where comments are added. Note that the template can contain the variable <strong>${typecomment}</strong> and <strong>${filecomment}</strong> that will be substituted by the evaluation of the <strong>Types</strong> respectively <strong>Files</strong> comment template.</p>
</td>
</tr>
<tr>
@ -226,7 +226,7 @@ The New File from Template wizard can be used to create new files based on one o
</td>
<td valign="top">
<p>Used by the New Class wizard and the New Header File wizard when a new C++ header file is created.</p>
<p>The template can specify where comments are added. Note that the template can contain the variable <b>${typecomment}</b> and <b>${filecomment}</b> that will be substituted by the evaluation of the <b>Types</b> respectively <b>Files</b> comment template.</p>
<p>The template can specify where comments are added. Note that the template can contain the variable <strong>${typecomment}</strong> and <strong>${filecomment}</strong> that will be substituted by the evaluation of the <strong>Types</strong> respectively <strong>Files</strong> comment template.</p>
</td>
</tr>
<tr>
@ -235,7 +235,7 @@ The New File from Template wizard can be used to create new files based on one o
</td>
<td valign="top">
<p>Used by the New Source File wizard when a new C source file is created.</p>
<p>The template can specify where comments are added. Note that the template can contain the variable <b>${typecomment}</b> and <b>${filecomment}</b> that will be substituted by the evaluation of the <b>Types</b> respectively <b>Files</b> comment template.</p>
<p>The template can specify where comments are added. Note that the template can contain the variable <strong>${typecomment}</strong> and <strong>${filecomment}</strong> that will be substituted by the evaluation of the <strong>Types</strong> respectively <strong>Files</strong> comment template.</p>
</td>
</tr>
<tr>
@ -244,12 +244,12 @@ The New File from Template wizard can be used to create new files based on one o
</td>
<td valign="top">
<p>Used by the New Header File wizard when a new C source file is created.</p>
<p>The template can specify where comments are added. Note that the template can contain the variable <b>${typecomment}</b> and <b>${filecomment}</b> that will be substituted by the evaluation of the <b>Types</b> respectively <b>Files</b> comment template.</p>
<p>The template can specify where comments are added. Note that the template can contain the variable <strong>${typecomment}</strong> and <strong>${filecomment}</strong> that will be substituted by the evaluation of the <strong>Types</strong> respectively <strong>Files</strong> comment template.</p>
</td>
</tr>
<tr>
<td valign="top" width="25%">
<p><i>Other file templates</i></p>
<p><em>Other file templates</em></p>
</td>
<td valign="top">
<p>File templates can be defined for other content types, e.g. Assembly or plain text.</p>

28
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_color.htm
View file

@ -12,44 +12,44 @@
<h1>Syntax Coloring preferences</h1>
<p>The <b>Syntax Coloring</b> preference panel specifies how C/C++ source code is rendered. Each element category (Code, Comments, and Preprocessor) contains a list of language elements that may be rendered with its own color and style.</p>
<p>Note that general text editor settings such as the background color can be configured on the general <b>Text Editors</b> preference pages. Fonts may be configured on the general <b>Colors and Fonts</b> preference page</p>
<p>The <strong>Syntax Coloring</strong> preference panel specifies how C/C++ source code is rendered. Each element category (Code, Comments, and Preprocessor) contains a list of language elements that may be rendered with its own color and style.</p>
<p>Note that general text editor settings such as the background color can be configured on the general <strong>Text Editors</strong> preference pages. Fonts may be configured on the general <strong>Colors and Fonts</strong> preference page</p>
<p><img src="../images/editor_color_preferences.png" alt="Syntax Coloring Preferences Page"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Syntax Coloring Preference Options</b></caption>
<caption><strong>Syntax Coloring Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Enable semantic highlighting</b></td>
<td><strong>Enable semantic highlighting</strong></td>
<td>Checkmark to activate semantic highlighting of specific structures in the elements listed.</td>
</tr>
<tr>
<td><b>Enable</b></td>
<td><strong>Enable</strong></td>
<td>Makes the selected element active for syntax coloring.</td>
</tr>
<tr>
<td><b>Color</b></td>
<td><strong>Color</strong></td>
<td>Specifies the color in which to display the selected element.</td>
</tr>
<tr>
<td><b>Bold</b></td>
<td>Makes the selected element <b>bold</b>.</td>
<td><strong>Bold</strong></td>
<td>Makes the selected element <strong>bold</strong>.</td>
</tr>
<tr>
<td><b>Italic</b></td>
<td>Makes the selected element <i>italic</i>.</td>
<td><strong>Italic</strong></td>
<td>Makes the selected element <em>italic</em>.</td>
</tr>
<tr>
<td><b>Strikethrough</b></td>
<td>Makes the selected element <s>strikethrough</s>.</td>
<td><strong>Strikethrough</strong></td>
<td>Makes the selected element <span class="linethrough">strikethrough</span>.</td>
</tr>
<tr>
<td><b>Underline</b></td>
<td>Makes the selected element <u>underlined</u>.</td>
<td><strong>Underline</strong></td>
<td>Makes the selected element <span class="underline">underlined</span>.</td>
</tr>
</tbody>
</table>

20
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_con_assist.htm
View file

@ -11,45 +11,45 @@
<h1>Content Assist preferences</h1>
<p>You can customize the Content Assist feature on the <b>Contents Assist</b> panel of the Preferences window. To change the Content Assist preferences click
<b>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Content Assist.</b></p>
<p>You can customize the Content Assist feature on the <strong>Contents Assist</strong> panel of the Preferences window. To change the Content Assist preferences click
<strong>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Content Assist.</strong></p>
<p><img src="../images/contentAssist_preferences.png" alt="Content Assist Preferences Dialog Box"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Content Assist Preference Options</b></caption>
<caption><strong>Content Assist Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Insert single proposals automatically</b></td>
<td><strong>Insert single proposals automatically</strong></td>
<td>Inserts an element into your code when the Content Assist feature finds only one proposal.</td>
</tr>
<tr>
<td><b>Insert common prefixes automatically</b></td>
<td><strong>Insert common prefixes automatically</strong></td>
<td>Inserts common prefixes.</td>
</tr>
<tr>
<td><b>Completion Proposal Filter</b></td>
<td><strong>Completion Proposal Filter</strong></td>
<td>Completion proposal filters may have been supplied with your Eclipse CDT distribution.
Completion proposal filters can sort and order the proposals provided by the Content Assist feature to best suit your needs.
Select the desired content assist filter from the list of available filters.</td>
</tr>
<tr>
<td><b>Enable "." as trigger</b></td>
<td><strong>Enable "." as trigger</strong></td>
<td>Enable to use "." as a trigger for auto-completion.</td>
</tr>
<tr>
<td><b>Enable "->" as trigger</b></td>
<td><strong>Enable "->" as trigger</strong></td>
<td>Enable to use "->" as a trigger for auto-completion.</td>
</tr>
<tr>
<td><b>Enable "::" as trigger</b></td>
<td><strong>Enable "::" as trigger</strong></td>
<td>Enable to use "::" as a trigger for auto-completion.</td>
</tr>
<tr>
<td><b>delay (ms)</b></td>
<td><strong>delay (ms)</strong></td>
<td>Specifies the number of milliseconds before Content Assist is activated.</td>
</tr>
</tbody>

12
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_con_assist_adv.htm
View file

@ -11,30 +11,30 @@
<h1>Advanced preferences</h1>
<p>Use the <b>Advanced</b> panel in the Preferences window to configure the behavior of the Content Assist (Ctrl+Space) command.</p>
<p>Use the <strong>Advanced</strong> panel in the Preferences window to configure the behavior of the Content Assist (Ctrl+Space) command.</p>
<p><img src="../images/contentAssist_adv_preferences.png" alt="Content Assist Preferences Dialog Box"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Advanced Content Assist Preference Options</b></caption>
<caption><strong>Advanced Content Assist Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Default Proposal Kindsy</b></td>
<td><strong>Default Proposal Kindsy</strong></td>
<td>Specifies the types of proposals Content Assist uses and the key bindings assigned.</td>
</tr>
<tr>
<td><b>Content Assist Cycling</b></td>
<td><strong>Content Assist Cycling</strong></td>
<td>Specifies the order and types of proposals Content Assist will cycle through.</td>
</tr>
<tr>
<td><b>Up</b></td>
<td><strong>Up</strong></td>
<td>Moves the selected proposal item up in the cycling list.</td>
</tr>
<tr>
<td><b>Down</b></td>
<td><strong>Down</strong></td>
<td>Moves the selected proposal item down in the cycling list.</td>
</tr>
</tbody>

30
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_folding.htm
View file

@ -11,10 +11,10 @@
<h1>Folding preferences</h1>
<p>You can customize the C/C++ editor folding behavior in the <b>Folding</b> panel of the Preferences window.</p>
<p>You can customize the C/C++ editor folding behavior in the <strong>Folding</strong> panel of the Preferences window.</p>
<p><img src="../images/editor_folding_preferences.png" alt="Editor Folding Preferences Window"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Folding Preference Options</b></caption>
<caption><strong>Folding Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="60%" valign="top" >
@ -22,57 +22,57 @@
</colgroup>
<tbody>
<tr>
<td><b>Option</b></td>
<td><b>Description</b></td>
<td><b>Default</b></td>
<td><strong>Option</strong></td>
<td><strong>Description</strong></td>
<td><strong>Default</strong></td>
</tr>
<tr>
<td><b>Enable folding when opening a new editor</b></td>
<td><strong>Enable folding when opening a new editor</strong></td>
<td>If enabled, apply folding rules to the new editor.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Select folding to use</b></td>
<td><strong>Select folding to use</strong></td>
<td>Select the folding to use from the available choices.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Enable folding of preprocessor branches (#if/#endif)</b></td>
<td><strong>Enable folding of preprocessor branches (#if/#endif)</strong></td>
<td>If enabled, fold preprocessor branches.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Macros</b></td>
<td><strong>Macros</strong></td>
<td>If enabled, fold macro definitions.</td>
<td>On</td>
</tr>
<tr>
<td><b>Functions</b></td>
<td><strong>Functions</strong></td>
<td>If enabled, fold functions.</td>
<td>Off</td>
</tr>
<tr>
<td><b>Methods</b></td>
<td><strong>Methods</strong></td>
<td>If enabled, fold methods.</td>
<td>Off</td>
</tr>
<tr>
<td><b>Structures</b></td>
<td><strong>Structures</strong></td>
<td>If enabled, fold structures.</td>
<td>On</td>
</tr>
<tr>
<td><b>Comments</b></td>
<td><strong>Comments</strong></td>
<td>If enabled, fold comments.</td>
<td>Off</td>
</tr>
<tr>
<td><b>Header Comments</b></td>
<td><strong>Header Comments</strong></td>
<td>If enabled, fold header comments.</td>
<td>On</td>
</tr>
<tr>
<td><b>Inactive Preprocessor Branches</b></td>
<td><strong>Inactive Preprocessor Branches</strong></td>
<td>If enabled, fold inactive processor branches.</td>
<td>On</td>
</tr>

16
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_gen.htm
View file

@ -11,38 +11,38 @@
<h1>Editor preferences</h1>
<p>Use the <b>Editor</b> preference panel to control the appearance of text highlighting in C/C++ editors.</p>
<p>Use the <strong>Editor</strong> preference panel to control the appearance of text highlighting in C/C++ editors.</p>
<p><img src="../images/editor_general_preferences.png" alt="Editor Preferences Dialog Box"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Editor Preference Options</b></caption>
<caption><strong>Editor Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Smart caret positioning in identifiers</b></td>
<td><strong>Smart caret positioning in identifiers</strong></td>
<td>If enabled, there are additional word boundaries inside identifiers.</td>
</tr>
<tr>
<td><b>Highlight matching brackets</b></td>
<td><strong>Highlight matching brackets</strong></td>
<td>When the cursor is beside a bracket, the matching bracket is highlighted.</td>
</tr>
<tr>
<td><b>Highlight inactive code</b></td>
<td><strong>Highlight inactive code</strong></td>
<td>Highlights inactive code when the cursor is positioned inside it.</td>
</tr>
<tr>
<td><b>Appearance color options</b></td>
<td><strong>Appearance color options</strong></td>
<td>Lists the items for which you can specify a color.</td>
</tr>
<tr>
<td><b>Color</b></td>
<td><strong>Color</strong></td>
<td>Specifies the color in which to display the selected item.</td>
</tr>
<tr>
<td><b>Documentation tool comments</b></td>
<td><strong>Documentation tool comments</strong></td>
<td>Specifies which documentation tool should be used to determine editor presentation and behaviors. This
enables editor features such as content-assist, documentation comment generation and syntax highlighting. The particular
tool selected here will be used for files that are not associated with a project, or where no project level preference has

8
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_hov.htm
View file

@ -11,21 +11,21 @@
<h1>Hovers preferences</h1>
<p>You can customize the appearance of the C/C++ editor hover behavior on the <b>Hovers</b> panel of the Preferences window.</p>
<p>You can customize the appearance of the C/C++ editor hover behavior on the <strong>Hovers</strong> panel of the Preferences window.</p>
<p><img src="../images/editor_hover_preferences.png" alt="Editor Hover Preferences Window"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Hovers Preference Options</b></caption>
<caption><strong>Hovers Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Enable editor problem annotation</b></td>
<td><strong>Enable editor problem annotation</strong></td>
<td>When selected problems found will be highlighted in the editor.</td>
</tr>
<tr>
<td><b>Text Hover key modifier preferences</b></td>
<td><strong>Text Hover key modifier preferences</strong></td>
<td>You can select hot-keys to enable alternate hover behavior. For example, a mouse over while pressing the &lt;Ctrl&gt; key will link to the element's source declaration.</td>
</tr>
</tbody>

2
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_mark_occurrences.htm
View file

@ -9,7 +9,7 @@
</head>
<body>
<h1>Mark Occurrences</h1>
<p>Indicate your preferences for the Mark Occurrences settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferences.MarkOccurrencesPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Mark Occurrences preference page"> <b>C/C++ &gt; Editor &gt; Mark Occurrences</b></a> preference page.</p>
<p>Indicate your preferences for the Mark Occurrences settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferences.MarkOccurrencesPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Mark Occurrences preference page"> <strong>C/C++ &gt; Editor &gt; Mark Occurrences</strong></a> preference page.</p>
<table border="1" cellspacing="0" cellpadding="5">
<thead>
<tr>

10
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_save_actions.htm
View file

@ -11,23 +11,23 @@
<h1>Save actions</h1>
<p>Use the <b>Save Actions</b> preference panel to configure actions performed by C/C++ editor while saving
a file. Click <b>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Save Actions</b> to make changes.</p>
<p>Use the <strong>Save Actions</strong> preference panel to configure actions performed by C/C++ editor while saving
a file. Click <strong>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Save Actions</strong> to make changes.</p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Editor Preference Options</b></caption>
<caption><strong>Editor Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Remove trailing whitespace</b></td>
<td><strong>Remove trailing whitespace</strong></td>
<td>While saving a file, C/C++ editor will remove spaces and tab characters from the end of edited
or all lines.</td>
</tr>
<tr>
<td><b>Ensure newline at the end of file</b></td>
<td><strong>Ensure newline at the end of file</strong></td>
<td>While saving a file, C/C++ editor will insert a newline at the end of the last line,
if the last line does not have it already.</td>
</tr>

20
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_scalability.htm
View file

@ -11,49 +11,49 @@
<h1>Scalability preferences</h1>
<p>Use the <b>Scalability</b> preference panel to configure options for dealing with large source files. Click <b>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Scalability</b> to make changes.</p>
<p>Use the <strong>Scalability</strong> preference panel to configure options for dealing with large source files. Click <strong>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Scalability</strong> to make changes.</p>
<img src="../images/editor_scalability_preferences.png" alt="Scalability Preferences">
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Scalability Preference Options</b></caption>
<caption><strong>Scalability Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Alert me when scalability mode will be turned on</b></td>
<td><strong>Alert me when scalability mode will be turned on</strong></td>
<td>If enabled, an information dialog pops up when a large file is opened
with the C/C++ Editor which exceeds the specified line limit.</td>
</tr>
<tr>
<td><b>Enable scalability mode options when the number of lines in the file is more than</b></td>
<td><strong>Enable scalability mode options when the number of lines in the file is more than</strong></td>
<td>If the number of lines in a file exceeds the specified number the C/C++ Editor will
enable scalability mode and all scalability mode options below will take effect.</td>
</tr>
<tr>
<td><b>Enable all scalability mode options</b></td>
<td><strong>Enable all scalability mode options</strong></td>
<td>If enabled, all options below are enabled, too.</td>
</tr>
<tr>
<td><b>Disable editor live parsing</b></td>
<td><strong>Disable editor live parsing</strong></td>
<td>If enabled, parsing while typing will be disabled.
This disables also other features like Outline view, semantic highlighting, folding, etc.</td>
</tr>
<tr>
<td><b>Disable semantic highlighting</b></td>
<td><strong>Disable semantic highlighting</strong></td>
<td>If enabled, C/C++ identifiers will not be colored.</td>
</tr>
<tr>
<td><b>Disable syntax coloring</b></td>
<td><strong>Disable syntax coloring</strong></td>
<td>If enabled, no coloring of keywords, comments and literals is done.</td>
</tr>
<tr>
<td><b>Disable parsing-based content assist proposals</b></td>
<td><strong>Disable parsing-based content assist proposals</strong></td>
<td>If enabled, content assist proposals which require parsing the file will not be available.</td>
</tr>
<tr>
<td><b>Disable content assist auto activation</b></td>
<td><strong>Disable content assist auto activation</strong></td>
<td>If enabled, content assist will not be activated automatically on trigger sequences, like '.', '::' or '->'.</td>
</tr>
</tbody>

22
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_editor_typing.htm
View file

@ -11,49 +11,49 @@
<h1>Typing preferences</h1>
<p>Use the <b>Typing</b> preference panel to assist in formatting input as you type. Click <b>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Typing</b> to make changes.</p>
<p>Use the <strong>Typing</strong> preference panel to assist in formatting input as you type. Click <strong>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Typing</strong> to make changes.</p>
<img src="../images/editor_typing_preferences.png" alt="Typing Preferences">
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Typing Preference Options</b></caption>
<caption><strong>Typing Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>"Strings"</b></td>
<td><strong>"Strings"</strong></td>
<td>If enabled, automatically close string quotes.</td>
</tr>
<tr>
<td><b>(Parenthesis) and [square] brackets</b></td>
<td><strong>(Parenthesis) and [square] brackets</strong></td>
<td>If enabled, automatically close parenthesis and square brackets.</td>
</tr>
<tr>
<td><b>&lt;Angle&gt; brackets</b></td>
<td><strong>&lt;Angle&gt; brackets</strong></td>
<td>If enabled, automatically close angle brackets.</td>
</tr>
<tr>
<td><b>{Braces}</b></td>
<td><strong>{Braces}</strong></td>
<td>If enabled, automatically close curly braces.</td>
</tr>
<tr>
<td><b>Tab key indents the current line</b></td>
<td><strong>Tab key indents the current line</strong></td>
<td>If enabled, indent the current line when the tab key is pressed.</td>
</tr>
<tr>
<td><b>Adjust indentation</b></td>
<td><strong>Adjust indentation</strong></td>
<td>Adjust the indentation of pasted text to match the current indentation level.</td>
</tr>
<tr>
<td><b>Wrap automatically</b></td>
<td><strong>Wrap automatically</strong></td>
<td>Enable to automatically wrap string literals when they exceed the max line length.</td>
</tr>
<tr>
<td><b>Escape text when pasting into a literal string</b></td>
<td><strong>Escape text when pasting into a literal string</strong></td>
<td>If enabled, special characters in pasted strings are escaped when pasted into an existing string literal.</td>
</tr>
<tr>
<td><b>Automatically indent - New lines and braces</b></td>
<td><strong>Automatically indent - New lines and braces</strong></td>
<td>If enabled, a new line or brace will be indented according to the <a href="cdt_u_c_code_style_pref.htm">Code Style preferences</a>.
If disabled, the default Text Editor indentation strategy is applied (copy indent from previous line)</td>
</tr>

6
doc/org.eclipse.cdt.doc.user/reference/cdt_u_c_pref.htm
View file

@ -11,18 +11,18 @@
<h1>C/C++ preferences</h1>
<p>The <b>C/C++</b> preference dialog box allows you to make changes to your C/C++ environment.</p>
<p>The <strong>C/C++</strong> preference dialog box allows you to make changes to your C/C++ environment.</p>
<p><img src="../images/c_cpp_preferences.png" alt="C/C++ Main Preferences Window"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>C/C++ Preference Options</b></caption>
<caption><strong>C/C++ Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td width="30%" valign="top"><b>Follow unindexed header files when producing the outline view</b></td>
<td width="30%" valign="top"><strong>Follow unindexed header files when producing the outline view</strong></td>
<td valign="top">Activate to do a more exhaustive search of header paths to build a more complete outline view.</td>
</tr>
</tbody>

16
doc/org.eclipse.cdt.doc.user/reference/cdt_u_call_hierarchy_view.htm
View file

@ -11,7 +11,7 @@
<h1>Call Hierarchy view</h1>
<p>The <b>Call Hierarchy</b> view shows the loaded callers and callees for a selected C/C++ function. Right-click a function name in a source file and select <b>Open Call Hierarchy</b> to open a Call Hierarchy view, if none is open, and show the function's callers.</p>
<p>The <strong>Call Hierarchy</strong> view shows the loaded callers and callees for a selected C/C++ function. Right-click a function name in a source file and select <strong>Open Call Hierarchy</strong> to open a Call Hierarchy view, if none is open, and show the function's callers.</p>
<p><img src="../images/view_call_hierarchy.png" alt="Call Hierarchy view" ></p>
@ -20,9 +20,9 @@
<p>The Call Hierarchy view toolbar commands include:</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td width="10%" align="left"><div align="center"><b>Command</b></div></td>
<td width="30%"><div align="center"><b>Name</b></div></td>
<td width="60%"><div align="center"><b>Description</b></div></td>
<td width="10%" align="left"><div align="center"><strong>Command</strong></div></td>
<td width="30%"><div align="center"><strong>Name</strong></div></td>
<td width="60%"><div align="center"><strong>Description</strong></div></td>
</tr>
<tr>
<td valign="top"><div align="center"><img src="../images/icon_show_next_reference.png" alt="Show Next Reference icon"></div></td>
@ -74,8 +74,8 @@
<p>The Call Hierarchy view context menu commands include:</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td width="25%"><div align="center"><b>Name</b></div></td>
<td width="75%"><div align="center"><b>Description</b></div></td>
<td width="25%"><div align="center"><strong>Name</strong></div></td>
<td width="75%"><div align="center"><strong>Description</strong></div></td>
</tr>
<tr>
<td valign="top">Show Reference</td>
@ -91,7 +91,7 @@
</tr>
<tr>
<td valign="top">Refactor...</td>
<td valign="top">Opens the <b>Rename global function</b> dialog.</td>
<td valign="top">Opens the <strong>Rename global function</strong> dialog.</td>
</tr>
<tr>
<td valign="top">Declarations</td>
@ -99,7 +99,7 @@
</tr>
<tr>
<td valign="top">References</td>
<td valign="top">Search the workspace, project, or working set for all function references and shows the result in the <b>Search</b> view.</td>
<td valign="top">Search the workspace, project, or working set for all function references and shows the result in the <strong>Search</strong> view.</td>
</tr>
</table>

26
doc/org.eclipse.cdt.doc.user/reference/cdt_u_code_temp.htm
View file

@ -11,46 +11,46 @@
<h1>Templates preferences</h1>
<p>Use the <b>Templates</b> preference panel to manipulate any of the common templates predefined within CDT or create your own. To modify, delete, export,
import, or create your own templates click <b>Window &gt; Preferences &gt; C/C++ &gt; Templates</b>.</p>
<p>Use the <strong>Templates</strong> preference panel to manipulate any of the common templates predefined within CDT or create your own. To modify, delete, export,
import, or create your own templates click <strong>Window &gt; Preferences &gt; C/C++ &gt; Templates</strong>.</p>
<img src="../images/code_templates.png" alt="Templates Preferences">
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Templates Preference Options</b></caption>
<caption><strong>Templates Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>New...</b></td>
<td>Opens the <b>New Template</b> dialog to create a new template.</td>
<td><strong>New...</strong></td>
<td>Opens the <strong>New Template</strong> dialog to create a new template.</td>
</tr>
<tr>
<td><b>Edit...</b></td>
<td>Opens the <b>Edit Template</b> dialog to edit the selected template.</td>
<td><strong>Edit...</strong></td>
<td>Opens the <strong>Edit Template</strong> dialog to edit the selected template.</td>
</tr>
<tr>
<td><b>Remove</b></td>
<td><strong>Remove</strong></td>
<td>Removes the selected templates from the list.</td>
</tr>
<tr>
<td><b>Restore Removed</b></td>
<td><strong>Restore Removed</strong></td>
<td>Restores templates deleted by the last Remove action.</td>
</tr>
<tr>
<td><b>Revert to Default</b></td>
<td><strong>Revert to Default</strong></td>
<td>Removes the last edits made to the selected template restoring it to it's unmodified state.</td>
</tr>
<tr>
<td><b>Import...</b></td>
<td><strong>Import...</strong></td>
<td>Imports a template.</td>
</tr>
<tr>
<td><b>Export...</b></td>
<td><strong>Export...</strong></td>
<td>Exports the selected templates.</td>
</tr>
<tr>
<td><b>Use code formatter</b></td>
<td><strong>Use code formatter</strong></td>
<td>Enable to apply the currently selected code style to the template.</td>
</tr>
</tbody>

12
doc/org.eclipse.cdt.doc.user/reference/cdt_u_console_view.htm
View file

@ -21,26 +21,26 @@ The console shows three different kinds of text, each in a different color:
<li>Standard input</li>
</ul>
<p>You can choose the different colors for these kinds of text on the preferences pages
(<b>Window &gt; Preferences &gt; Debug &gt; Console</b>).
(<strong>Window &gt; Preferences &gt; Debug &gt; Console</strong>).
</p>
<h2>Console View Context Menu</h2>
<p>When you right-click in the <b>Console</b> view
(or when you press <b>Shift+F10</b> when the focus is on the <b>Console</b> view),
<p>When you right-click in the <strong>Console</strong> view
(or when you press <strong>Shift+F10</strong> when the focus is on the <strong>Console</strong> view),
you see the following options:
</p>
<dl>
<dt>Edit options: Cut, Copy, Paste, Select All</dt>
<dd>These options perform the standard edit operations.
Which options are available depends on where the focus is in the
<b>Console</b> view.
<strong>Console</strong> view.
For example, you cannot paste text into the program output,
but you can paste text to the bottom of the file.
</dd>
<dt>Find/Replace</dt>
<dd>Opens a <b>Find/Replace</b> dialog
that operates only on the text in the <b>Console</b> view.</dd>
<dd>Opens a <strong>Find/Replace</strong> dialog
that operates only on the text in the <strong>Console</strong> view.</dd>
<dt>Go to Line</dt>
<dd>Opens a dialog that moves the focus to the line you specify.
The dialog also indicates the total number of lines in the console buffer.

30
doc/org.eclipse.cdt.doc.user/reference/cdt_u_cproj_view.htm
View file

@ -35,24 +35,24 @@ Files that you select in the C/C++ Projects view affect the information that is
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_con_min.png" alt="Minimize Icon"></td>
<td valign="top"><b>Minimize</b></td>
<td valign="top"><strong>Minimize</strong></td>
<td valign="top">Minimizes the view.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_con_max.png" alt="Maximize Icon"></td>
<td valign="top"><b>Maximize</b></td>
<td valign="top"><strong>Maximize</strong></td>
<td valign="top">Maximizes the view.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_back.png" alt="Back Icon"></td>
<td valign="top"><b>Back</b></td>
<td valign="top"><strong>Back</strong></td>
<td valign="top">This command displays the hierarchy that was displayed immediately prior to the current display.&nbsp;
For example, if you Go Into a resource, then the Back command in the resulting display returns the view to the same hierarchy from which you activated the
<i> Go Into</i> command. The hover help for this button tells you where it will take you. This command is similar to the Back button in a web browser.</td>
<em> Go Into</em> command. The hover help for this button tells you where it will take you. This command is similar to the Back button in a web browser.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_forward.png" alt="Forward Icon"></td>
<td valign="top"><b>Forward</b></td>
<td valign="top"><strong>Forward</strong></td>
<td valign="top">This command displays the hierarchy that was displayed immediately after the current display.&nbsp;
For example, if you've just selected the Back command, then selecting the Forward command in the resulting display returns the view to the same hierarchy from which you activated the Back command.&nbsp;The
hover help for this button tells you where it will take you.
@ -60,36 +60,36 @@ Files that you select in the C/C++ Projects view affect the information that is
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_up.png" alt="Up Icon"></td>
<td valign="top"><b>Up</b></td>
<td valign="top"><strong>Up</strong></td>
<td valign="top">This command displays the hierarchy of the parent of the current highest level resource. The hover help for this button tells you where it will take you.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_collapse_all.png" alt="Collapse All Icon"></td>
<td valign="top"><b>Collapse All</b></td>
<td valign="top"><strong>Collapse All</strong></td>
<td valign="top">This command collapses the tree expansion state of all resources in the view.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_link_with_editor.png" alt="Link with Editor Icon"></td>
<td valign="top"><b>Link with Editor</b></td>
<td valign="top"><strong>Link with Editor</strong></td>
<td valign="top">This command toggles whether the view selection is linked to the active editor.
When this option is selected, changing the active editor will automatically update the selection to the resource being edited.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_menu.png" alt="Menu Icon"></td>
<td valign="top"><b>Menu</b></td>
<td valign="top"><strong>Menu</strong></td>
<td valign="top">Click the black upside-down triangle icon to open a menu of items specific to the view.<br><br>
<dl>
<p><dt>Select Working Set</dt>
<dd>Opens the <B>Select Working Set</B> dialog to allow selecting a working set for the view.</dd></p>
<dd>Opens the <strong>Select Working Set</strong> dialog to allow selecting a working set for the view.</dd></p>
<p><dt>Deselect Working Set</dt>
<dd>Deselects the current working set. </dd></p>
<p><dt>Edit Active Working Set</dt>
<dd>Opens the <B>Edit Working Set</B> dialog to allow changing the current working set.</dd></p>
<dd>Opens the <strong>Edit Working Set</strong> dialog to allow changing the current working set.</dd></p>
<p><dt>Sort</dt>
<dd>This command sorts the resources in the view according to the selected schema:<br>
<ul>
<li><b>By Name</b>:&nbsp; Resources are sorted alphabetically, according to the full name of the resource (e.g., A.TXT, then B.DOC, then C.HTML, etc.)</li>
<li><b>By Type</b>:&nbsp; Resources are sorted alphabetically by file type/extension (e.g., all DOC files, then all HTML files, then all TXT files, etc.).</li>
<li><strong>By Name</strong>:&nbsp; Resources are sorted alphabetically, according to the full name of the resource (e.g., A.TXT, then B.DOC, then C.HTML, etc.)</li>
<li><strong>By Type</strong>:&nbsp; Resources are sorted alphabetically by file type/extension (e.g., all DOC files, then all HTML files, then all TXT files, etc.).</li>
</ul></p>
<p><dt>Filters</dt>
<dd>This command allows you to select filters to apply to the view so that you can show or hide various resources as needed.
@ -107,8 +107,8 @@ Files that you select in the C/C++ Projects view affect the information that is
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="34%">
<tr>
<td width="19%" align="left"><b>Icon</b></td>
<td width="81%"><b>Description</b></td>
<td width="19%" align="left"><strong>Icon</strong></td>
<td width="81%"><strong>Description</strong></td>
</tr>
<tr>
<td width="19%" align="left">

2
doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm
View file

@ -20,7 +20,7 @@
<dt>Target Name</dt><dd>Name of the Make Target.</dd>
<dt>Make Target</dt><dd>The reference to the make section in your makefile.</dd>
<dt>Use default</dt><dd>Select this checkbox to use the default make command. Clear the check box to specify a new make command.</dd>
<dt>Build command</dt><dd>If you clear the <b>Use default</b> checkbox type a new make command in this field.</dd>
<dt>Build command</dt><dd>If you clear the <strong>Use default</strong> checkbox type a new make command in this field.</dd>
<dt>Stop on first build error</dt> <dd>Stops the build when an error occurs.</dd>
<dt>Run all project builders</dt><dd>Runs additional project builders such as discovery.</dd>
</dl>

16
doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_brkpt_actions.htm
View file

@ -11,28 +11,28 @@
<h1>Breakpoint Actions preferences</h1>
<p>Use the <b>Breakpoint Actions</b> page in the Preferences window to create, edit, and remove breakpoint actions. The breakpoint actions defined here are available to all projects in the current workspace.</p>
<p>Use the <strong>Breakpoint Actions</strong> page in the Preferences window to create, edit, and remove breakpoint actions. The breakpoint actions defined here are available to all projects in the current workspace.</p>
<p><img src="../images/cdt_pref_brk_action.png" width="581" height="527" alt="Breakpoint Actions preference page"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Breakpoint Actions Preference Options</b></caption>
<caption><strong>Breakpoint Actions Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td width="30%" valign="top"><b>New...</b></td>
<td valign="top"><p>To create a new breakpoint action, click <b>New</b>. </p>
<td width="30%" valign="top"><strong>New...</strong></td>
<td valign="top"><p>To create a new breakpoint action, click <strong>New</strong>. </p>
</td>
</tr>
<tr>
<td width="30%" valign="top"><b>Edit...</b></td>
<td valign="top">To edit the currently selected action, click <b>Edit</b>. In the Action dialog box that appears, edit the action settings, then click <b>OK</b>. </td>
<td width="30%" valign="top"><strong>Edit...</strong></td>
<td valign="top">To edit the currently selected action, click <strong>Edit</strong>. In the Action dialog box that appears, edit the action settings, then click <strong>OK</strong>. </td>
</tr>
<tr>
<td width="30%" valign="top"><b>Delete</b></td>
<td valign="top">To delete the currently selected action, click <b>Delete</b>. </td>
<td width="30%" valign="top"><strong>Delete</strong></td>
<td valign="top">To delete the currently selected action, click <strong>Delete</strong>. </td>
</tr>
</tbody>
</table>

18
doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_pref.htm
View file

@ -11,41 +11,41 @@
<h1>Debug preferences</h1>
<p>The C/C++ <b>Debug</b> panel controls general settings for C/C++ debugging.</p>
<p>The C/C++ <strong>Debug</strong> panel controls general settings for C/C++ debugging.</p>
<p><img src="../images/view_debug_prefs.png" ALT="C/C++ Debug preferences panel" ></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>C/C++ Debug Preference Options</b></caption>
<caption><strong>C/C++ Debug Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td width="30%" valign="top"><b>Show full paths</b></td>
<td width="30%" valign="top"><strong>Show full paths</strong></td>
<td valign="top">Displays the full path of resources.</td>
</tr>
<tr>
<td width="30%" valign="top"><b>Default variable format</b></td>
<td width="30%" valign="top"><strong>Default variable format</strong></td>
<td valign="top">Specifies the number system in which to display variables (Natural, Hexadecimal, Decimal, or Binary).</td>
</tr>
<tr>
<td width="30%" valign="top"><b>Default expression format</b></td>
<td width="30%" valign="top"><strong>Default expression format</strong></td>
<td valign="top">Specifies the number system in which to display expressions (Natural, Hexadecimal, Decimal, or Binary).</td>
</tr>
<tr>
<td width="30%" valign="top"><b>Default register format</b></td>
<td width="30%" valign="top"><strong>Default register format</strong></td>
<td valign="top">Specifies the number system in which to display registers (Natural, Hexadecimal, Decimal, or Binary).</td>
</tr>
<tr>
<td width="30%" valign="top"><b>Maximum number of displayed instructions</b></td>
<td width="30%" valign="top"><strong>Maximum number of displayed instructions</strong></td>
<td valign="top">The maximum number of assembler instructions displayed in the Disassembly view.</td>
</tr>
<tr>
<td width="30%" valign="top"><b>Color of source lines</b></td>
<td width="30%" valign="top"><strong>Color of source lines</strong></td>
<td valign="top">The color of source lines in the Disassembly view if mixed source/disassembly code is shown.</td>
</tr>
<tr>
<td valign="top"><b>Show source files in binaries </b></td>
<td valign="top"><strong>Show source files in binaries </strong></td>
<td valign="top">Show source files associated with project binaries. </td>
</tr>
</tbody>

18
doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_src.htm
View file

@ -11,13 +11,13 @@
<h1>Common Source Lookup Path preference</h1>
<p>Use the <b>Common Source Lookup Path</b> preference page to add or remove source containers.</p>
<p>Use the <strong>Common Source Lookup Path</strong> preference page to add or remove source containers.</p>
<p><img src="../images/debug_src_pref.png" alt="Debug Source Code Locations Preferences" width="627" height="544"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption>
<b>Common Source Lookup Path Options </b>
<strong>Common Source Lookup Path Options </strong>
</caption>
<colgroup>
<col width="30%" valign="top" >
@ -25,8 +25,8 @@
</colgroup>
<tbody>
<tr>
<td width="99" valign="top"><b>Add...</b></td>
<td width="475"><p>Opens the <b>Add Source</b> dialog to insert a new source container of one of the following types:</p>
<td width="99" valign="top"><strong>Add...</strong></td>
<td width="475"><p>Opens the <strong>Add Source</strong> dialog to insert a new source container of one of the following types:</p>
<ul>
<li>File System Directory</li>
<li>Path Mapping</li>
@ -37,19 +37,19 @@
</td>
</tr>
<tr>
<td valign="top"><b>Edit...</b></td>
<td>Opens the <b>Edit File System Director</b>y dialog to modify the currently selected souce container.</td>
<td valign="top"><strong>Edit...</strong></td>
<td>Opens the <strong>Edit File System Director</strong>y dialog to modify the currently selected souce container.</td>
</tr>
<tr>
<td valign="top"><b>Remove</b></td>
<td valign="top"><strong>Remove</strong></td>
<td>Remove the currently selected souce container.</td>
</tr>
<tr>
<td valign="top"><b>Up</b></td>
<td valign="top"><strong>Up</strong></td>
<td>Move the currently selected source container higher in the list.</td>
</tr>
<tr>
<td valign="top"><b>Down</b></td>
<td valign="top"><strong>Down</strong></td>
<td>Move the currently selected source container lower in the list.</td>
</tr>
</tbody>

82
doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_view.htm
View file

@ -14,7 +14,7 @@
<h1>Debug view</h1>
<p>The <b>Debug</b> view shows the target debugging information in a tree hierarchy.</p>
<p>The <strong>Debug</strong> view shows the target debugging information in a tree hierarchy.</p>
<p><img src="../images/view_debug.png" width="529" height="252" alt="Debug view" ></p>
<p>The number beside the thread label is a reference counter, not a
thread identification number (TID).</p>
@ -78,42 +78,42 @@ from Debug view.</p>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_terminate_all.png" width="21" height="20" alt="Remove all Terminated launches icon">
</center> </td>
<td align="left" valign="top"><b>Remove All Terminated Launches </b></td>
<td align="left" valign="top"><strong>Remove All Terminated Launches </strong></td>
<td align="left" valign="top">Clears all terminated processes in Debug view</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_restart.png" width="20" height="18" alt="Restart icon">
</center> </td>
<td align="left" valign="top"><b>Restart</b></td>
<td align="left" valign="top"><strong>Restart</strong></td>
<td align="left" valign="top">Starts a new debug session for the selected process</td>
</tr>
<tr>
<td align="left" valign="top"><center>
<img src="../images/icon_db_resume.png" width="19" height="14" alt="Resume icon">
</center> </td>
<td align="left" valign="top"><b>Resume</b></td>
<td align="left" valign="top"><strong>Resume</strong></td>
<td align="left" valign="top">Select the Resume command to resume execution of the currently suspended debug target.</td>
</tr>
<tr>
<td align="left" valign="top"><center>
<img src="../images/icon_db_suspend.png" width="17" height="17" alt="Suspend icon">
</center> </td>
<td align="left" valign="top"><b>Suspend</b></td>
<td align="left" valign="top"><strong>Suspend</strong></td>
<td align="left" valign="top">Select the Suspend command to halt execution of the currently selected thread in a debug target.</td>
</tr>
<tr>
<td width="45" align="left" valign="top"> <center>
<img src="../images/icon_db_terminate.png" width="17" height="15" alt="Terminate icon">
</center> </td>
<td width="211" align="left" valign="top"><b>Terminate </b></td>
<td width="211" align="left" valign="top"><strong>Terminate </strong></td>
<td width="638" align="left" valign="top">Ends the selected debug session and/or process. The impact of this action depends on the type of the item selected in the Debug view.</td>
</tr>
<tr>
<td width="45" align="left" valign="top"> <center>
<img border="0" src="../images/icon_disconnect.gif" width="16" height="16" alt="Disconnect icon">
</center> </td>
<td width="211" align="left" valign="top"><b>Disconnect</b></td>
<td width="211" align="left" valign="top"><strong>Disconnect</strong></td>
<td width="638" align="left" valign="top">Detaches the debugger from the selected process (useful for
debugging attached processes).</td>
</tr>
@ -121,48 +121,48 @@ debugging attached processes).</td>
<td align="left" valign="top"><center>
<img src="../images/icon_db_stepinto.png" width="18" height="14" alt="Step Into icon">
</center> </td>
<td align="left" valign="top"><b>Step Into </b></td>
<td align="left" valign="top"><strong>Step Into </strong></td>
<td>Select to execute the current line, including any routines, and proceed to the next statement.</td>
</tr>
<tr>
<td align="left" valign="top"><center>
<img src="../images/icon_db_stepover.png" width="19" height="14" alt="Step Over icon">
</center> </td>
<td align="left" valign="top"><b>Step Over </b></td>
<td align="left" valign="top"><strong>Step Over </strong></td>
<td>Select to execute the current line, following execution inside a routine.</td>
</tr>
<tr>
<td align="left" valign="top"><center>
<img src="../images/icon_db_stepreturn.png" width="17" height="14" alt="Step Return icon">
</center> </td>
<td align="left" valign="top"><b>Step Return </b></td>
<td align="left" valign="top"><strong>Step Return </strong></td>
<td>Select to continue execution to the end of the current routine, then follow execution to the routine&rsquo;s caller.</td>
</tr>
<tr>
<td align="left" valign="top"><center>
<img src="../images/icon_db_drop_to_frame.png" width="18" height="17" alt="Drop to Frame icon">
</center> </td>
<td align="left" valign="top"><b>Drop to Frame </b></td>
<td align="left" valign="top"><strong>Drop to Frame </strong></td>
<td align="left" valign="top">Select the Drop to Frame command to re-enter the selected stack frame in the Debug view.</td>
</tr>
<tr>
<td align="left" valign="top"><center>
<img src="../images/icon_db_step_mode.png" width="19" height="14" alt="Instruction Stepping Mode icon">
</center> </td>
<td align="left" valign="top"><b>Instruction Stepping Mode </b></td>
<td align="left" valign="top"><strong>Instruction Stepping Mode </strong></td>
<td align="left" valign="top">Activate to enable instruction stepping mode to examine a program as it steps into disassembled code. </td>
</tr>
<tr>
<td align="left" valign="top"><center>
<img src="../images/icon_db_use_step_filters.png" width="18" height="17" alt="Use Step Filters icon">
</center> </td>
<td align="left" valign="top"><b>Use Step Filters </b></td>
<td align="left" valign="top"><strong>Use Step Filters </strong></td>
<td align="left" valign="top">Select the Use Step Filters command to change whether step filters should be used in the Debug view.</td>
</tr>
<tr>
<td align="left" valign="top"><center>
</center> </td>
<td align="left" valign="top"><b>Menu</b></td>
<td align="left" valign="top"><strong>Menu</strong></td>
<td align="left" valign="top"><p>Use the Debug view menu to:</p>
<ul>
<li>change the layout of debug view (tree vs. breadcrumb)</li>
@ -178,112 +178,112 @@ debugging attached processes).</td>
<p>The Debug view context menu commands include:</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td align="center"><b>Icons</b></td>
<td align="center"><b>Name</b></td>
<td align="center"><b>Description</b></td>
<td align="center"><strong>Icons</strong></td>
<td align="center"><strong>Name</strong></td>
<td align="center"><strong>Description</strong></td>
</tr>
<tr>
<td align="left"><center>
<img src="../images/icon_db_copy_stack.png" width="20" height="19" alt="Copy Stack icon">
</center> </td>
<td><b>Copy Stack </b></td>
<td><strong>Copy Stack </strong></td>
<td>Copies the selected stack of suspended threads as well as the state of the running threads to the clipboard. </td>
</tr>
<tr>
<td align="left"><center>
</center> </td>
<td><b>Find...</b></td>
<td><strong>Find...</strong></td>
<td>Opens the debug view element searching dialog.</td>
</tr>
<tr>
<td align="left"><center>
<img src="../images/icon_db_drop_to_frame.png" width="18" height="17" alt="Drop to Frame icon">
</center> </td>
<td><b>Drop To Frame </b></td>
<td><strong>Drop To Frame </strong></td>
<td>Select the Drop to Frame command to re-enter the selected stack frame in the Debug view.</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_restart.png" width="20" height="18" alt="Restart icon">
</center> </td>
<td align="left" valign="top"><b>Restart</b></td>
<td align="left" valign="top"><strong>Restart</strong></td>
<td align="left" valign="top">Starts a new debug session for the selected process</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_stepinto.png" width="18" height="14" alt="Step Into icon">
</center> </td>
<td align="left" valign="top"><b>Step Into </b></td>
<td align="left" valign="top"><strong>Step Into </strong></td>
<td>Select to execute the current line, including any routines, and proceed to the next statement.</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_stepover.png" width="19" height="14" alt="Step Over icon">
</center> </td>
<td align="left" valign="top"><b>Step Over </b></td>
<td align="left" valign="top"><strong>Step Over </strong></td>
<td>Select to execute the current line, following execution inside a routine.</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_stepreturn.png" width="17" height="14" alt="Step Return icon">
</center> </td>
<td align="left" valign="top"><b>Step Return </b></td>
<td align="left" valign="top"><strong>Step Return </strong></td>
<td>Select to continue execution to the end of the current routine, then follow execution to the routine&rsquo;s caller.</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_step_mode.png" width="19" height="14" alt="Instruction Stepping Mode icon">
</center> </td>
<td align="left" valign="top"><b>Instruction Stepping Mode </b></td>
<td align="left" valign="top"><strong>Instruction Stepping Mode </strong></td>
<td align="left" valign="top">Activate to enable instruction stepping mode to examine a program as it steps into disassembled code. </td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_use_step_filters.png" width="18" height="17" alt="Use Step Filters icon">
</center> </td>
<td align="left" valign="top"><b>Use Step Filters </b></td>
<td align="left" valign="top"><strong>Use Step Filters </strong></td>
<td align="left" valign="top">Toggles step filters on/off. When on, all step functions apply step filters.</td>
</tr>
<tr>
<td align="left"><center>
<img src="../images/icon_resume_signal.png" width="17" height="15" alt="Resume without signal icon">
</center> </td>
<td><b>Resume Without Signal </b></td>
<td><strong>Resume Without Signal </strong></td>
<td valign="top">Resume program execution after receiving the signal. </td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_resume.png" width="19" height="14" alt="Resume icon">
</center> </td>
<td align="left" valign="top"><b>Resume</b></td>
<td align="left" valign="top"><strong>Resume</strong></td>
<td align="left" valign="top">Select the Resume command to resume execution of the currently suspended debug target.</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_suspend.png" width="17" height="17" alt="Suspend icon">
</center> </td>
<td align="left" valign="top"><b>Suspend</b></td>
<td align="left" valign="top"><strong>Suspend</strong></td>
<td align="left" valign="top">Select the Suspend command to halt execution of the currently selected thread in a debug target.</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_terminate.png" width="17" height="15" alt="Terminate icon">
</center> </td>
<td align="left" valign="top"><b>Terminate </b></td>
<td align="left" valign="top"><strong>Terminate </strong></td>
<td align="left" valign="top">Ends the selected debug session and/or process. The impact of this action depends on the type of the item selected in the Debug view.</td>
</tr>
<tr>
<td align="left"><center>
<img src="../images/icon_db_terminate_relaunch.png" width="19" height="17" alt="Terminate and Relaunch icon">
</center> </td>
<td><b>Terminate and Relaunch </b></td>
<td><strong>Terminate and Relaunch </strong></td>
<td>Select the Terminate and Relaunch command to terminate the selected debug target and then relaunch it.</td>
</tr>
<tr>
<td align="left" valign="top"> <center>
<img border="0" src="../images/icon_disconnect.gif" width="16" height="16" alt="Disconnect icon">
</center> </td>
<td align="left" valign="top"><b>Disconnect</b></td>
<td align="left" valign="top"><strong>Disconnect</strong></td>
<td align="left" valign="top">Detaches the debugger from the selected process (useful for
debugging attached processes)</td>
</tr>
@ -291,54 +291,54 @@ debugging attached processes).</td>
<td align="left" valign="top"> <center>
<img src="../images/icon_db_terminate_all.png" width="21" height="20" alt="Remote all Terminated icon">
</center> </td>
<td align="left" valign="top"><b>Remove All Terminated </b></td>
<td align="left" valign="top"><strong>Remove All Terminated </strong></td>
<td align="left" valign="top">Clears all terminated processes in Debug view</td>
</tr>
<tr>
<td align="left"><center>
<img src="../images/icon_db_relaunch.png" width="21" height="19" alt="Relaunch icon">
</center> </td>
<td><b>Relaunch</b></td>
<td><strong>Relaunch</strong></td>
<td>This command relaunches the selected debug target. </td>
</tr>
<tr>
<td align="left"><center>
</center> </td>
<td><b>Edit...</b></td>
<td><strong>Edit...</strong></td>
<td>Opens the launch configuration dialog, allowing you to make changes. </td>
</tr>
<tr>
<td align="left"><center>
<img src="../images/icon_db_edit_src_lookup.png" width="20" height="18" alt="Edit Source Lookup icon">
</center> </td>
<td><b>Edit Source Lookup... </b></td>
<td><strong>Edit Source Lookup... </strong></td>
<td valign="top">Opens the source lookup dialog, allowing you to make changes. </td>
</tr>
<tr>
<td align="left"><center>
</center> </td>
<td><b>Lookup Source </b></td>
<td><strong>Lookup Source </strong></td>
<td>Select to force a source lookup to take place. </td>
</tr>
<tr>
<td align="left"><center>
<img src="../images/icon_db_terminate_remove.png" width="19" height="17" alt="Terminate and Remove icon">
</center> </td>
<td><b>Terminate and Remove </b></td>
<td><strong>Terminate and Remove </strong></td>
<td>Terminates the selected debug target and removes it from the view. </td>
</tr>
<tr>
<td align="left"><center>
<img src="../images/icon_db_terminate_all2.png" width="19" height="18" alt="Terminate all icon">
</center> </td>
<td><b>Terminate All </b></td>
<td><strong>Terminate All </strong></td>
<td>Terminates all active launches in the view. </td>
</tr>
<tr>
<td align="left"><center>
</center> </td>
<td><b>Properties</b></td>
<td>Opens the <b>Properties for</b> window showing the process properties. </td>
<td><strong>Properties</strong></td>
<td>Opens the <strong>Properties for</strong> window showing the process properties. </td>
</tr>
</table>

2
doc/org.eclipse.cdt.doc.user/reference/cdt_u_debug.htm
View file

@ -11,7 +11,7 @@
<h1>Debug page, Preferences window</h1>
<p>You can manipulate any of the common predefined debug settings by clicking <b>Window &gt; Preferences &gt; C/C++ &gt; Debug</b>.</p>
<p>You can manipulate any of the common predefined debug settings by clicking <strong>Window &gt; Preferences &gt; C/C++ &gt; Debug</strong>.</p>
<img src="../images/debug_pref.png" alt="Debug Preferences">
<dl>

8
doc/org.eclipse.cdt.doc.user/reference/cdt_u_dissassembly_view.htm
View file

@ -11,7 +11,7 @@
<h1>Disassembly view</h1>
<p>The <b>Disassembly</b> view shows the loaded program as assembler instructions mixed with source code for comparison. The currently executing line is indicated by an arrow marker and highlighted in the view. You can do the following tasks in the Disassembly view:</p>
<p>The <strong>Disassembly</strong> view shows the loaded program as assembler instructions mixed with source code for comparison. The currently executing line is indicated by an arrow marker and highlighted in the view. You can do the following tasks in the Disassembly view:</p>
<ul>
<li>Set breakpoints at the start of any assembler instruction</li>
<li>Enable and disable breakpoints and their set their properties </li>
@ -26,9 +26,9 @@
<p>The Disassembly view context menu commands include:</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td width="19%" align="left"><div align="center"><b>Command</b></div></td>
<td width="35%"><div align="center"><b>Name</b></div></td>
<td width="46%"><div align="center"><b>Description</b></div></td>
<td width="19%" align="left"><div align="center"><strong>Command</strong></div></td>
<td width="35%"><div align="center"><strong>Name</strong></div></td>
<td width="46%"><div align="center"><strong>Description</strong></div></td>
</tr>
<tr>
<td valign="top"><div align="center"><img src="../images/icon_run_to_line.png" alt="Run to line icon" width="20" height="17"></div></td>

24
doc/org.eclipse.cdt.doc.user/reference/cdt_u_environment_pref.htm
View file

@ -12,11 +12,11 @@
<h1>Environment preferences</h1>
<p>Define environment variables and how they are used in the <b>Environment</b> preference panel. </p>
<p>Define environment variables and how they are used in the <strong>Environment</strong> preference panel. </p>
<p><img src="../images/view_environment_prefs.png" alt="Environment Preference" width="721" height="641"></p>
<table width="600" cellpadding="5" cellspacing="0" border="1" >
<caption>
<b>Environment Options</b>
<strong>Environment Options</strong>
</caption>
<colgroup>
<col width="30%" valign="top" >
@ -24,36 +24,36 @@
</colgroup>
<tbody>
<tr>
<td width="171" valign="top"><b>Environment variables to set </b></td>
<td width="171" valign="top"><strong>Environment variables to set </strong></td>
<td width="503" valign="top">Shows a list of the environment variables and their value. </td>
</tr>
<tr>
<td valign="top"><b>New...</b></td>
<td valign="top">Click to open the <b>New Variable</b> dialog where you define the variable name and value. </td>
<td valign="top"><strong>New...</strong></td>
<td valign="top">Click to open the <strong>New Variable</strong> dialog where you define the variable name and value. </td>
</tr>
<tr>
<td valign="top"><b>Select...</b></td>
<td valign="top"><p>Click to open the <b>Select variables</b> dialog. </p> </td>
<td valign="top"><strong>Select...</strong></td>
<td valign="top"><p>Click to open the <strong>Select variables</strong> dialog. </p> </td>
</tr>
<tr>
<td valign="top"><b>Edit...</b></td>
<td valign="top"><strong>Edit...</strong></td>
<td valign="top">Click to edit the currently selected variable and its value. </td>
</tr>
<tr>
<td valign="top"><b>Remove</b></td>
<td valign="top"><strong>Remove</strong></td>
<td valign="top">Click to remove the currently selected variable. </td>
</tr>
<tr>
<td valign="top"><b>Undefine</b></td>
<td valign="top"><strong>Undefine</strong></td>
<td valign="top"><p>Click to undefine the currently selected variable.</p>
<p>NOTE: Some variables, like <span class="userinput">PATH</span>, have special meaning and cannot be undefined. </p></td>
</tr>
<tr>
<td valign="top"><b>Append variables to native environment </b></td>
<td valign="top"><strong>Append variables to native environment </strong></td>
<td valign="top">Activate this checkbox to append the variables to the native environment during execution. </td>
</tr>
<tr>
<td valign="top"><b>Replace native environment with specified one </b></td>
<td valign="top"><strong>Replace native environment with specified one </strong></td>
<td valign="top">Activate this checkbox to replace the native environment with these variables, restoring the native environment upon completion. </td>
</tr>
</tbody>

32
doc/org.eclipse.cdt.doc.user/reference/cdt_u_fileprop_discovery.htm
View file

@ -20,7 +20,7 @@ of a C/C++ project's properties window.<br>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Discovery options</b></caption>
<caption><strong>Discovery options</strong></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
@ -28,15 +28,15 @@ of a C/C++ project's properties window.<br>
</colgroup>
<tbody>
<tr>
<td><b>Configuration</b></td>
<td><strong>Configuration</strong></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><b>Manage configurations</b></td>
<td><strong>Manage configurations</strong></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><b>Exclude resource from build</b></td>
<td><strong>Exclude resource from build</strong></td>
<td>Excludes the selected file from the build process.</td>
</tr>
<tr>
@ -44,28 +44,28 @@ of a C/C++ project's properties window.<br>
<td>Shows a list of language specific compilers. Select a language from the list.</td>
</tr>
<tr>
<td><b>Automate discovery of paths and symbols</b></td>
<td>Scans the build output to populate the path and symbol tables, such as symbol definitions, system include directories, local include directories, macros files, and include files. If this option is not selected, the <b>Discovery profile options</b> below do not appear.</td>
<td><strong>Automate discovery of paths and symbols</strong></td>
<td>Scans the build output to populate the path and symbol tables, such as symbol definitions, system include directories, local include directories, macros files, and include files. If this option is not selected, the <strong>Discovery profile options</strong> below do not appear.</td>
</tr>
<tr>
<td><b>Report path detection problems</b></td>
<td><strong>Report path detection problems</strong></td>
<td>Sets the notification of diagnostic errors for include paths that the Eclipse CDT is unable to resolve as it parses the build output.</td>
</tr>
<tr>
<td><b>Discovery profile options</b></td>
<td>Indicates the discovery profile to use for paths and symbol detection. The type of <b>Configuration</b> and <b>Discovery Profile Scope</b> you specify determine what which <b>Discovery Profile</b> options display on this tab. This set of controls is profile-specific. It may vary from one profile to another.</td>
<td><strong>Discovery profile options</strong></td>
<td>Indicates the discovery profile to use for paths and symbol detection. The type of <strong>Configuration</strong> and <strong>Discovery Profile Scope</strong> you specify determine what which <strong>Discovery Profile</strong> options display on this tab. This set of controls is profile-specific. It may vary from one profile to another.</td>
</tr>
<tr>
<td><b>Enable generate scanner info command</b></td>
<td><strong>Enable generate scanner info command</strong></td>
<td>Enables the retrieval of information from the scanner. If it is not selected, the includes will be populated with default gcc system includes; Eclipse gathers the compiler settings based on the specified toolchain. This means that the Eclipse CDT can obtain the default gcc system includes to associate with the project.
<p>When selected, you can specify any required compiler specific commands in the <b>Compiler invocation command</b> field.</p>
<p>When selected, you can specify any required compiler specific commands in the <strong>Compiler invocation command</strong> field.</p>
</td>
</tr>
<tr>
<td><b>Compiler invocation command</b></td>
<td>Indicates the compiler specific command used to invoke the compiler (such as <tt>gcc</tt>, or more complicated commands used to perform all necessary steps for compiling C/C++ source files into .o files, and linking the object files and libraries into an executable program. For example, the command <b>gcc -E -P -v hello.c | hello.cpp</b> reads a compiler's configuration file and prints out information that includes the compiler's internally defined preprocessor symbols and include search paths. The information is complementary to the scanner configuration discovered when the output is parsed (if you've enabled the <b>Enable build output scanner info discovery</b> option), and is added to the project's scanner configuration. You can click <b>Browse</b> to locate this command, if required.
<td><strong>Compiler invocation command</strong></td>
<td>Indicates the compiler specific command used to invoke the compiler (such as <span class="typewriter">gcc</span>, or more complicated commands used to perform all necessary steps for compiling C/C++ source files into .o files, and linking the object files and libraries into an executable program. For example, the command <strong>gcc -E -P -v hello.c | hello.cpp</strong> reads a compiler's configuration file and prints out information that includes the compiler's internally defined preprocessor symbols and include search paths. The information is complementary to the scanner configuration discovered when the output is parsed (if you've enabled the <strong>Enable build output scanner info discovery</strong> option), and is added to the project's scanner configuration. You can click <strong>Browse</strong> to locate this command, if required.
<p><b>Note:</b> The parsing of build output for scanner information is compiler specific. For example, the GNU toolchain compilers (gcc and g++) use -I for include paths, and -D for symbol definitions. Consult your compiler specific documentation for more information about scanner information commands, such as the following gcc commands:</p>
<p><strong>Note:</strong> The parsing of build output for scanner information is compiler specific. For example, the GNU toolchain compilers (gcc and g++) use -I for include paths, and -D for symbol definitions. Consult your compiler specific documentation for more information about scanner information commands, such as the following gcc commands:</p>
<ul>
<li><samp>-D <span style="font-style: italic;">name</span></samp></li>
<li><samp>-I</samp></li>
@ -84,8 +84,8 @@ of a C/C++ project's properties window.<br>
</td>
</tr>
<tr>
<td><b>Browse</b></td>
<td>Click to browse for a file to include in the compiler invocation command. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
<td><strong>Browse</strong></td>
<td>Click to browse for a file to include in the compiler invocation command. This button is only visible when <strong>Configuration</strong> is set to Release and the <strong>Discovery Profiles Scope</strong> is set to <strong>Configuration-wide</strong>.</td>
</tr>
</tbody>
</table>

8
doc/org.eclipse.cdt.doc.user/reference/cdt_u_fileprop_lang_mapp.htm
View file

@ -17,7 +17,7 @@
<table cellpadding="5" cellspacing="0" border="1" >
<caption>
<b>Language Mappings Options</b>
<strong>Language Mappings Options</strong>
</caption>
<colgroup>
<col width="30%" valign="top" >
@ -25,15 +25,15 @@
</colgroup>
<tbody>
<tr>
<td width="171" valign="top"><b>Content Type </b></td>
<td width="171" valign="top"><strong>Content Type </strong></td>
<td width="503" valign="top">The content type associated with the language. </td>
</tr>
<tr>
<td valign="top"><b>Configuration</b></td>
<td valign="top"><strong>Configuration</strong></td>
<td valign="top">Shows the list of configurations for the selected content type. </td>
</tr>
<tr>
<td valign="top"><b>Language</b></td>
<td valign="top"><strong>Language</strong></td>
<td valign="top">Shows the list of corresponding languages associated with the configurations in the list for the specific content type. </td>
</tr>
</tbody>

2
doc/org.eclipse.cdt.doc.user/reference/cdt_u_fileprop_lng.htm
View file

@ -8,7 +8,7 @@
</head>
<body>
<h1>C/C++ File Properties, Language mappings</h1>
<p>Customize the use of C/C++ language associations in the <b>Language Mappings</b> preference panel for individual files. </p>
<p>Customize the use of C/C++ language associations in the <strong>Language Mappings</strong> preference panel for individual files. </p>
<p><img img="" src="../images/prop_file_lang.png"
alt="C/C++ Project Properties, Language mapping"></p>
<p></p>

8
doc/org.eclipse.cdt.doc.user/reference/cdt_u_fileprop_toolsettings.htm
View file

@ -14,7 +14,7 @@ Customizes the tools and tool options used in your build configuration.
<p></p>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Tool Settings options</b></caption>
<caption><strong>Tool Settings options</strong></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
@ -22,11 +22,11 @@ Customizes the tools and tool options used in your build configuration.
</colgroup>
<tbody>
<tr>
<td><b>Configuration</b></td>
<td><strong>Configuration</strong></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><b>Manage configurations</b></td>
<td><strong>Manage configurations</strong></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
@ -39,7 +39,7 @@ Customizes the tools and tool options used in your build configuration.
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT source files</p>
<p><strong>Available for:</strong> CDT source files</p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"

22
doc/org.eclipse.cdt.doc.user/reference/cdt_u_find_replace.htm
View file

@ -8,25 +8,25 @@
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<h1>C/C++ Find/Replace</h1>
<p><b>Ctrl+F</b> (or <b>Edit > Find/Replace</b>) displays the <b>Find/Replace</b> dialog.
<p><strong>Ctrl+F</strong> (or <strong>Edit > Find/Replace</strong>) displays the <strong>Find/Replace</strong> dialog.
Here you can specify text to search for and optionally text with which to replace it.
</p>
<p><img src="../images/find_replace_dialog.png" alt="Find and Replace Dialog Box" ></p>
<p>You can specify:</p>
<ul>
<li>The direction (forward or back from the current cursor location)</li>
<li>The scope (<b>All</b> for the whole file or <b>Selected Lines</b> to search only
<li>The scope (<strong>All</strong> for the whole file or <strong>Selected Lines</strong> to search only
within the highlighted area)</li>
<li>Whether the search is <b>Case Sensitive</b> or <b>Whole Word</b>.
<li>Whether the search is <strong>Case Sensitive</strong> or <strong>Whole Word</strong>.
You can also specify whether the search wraps at the end of the file.</li>
</ul>
<p>If you close the <b>Find/Replace</b> dialog with text in the <b>Find</b> field,
you can use <b>Ctrl+K</b> (or <b>Edit > Find Next</b>) or
<b>Ctrl+Shift+K</b> (or <b>Edit > Find Previous</b>) to go to the next
<p>If you close the <strong>Find/Replace</strong> dialog with text in the <strong>Find</strong> field,
you can use <strong>Ctrl+K</strong> (or <strong>Edit > Find Next</strong>) or
<strong>Ctrl+Shift+K</strong> (or <strong>Edit > Find Previous</strong>) to go to the next
occurrence of that text.
The directions for &quot;Next&quot; and &quot;Previous&quot;
are not affected by the <b>Direction</b> setting in the <b>Find/Replace</b> dialog.
are not affected by the <strong>Direction</strong> setting in the <strong>Find/Replace</strong> dialog.
</p>
<p class="note"><span class="notetitle">Note: </span>
@ -34,17 +34,17 @@ Wildcards are not currently supported for searches.</p>
<h2>Incremental Find</h2>
<p>You can also choose <b>Incremental Find</b> from the <b>Find/Replace</b> dialog.
With this option selected, each letter you type in the <b>Find</b> field
<p>You can also choose <strong>Incremental Find</strong> from the <strong>Find/Replace</strong> dialog.
With this option selected, each letter you type in the <strong>Find</strong> field
causes the editor focus to move to the first complete occurrence of the text
you are typing.
You can also use incremental find by pressing <b>Ctrl+J</b> (<b>Edit > Incremental Find</b>).
You can also use incremental find by pressing <strong>Ctrl+J</strong> (<strong>Edit > Incremental Find</strong>).
In this case, the text you type appears in the Status Line at the bottom of
the Eclipse window.
</p>
<p class="note"><span class="notetitle">Note: </span>
The settings in the <b>Find/Replace</b> dialog do not affect the operation
The settings in the <strong>Find/Replace</strong> dialog do not affect the operation
of incremental find in the Status Line.</p>

32
doc/org.eclipse.cdt.doc.user/reference/cdt_u_fprop_discovery.htm
View file

@ -20,7 +20,7 @@ of a C/C++ project's properties window.<br>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Discovery options</b></caption>
<caption><strong>Discovery options</strong></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
@ -28,15 +28,15 @@ of a C/C++ project's properties window.<br>
</colgroup>
<tbody>
<tr>
<td><b>Configuration</b></td>
<td><strong>Configuration</strong></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><b>Manage configurations</b></td>
<td><strong>Manage configurations</strong></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><b>Exclude resource from build</b></td>
<td><strong>Exclude resource from build</strong></td>
<td>Excludes the selected folder from the build process.</td>
</tr>
<tr>
@ -44,28 +44,28 @@ of a C/C++ project's properties window.<br>
<td>Shows a list of language specific compilers. Select a language from the list.</td>
</tr>
<tr>
<td><b>Automate discovery of paths and symbols</b></td>
<td>Scans the build output to populate the path and symbol tables, such as symbol definitions, system include directories, local include directories, macros files, and include files. If this option is not selected, the <b>Discovery profile options</b> below do not appear.</td>
<td><strong>Automate discovery of paths and symbols</strong></td>
<td>Scans the build output to populate the path and symbol tables, such as symbol definitions, system include directories, local include directories, macros files, and include files. If this option is not selected, the <strong>Discovery profile options</strong> below do not appear.</td>
</tr>
<tr>
<td><b>Report path detection problems</b></td>
<td><strong>Report path detection problems</strong></td>
<td>Sets the notification of diagnostic errors for include paths that the Eclipse CDT is unable to resolve as it parses the build output.</td>
</tr>
<tr>
<td><b>Discovery profile options</b></td>
<td>Indicates the discovery profile to use for paths and symbol detection. The type of <b>Configuration</b> and <b>Discovery Profile Scope</b> you specify determine what which <b>Discovery Profile</b> options display on this tab. This set of controls is profile-specific. It may vary from one profile to another.</td>
<td><strong>Discovery profile options</strong></td>
<td>Indicates the discovery profile to use for paths and symbol detection. The type of <strong>Configuration</strong> and <strong>Discovery Profile Scope</strong> you specify determine what which <strong>Discovery Profile</strong> options display on this tab. This set of controls is profile-specific. It may vary from one profile to another.</td>
</tr>
<tr>
<td><b>Enable generate scanner info command</b></td>
<td><strong>Enable generate scanner info command</strong></td>
<td>Enables the retrieval of information from the scanner. If it is not selected, the includes will be populated with default gcc system includes; Eclipse gathers the compiler settings based on the specified toolchain. This means that the Eclipse CDT can obtain the default gcc system includes to associate with the project.
<p>When selected, you can specify any required compiler specific commands in the <b>Compiler invocation command</b> field.</p>
<p>When selected, you can specify any required compiler specific commands in the <strong>Compiler invocation command</strong> field.</p>
</td>
</tr>
<tr>
<td><b>Compiler invocation command</b></td>
<td>Indicates the compiler specific command used to invoke the compiler (such as <tt>gcc</tt>, or more complicated commands used to perform all necessary steps for compiling C/C++ source files into .o files, and linking the object files and libraries into an executable program. For example, the command <b>gcc -E -P -v hello.c | hello.cpp</b> reads a compiler's configuration file and prints out information that includes the compiler's internally defined preprocessor symbols and include search paths. The information is complementary to the scanner configuration discovered when the output is parsed (if you've enabled the <b>Enable build output scanner info discovery</b> option), and is added to the project's scanner configuration. You can click <b>Browse</b> to locate this command, if required.
<td><strong>Compiler invocation command</strong></td>
<td>Indicates the compiler specific command used to invoke the compiler (such as <span class="typewriter">gcc</span>, or more complicated commands used to perform all necessary steps for compiling C/C++ source files into .o files, and linking the object files and libraries into an executable program. For example, the command <strong>gcc -E -P -v hello.c | hello.cpp</strong> reads a compiler's configuration file and prints out information that includes the compiler's internally defined preprocessor symbols and include search paths. The information is complementary to the scanner configuration discovered when the output is parsed (if you've enabled the <strong>Enable build output scanner info discovery</strong> option), and is added to the project's scanner configuration. You can click <strong>Browse</strong> to locate this command, if required.
<p><b>Note:</b> The parsing of build output for scanner information is compiler specific. For example, the GNU toolchain compilers (gcc and g++) use -I for include paths, and -D for symbol definitions. Consult your compiler specific documentation for more information about scanner information commands, such as the following gcc commands:</p>
<p><strong>Note:</strong> The parsing of build output for scanner information is compiler specific. For example, the GNU toolchain compilers (gcc and g++) use -I for include paths, and -D for symbol definitions. Consult your compiler specific documentation for more information about scanner information commands, such as the following gcc commands:</p>
<ul>
<li><samp>-D <span style="font-style: italic;">name</span></samp></li>
<li><samp>-I</samp></li>
@ -84,8 +84,8 @@ of a C/C++ project's properties window.<br>
</td>
</tr>
<tr>
<td><b>Browse</b></td>
<td>Click to browse for a file to include in the compiler invocation command. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
<td><strong>Browse</strong></td>
<td>Click to browse for a file to include in the compiler invocation command. This button is only visible when <strong>Configuration</strong> is set to Release and the <strong>Discovery Profiles Scope</strong> is set to <strong>Configuration-wide</strong>.</td>
</tr>
</tbody>
</table>

8
doc/org.eclipse.cdt.doc.user/reference/cdt_u_fprop_toolsettings.htm
View file

@ -18,7 +18,7 @@ Customizes the tools and tool options used in your build configuration.
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Tool settings options</b></caption>
<caption><strong>Tool settings options</strong></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
@ -26,11 +26,11 @@ Customizes the tools and tool options used in your build configuration.
</colgroup>
<tbody>
<tr>
<td><b>Configuration</b></td>
<td><strong>Configuration</strong></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><b>Manage configurations</b></td>
<td><strong>Manage configurations</strong></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
@ -43,7 +43,7 @@ Customizes the tools and tool options used in your build configuration.
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT projects, folders and source files</p>
<p><strong>Available for:</strong> CDT projects, folders and source files</p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"

2
doc/org.eclipse.cdt.doc.user/reference/cdt_u_gdb_mi.htm
View file

@ -11,7 +11,7 @@
<h1>Debug GDB MI page, Preferences window</h1>
<p>You can manipulate certain GDB timeout settings <b>Window &gt; Preferences &gt; C/C++ &gt; Debug &gt; GDB MI</b>.</p>
<p>You can manipulate certain GDB timeout settings <strong>Window &gt; Preferences &gt; C/C++ &gt; Debug &gt; GDB MI</strong>.</p>
<img src="../images/debug_gdb_pref.png" alt="Debug GDB MI Preferences">
<dl>

4
doc/org.eclipse.cdt.doc.user/reference/cdt_u_icons.htm
View file

@ -18,8 +18,8 @@ END INFOPOP-->
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="34%">
<tr>
<td width="19%" align="left"><b>Icon</b></td>
<td width="81%"><b>Description</b></td>
<td width="19%" align="left"><strong>Icon</strong></td>
<td width="81%"><strong>Description</strong></td>
</tr>
<tr>
<td width="19%" align="left">

30
doc/org.eclipse.cdt.doc.user/reference/cdt_u_indexer_preference.html
View file

@ -8,13 +8,13 @@
</head>
<body>
<h1>Indexer Preference page</h1>
<p>Use the <b>Indexer</b> preference page to select the indexer used by default for new projects and configure its behavior.</p>
<p>Use the <strong>Indexer</strong> preference page to select the indexer used by default for new projects and configure its behavior.</p>
<p> <img src="../images/indexer_preference_page.PNG"
alt="Indexer Preferences Window" ><br>
</p>
<table width="600" cellpadding="5" cellspacing="0" border="1" >
<caption>
<b>Indexer Options</b>
<strong>Indexer Options</strong>
</caption>
<colgroup>
<col width="30%" valign="top" >
@ -22,55 +22,55 @@
</colgroup>
<tbody>
<tr>
<td width="241" valign="top"><b>Select Indexer </b></td>
<td width="241" valign="top"><strong>Select Indexer </strong></td>
<td width="333" valign="top">Select the indexer to use by default for all new projects. </td>
</tr>
<tr>
<td valign="top"><b>Index all files (files neither built nor included, also) </b></td>
<td valign="top"><strong>Index all files (files neither built nor included, also) </strong></td>
<td valign="top">Activate this checkbox to index all files </td>
</tr>
<tr>
<td valign="top"><b>Skip all references (Call Hierarchy and Search will not work) </b></td>
<td valign="top"><strong>Skip all references (Call Hierarchy and Search will not work) </strong></td>
<td valign="top">Activate this checkbox to not index references to save space and gain performance. This prevents some portions of CDT from working, like Call Hierarchy and search for references. </td>
</tr>
<tr>
<td valign="top"><b>Skip type references (Search for type references will not work) </b></td>
<td valign="top"><strong>Skip type references (Search for type references will not work) </strong></td>
<td valign="top">Activate this checkbox to not index type references. This prevents some portions of CDT from working, like Search for type references. </td>
</tr>
<tr>
<td valign="top"><b>Skip macro references (Search for macro references will not work) </b></td>
<td valign="top"><strong>Skip macro references (Search for macro references will not work) </strong></td>
<td valign="top">Activate this checkbox to not index macro references. This prevents some portions of CDT from working, like Search for macro references. </td>
</tr>
<tr>
<td valign="top"><b>Files to index up-front </b></td>
<td valign="top"><strong>Files to index up-front </strong></td>
<td valign="top">Type a comma separated list of files that should always be indexed immediately. </td>
</tr>
<tr>
<td valign="top"><b>Automatically update the index </b></td>
<td valign="top"><strong>Automatically update the index </strong></td>
<td valign="top">Activate this checkbox to have the index automatically update as it requires. </td>
</tr>
<tr>
<td valign="top"><b>Update index immediately after every file change </b></td>
<td valign="top"><strong>Update index immediately after every file change </strong></td>
<td valign="top">Activate this checkbox to force an index update whenever a file is saved. </td>
</tr>
<tr>
<td valign="top"><b>Use active build configuration </b></td>
<td valign="top"><strong>Use active build configuration </strong></td>
<td valign="top">Activate this checkbox to always use the active build configuration indexer settings to build the index. </td>
</tr>
<tr>
<td valign="top"><b>Use the build configuration specified in the project's indexer settings </b></td>
<td valign="top"><strong>Use the build configuration specified in the project's indexer settings </strong></td>
<td valign="top">Activate this checkbox to always use the project's indexer settings to build the index. </td>
</tr>
<tr>
<td valign="top"><b>Limit relative to the maximum heap size </b></td>
<td valign="top"><strong>Limit relative to the maximum heap size </strong></td>
<td valign="top">Specify the relative size limit the index can reach based on the maximum heap size. </td>
</tr>
<tr>
<td valign="top"><b>Index database cache: Absolute limit </b></td>
<td valign="top"><strong>Index database cache: Absolute limit </strong></td>
<td valign="top">Specify the maximum size the index database cache is limited to. </td>
</tr>
<tr>
<td valign="top"><b>Header file cache: Absolute limit </b></td>
<td valign="top"><strong>Header file cache: Absolute limit </strong></td>
<td valign="top">Specify the maximum size the header file cache is limited to. </td>
</tr>
</tbody>

14
doc/org.eclipse.cdt.doc.user/reference/cdt_u_language_mapping_pref.htm
View file

@ -12,12 +12,12 @@
<h1>Language Mappings preferences</h1>
<p>Customize the use of C/C++ language associations in the <b>Language Mappings</b> preference panel for the workspace. </p>
<p>Customize the use of C/C++ language associations in the <strong>Language Mappings</strong> preference panel for the workspace. </p>
<p><img src="../images/view_language_mappings_prefs.png" width="627" height="544" alt="Language Mappings preferences"></p>
<table width="600" cellpadding="5" cellspacing="0" border="1" >
<caption>
<b>Language Mappings Options</b>
<strong>Language Mappings Options</strong>
</caption>
<colgroup>
<col width="30%" valign="top" >
@ -25,20 +25,20 @@
</colgroup>
<tbody>
<tr>
<td width="171" valign="top"><b>Content Type </b></td>
<td width="171" valign="top"><strong>Content Type </strong></td>
<td width="503" valign="top">The content type associated with the language. </td>
</tr>
<tr>
<td valign="top"><b>Language</b></td>
<td valign="top"><strong>Language</strong></td>
<td valign="top">The language associated with the content type. </td>
</tr>
<tr>
<td valign="top"><b>Add</b></td>
<td valign="top"><p>Click to show the <b>Add Mapping</b> dialog where you define the content type and language associated with it. </p>
<td valign="top"><strong>Add</strong></td>
<td valign="top"><p>Click to show the <strong>Add Mapping</strong> dialog where you define the content type and language associated with it. </p>
<p align="center"><img src="../images/view_add_mapping.png" width="216" height="134" alt="Add Mapping dialog"></p></td>
</tr>
<tr>
<td valign="top"><b>Remove</b></td>
<td valign="top"><strong>Remove</strong></td>
<td valign="top">Click to remove the selected langauge mapping. </td>
</tr>
</tbody>

62
doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_edit.htm
View file

@ -19,166 +19,166 @@
<th>Keyboard Shortcut</th>
</tr>
<tr align="left" valign="top">
<td align="left" valign="top"><b>Undo</b></td>
<td align="left" valign="top"><strong>Undo</strong></td>
<td align="left" valign="top">Revert the last change in the editor</td>
<td> Ctrl+Z</td>
</tr>
<tr>
<td align="left" valign="top"><b>Redo </b></td>
<td align="left" valign="top"><strong>Redo </strong></td>
<td align="left" valign="top">Revert an undone change</td>
<td> Ctrl+Y</td>
</tr>
<tr>
<td align="left" valign="top"><b>Cut</b></td>
<td align="left" valign="top"><strong>Cut</strong></td>
<td align="left" valign="top">Copies the currently selected text or element to the clipboard and removes the element. On elements, the remove is not performed before the clipboard is pasted.</td>
<td> Ctrl+X</td>
</tr>
<tr>
<td align="left" valign="top"><b>Copy</b></td>
<td align="left" valign="top"><strong>Copy</strong></td>
<td align="left" valign="top">Copies the currently selected text or elements to the clipboard</td>
<td> Ctrl+C</td>
</tr>
<tr>
<td align="left" valign="top"><b>Paste </b></td>
<td align="left" valign="top"><strong>Paste </strong></td>
<td align="left" valign="top">Paste the current content as text to the editor, or as a sibling or child element to the a currently selected element.&nbsp;</td>
<td> Ctrl+V</td>
</tr>
<tr>
<td><b>Delete </b></td>
<td><strong>Delete </strong></td>
<td>Delete the current text or element selection.</td>
<td> Delete</td>
</tr>
<tr align="left" valign="top">
<td><b>Select All</b></td>
<td><strong>Select All</strong></td>
<td>Select all the editor content..</td>
<td> Ctrl+A</td>
</tr>
<tr align="left" valign="top">
<td><b>Find / Replace</b></td>
<td><strong>Find / Replace</strong></td>
<td>Open the Find / Replace dialog. Editor only.</td>
<td> Ctrl+F</td>
</tr>
<tr align="left" valign="top">
<td><b>Find Next</b></td>
<td><strong>Find Next</strong></td>
<td>Finds the next occurrence of the currently selected text. Editor only.</td>
<td> Ctrl+K</td>
</tr>
<tr>
<td><b>Find Previous</b></td>
<td><strong>Find Previous</strong></td>
<td>Finds the previous occurrence of the currently selected text. Editor only.</td>
<td> Ctrl+Shift+K</td>
</tr>
<tr>
<td><b>Incremental Find Next</b></td>
<td><strong>Incremental Find Next</strong></td>
<td>Starts the incremental find mode. After invocation, enter the search text as instructed in the status bar. Editor only.</td>
<td> Ctrl+J</td>
</tr>
<tr>
<td><b>Incremental Find Previous</b></td>
<td><strong>Incremental Find Previous</strong></td>
<td>Starts the incremental find mode. After invocation, enter the search text as instructed in the status bar. Editor only.</td>
<td> Ctrl+Shift+J</td>
</tr>
<tr align="left" valign="top">
<td><b>Add Bookmark...</b></td>
<td><strong>Add Bookmark...</strong></td>
<td>Add a bookmark to the current text selection or selected element.</td>
<td> &nbsp;</td>
</tr>
<tr align="left" valign="top">
<td><b>Add Task...</b></td>
<td><strong>Add Task...</strong></td>
<td>Add a user defined task to the current text selection or selected element.</td>
<td> Alt+<b></b>Enter</td>
<td> Alt+<strong></strong>Enter</td>
</tr>
<tr align="left" valign="top">
<td><b>Add to working set</b></td>
<td><strong>Add to working set</strong></td>
<td>Add current resource to selected Working Set</td>
<td> Ctrl+I</td>
</tr>
<tr>
<td><b>Remove from working set</b></td>
<td><strong>Remove from working set</strong></td>
<td>Remove current resource from Working Set</td>
<td> Ctrl+Shift+I</td>
</tr>
<tr>
<td><b>Smart Insert Mode</b></td>
<td><strong>Smart Insert Mode</strong></td>
<td>Toggles editor's Smart Insert Mode</td>
<td> Ctrl+Shift+Insert</td>
</tr>
<tr>
<td><b>Show Tooltip Description</b></td>
<td><strong>Show Tooltip Description</strong></td>
<td>Displays tooltip description, where applicable.</td>
<td>F2</td>
</tr>
<tr>
<td><b>Word Completion</b></td>
<td><strong>Word Completion</strong></td>
<td>Completes current word in editor.</td>
<td>Alt+/</td>
</tr>
<tr>
<td><b>Quick fix</b></td>
<td><strong>Quick fix</strong></td>
<td>Call quick fix dialog for selected warning/error.</td>
<td> Ctrl+1</td>
</tr>
<tr>
<td><b>Content Assist</b></td>
<td><strong>Content Assist</strong></td>
<td>Opens a context assist dialog at the current cursor position to bring up Java code assist proposals and templates. See the Templates preference page for available templates
<b>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Templates</b> and go to the Editor preference page
<b>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Content Assist</b> for configuring the behaviour of content assist.</td>
<strong>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Templates</strong> and go to the Editor preference page
<strong>Window &gt; Preferences &gt; C/C++ &gt; Editor &gt; Content Assist</strong> for configuring the behaviour of content assist.</td>
<td> Ctrl+Space</td>
</tr>
<tr>
<td><b>Parameter Hints</b></td>
<td><strong>Parameter Hints</strong></td>
<td>Opens Parameter Hints dialog. Editor only</td>
<td>Ctrl+Shift+Space</td>
</tr>
<tr align="left" valign="top">
<td><b>Shift Right</b></td>
<td><strong>Shift Right</strong></td>
<td>Shifts text Right. Editor only</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Shift Left</b></td>
<td><strong>Shift Left</strong></td>
<td>Shifts text Right. Editor only</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Format</b></td>
<td><strong>Format</strong></td>
<td>Formats text. Editor only</td>
<td>Ctrl+Shift+F</td>
</tr>
<tr>
<td><b>Add Include</b></td>
<td><strong>Add Include</strong></td>
<td>Add include to current file. Editor only </td>
<td>Ctrl+Shift+N</td>
</tr>
<tr>
<td><b>Set Encoding... </b></td>
<td><strong>Set Encoding... </strong></td>
<td>Toggles the encoding of the currently shown text content.</td>
<td>&nbsp;</td>
</tr>
@ -187,7 +187,7 @@
</p>
<p><b>Note: </b> Other <b>Edit</b> options are used with the JDT. Refer to the <i>Java Development User Guide</i> for details. </p>
<p><strong>Note: </strong> Other <strong>Edit</strong> options are used with the JDT. Refer to the <em>Java Development User Guide</em> for details. </p>
<p>
<IMG alt="IBM Copyright Statement" src="../images/ng00_04a.gif" border=0>

40
doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_file.htm
View file

@ -19,115 +19,115 @@
<tr><th>Name</th><th>Function</th><th>Keyboard Shortcut</th></tr>
<tr valign="top">
<td valign="top"><b>New</b></td>
<td valign="top"><strong>New</strong></td>
<td valign="top">Create a new project, folder, or file.</td>
<td valign="top">Alt+Shift+N</td>
</tr>
<tr valign="top">
<td valign="top"><b>Open File...</b></td>
<td valign="top"><strong>Open File...</strong></td>
<td valign="top">Open existing file.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Close</b></td>
<td valign="top"><strong>Close</strong></td>
<td valign="top">Close the current editor.
If the editor contains unsaved data, a save request dialog is shown.</td>
<td valign="top">Ctrl+F4</td>
</tr>
<tr>
<td valign="top"><b>Close All</b></td>
<td valign="top"><strong>Close All</strong></td>
<td valign="top">Close all editors.
If editors contains unsaved data, a save request dialog will be shown.</td>
<td valign="top">Ctrl+Shift+F4</td>
</tr>
<tr>
<td valign="top"><b>Save</b></td>
<td valign="top"><strong>Save</strong></td>
<td valign="top">Save the content of the current editor.
Disabled if the editor does not contain unsaved changes.</td>
<td valign="top">Ctrl+S</td>
</tr>
<tr>
<td valign="top"><b>Save As</b></td>
<td valign="top"><strong>Save As</strong></td>
<td valign="top">Save the content of the current editor under a new name.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Save All</b></td>
<td valign="top"><strong>Save All</strong></td>
<td valign="top">Save the content of the current editor.
Disabled if no editor contains unsaved changes.</td>
<td valign="top">Ctrl+Shift+S</td>
</tr>
<tr valign="top">
<td valign="top"><b>Revert</b></td>
<td valign="top"><strong>Revert</strong></td>
<td valign="top">Revert the content of the current editor back to the content of the saved file.
Disabled if the editor does not contain unsaved changes.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr valign="top">
<td valign="top"><b>Move</b></td>
<td valign="top"><strong>Move</strong></td>
<td valign="top">Move a resource.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr valign="top">
<td valign="top"><b>Rename</b></td>
<td valign="top"><strong>Rename</strong></td>
<td valign="top">Renames a resource.</td>
<td valign="top">F2</td>
</tr>
<tr>
<td valign="top"><b>Refresh</b></td>
<td valign="top"><strong>Refresh</strong></td>
<td valign="top">Refreshes the content of the selected element with the local file system.
When launched from no specific selection, this command refreshes all projects.</td>
<td valign="top">F5</td>
</tr>
<tr valign="top">
<td valign="top"><b>Convert Line Delimiters to (submenu)</b></td>
<td valign="top"><strong>Convert Line Delimiters to (submenu)</strong></td>
<td valign="top">Changes line delimiters either to Windows, or UNIX, or Mac OS9 format.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Print</b></td>
<td valign="top"><strong>Print</strong></td>
<td valign="top">Prints the content of the current editor. Enabled when an editor has the focus.</td>
<td valign="top">Ctrl+P</td>
</tr>
<tr valign="top">
<td valign="top"><b>Switch workspace...</b></td>
<td valign="top"><strong>Switch workspace...</strong></td>
<td valign="top">Relaunches Eclipse with a new workspace.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Import</b></td>
<td valign="top">Opens the <b>Import</b> dialog and shows all import wizards.</td>
<td valign="top"><strong>Import</strong></td>
<td valign="top">Opens the <strong>Import</strong> dialog and shows all import wizards.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr valign="top">
<td valign="top"><b>Export</b></td>
<td valign="top">Opens the <b>Export</b> dialog and shows all export wizards.</td>
<td valign="top"><strong>Export</strong></td>
<td valign="top">Opens the <strong>Export</strong> dialog and shows all export wizards.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr valign="top">
<td valign="top"><b>Properties</b></td>
<td valign="top"><strong>Properties</strong></td>
<td valign="top">Opens the property pages of the select elements.</td>
<td valign="top">Alt+Enter</td>
</tr>
<tr valign="top">
<td valign="top"><b>Exit</b></td>
<td valign="top"><strong>Exit</strong></td>
<td valign="top">Exit Eclipse</td>
<td valign="top">&nbsp;</td>
</tr>

50
doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_navigate.htm
View file

@ -20,100 +20,100 @@
</tr>
<tr>
<td valign="top"><b>Go Into</b></td>
<td valign="top"><strong>Go Into</strong></td>
<td valign="top">Sets the view input to the currently selected element.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Go To</b></td>
<td valign="top"><strong>Go To</strong></td>
<td valign="top"><ul>
<li><b>Back</b>:&nbsp; This command displays the hierarchy that was displayed immediately prior to the current display.&nbsp;
<li><strong>Back</strong>:&nbsp; This command displays the hierarchy that was displayed immediately prior to the current display.&nbsp;
For example, if you Go Into a resource, then the Back command in the resulting display returns the view to the same hierarchy from which you activated the Go Into command.&nbsp;
This command is similar to the Back button in an HTML browser.</li>
<li><b>Forward</b>:&nbsp; This command displays the hierarchy that was displayed immediately after the current display.&nbsp;
<li><strong>Forward</strong>:&nbsp; This command displays the hierarchy that was displayed immediately after the current display.&nbsp;
For example, if you've just selected the Back command, then selecting the Forward command in the resulting display returns the view to the same hierarchy from which you activated the
Back command.&nbsp; This command is similar to the Forward button in an HTML browser.</li>
<li><b>Up one level</b>:&nbsp; This command displays the hierarchy of the parent of the current highest-level resource.</li>
<li><B>Resource</B>: This command allows you to navigate quickly to a resource. For more information see the links to related tasks below.</li>
<li><strong>Up one level</strong>:&nbsp; This command displays the hierarchy of the parent of the current highest-level resource.</li>
<li><strong>Resource</strong>: This command allows you to navigate quickly to a resource. For more information see the links to related tasks below.</li>
</ul>
</td>
<td>&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Open Type Hierarchy</b></td>
<td valign="top"><strong>Open Type Hierarchy</strong></td>
<td valign="top">Opens Type Hierarchy view for selected object</td>
<td>F4</td>
</tr>
<tr>
<td valign="top"><b>Open Call Hierarchy</b></td>
<td valign="top"><strong>Open Call Hierarchy</strong></td>
<td valign="top">Opens Call Hierarchy view for selected object</td>
<td>Ctrl+Alt+H</td>
</tr>
<tr>
<td valign="top"><b>Open Declaration</b></td>
<td valign="top"><strong>Open Declaration</strong></td>
<td valign="top">Opens Declaration for selected object (class, variable...)</td>
<td>F3</td>
</tr>
<tr>
<td valign="top"><b>Toggle Source/Header</b></td>
<td valign="top"><strong>Toggle Source/Header</strong></td>
<td valign="top">Switches between source and corresponding header files.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Open Element...</b></td>
<td valign="top"><strong>Open Element...</strong></td>
<td valign="top">Brings up the Open Element selection dialog to open an element in the editor. This dialog shows all types existing in the workspace. </td>
<td>Ctrl+Shift+T</td>
</tr>
<tr>
<td valign="top"><b>Open Resource</b></td>
<td valign="top"><strong>Open Resource</strong></td>
<td valign="top">This command displays a dialog that lets you select any resource in the workspace to open it in an editor.
</td>
<td>Ctrl+Shift+R</td>
</tr>
<tr>
<td valign="top"><b>Show In</b></td>
<td valign="top"><strong>Show In</strong></td>
<td valign="top">This sub-menu is used to find and select the currently selected resource in another view. If an editor is active, these commands are used to select the resource currently being edited in another view.</td>
<td>Ctrl+Shift+W</td>
</tr>
<tr>
<td valign="top"><b>Quick Outline</b></td>
<td valign="top"><strong>Quick Outline</strong></td>
<td valign="top">Displays outline view for current source file.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Next</b></td>
<td valign="top">The &quot;next&quot; definition is based on where the focus is. For example, during a search this entry becomes <b>Next Match</b>.</td>
<td valign="top"><strong>Next</strong></td>
<td valign="top">The &quot;next&quot; definition is based on where the focus is. For example, during a search this entry becomes <strong>Next Match</strong>.</td>
<td>Ctrl+.</td>
</tr>
<tr>
<td><b>Previous</b></td>
<td><strong>Previous</strong></td>
<td>The &quot;previous&quot; definition is based on
where the focus is.
For example, during a search this entry becomes <b>Previous Match</b>.</td>
For example, during a search this entry becomes <strong>Previous Match</strong>.</td>
<td>Ctrl+,</td>
</tr>
<tr>
<td valign="top"><b>Last Edit Location</b></td>
<td valign="top"><strong>Last Edit Location</strong></td>
<td valign="top">Moves the cursor to the line that contains the last edit.
Editor only.</td>
<td valign="top">Ctrl+Q</td>
</tr>
<tr>
<td valign="top"><b>Go to Line</b></td>
<td valign="top"><strong>Go to Line</strong></td>
<td valign="top">Open a dialog where you can specify the line number
to which to move the cursor.
Editor only.</td>
@ -121,14 +121,14 @@ Editor only.</td>
</tr>
<tr>
<td valign="top"><b>Back</b></td>
<td valign="top"><strong>Back</strong></td>
<td valign="top">Moves the focus to the previous file.
Editor only.</td>
<td valign="top">Ctrl+Q</td>
</tr>
<tr>
<td valign="top"><b>Forward</b></td>
<td valign="top"><strong>Forward</strong></td>
<td valign="top">Returns the focus from the previous file.
Editor only.</td>
<td valign="top">Ctrl+Q</td>
@ -138,9 +138,9 @@ Editor only.</td>
</table>
</p>
<p class="note"><b>Note: </b>
Other <b>Navigate</b> options are used with the JDT.
Refer to the <i>Java Development User Guide</i> for details.
<p class="note"><strong>Note: </strong>
Other <strong>Navigate</strong> options are used with the JDT.
Refer to the <em>Java Development User Guide</em> for details.
</p>
<p>

32
doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_project.htm
View file

@ -18,27 +18,27 @@
<tr><th>Name</th><th>Function</th><th>Keyboard Shortcut</th></tr>
<tr>
<td><b>Open Project</b></td>
<td><strong>Open Project</strong></td>
<td>Shows a dialog that can be used to select a closed project and open it.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Close Project</b></td>
<td><strong>Close Project</strong></td>
<td>Closes the currently selected projects.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Build All</b></td>
<td><strong>Build All</strong></td>
<td>Builds all projects in the workspace. This is a full build; all files are built.</td>
<td>Ctrl+B</td>
</tr>
<tr>
<td><b>Build parallel</b></td>
<td><strong>Build parallel</strong></td>
<td>Builds all (or selected) configurations of given project(s). Each configuration is built as separate parallel task.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Build Configurations</b></td>
<td><strong>Build Configurations</strong></td>
<td>Submenu which allows to:
<ul>
<li>Delete resource configurastion for file/folder
@ -49,36 +49,36 @@
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Build Project</b></td>
<td><strong>Build Project</strong></td>
<td>Builds the currently selected project. This is a full build; all files in the project are built. </td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Build Working Set</b></td>
<td><strong>Build Working Set</strong></td>
<td>Builds the current working set.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Clean</b></td>
<td><strong>Clean</strong></td>
<td>Invokes the make clean defined in the makefile</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Build Automatically</b></td>
<td><strong>Build Automatically</strong></td>
<td>When checked, the CDT will perform a build whenever a file in a project is saved. You should turn this feature off for very large projects.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Make Target</b></td>
<td>Submenu wich allows create or build a target in the <b>Make Targets</b> view.</td>
<td><strong>Make Target</strong></td>
<td>Submenu wich allows create or build a target in the <strong>Make Targets</strong> view.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Properties</b></td>
<td>Displays the <b>Properties</b> dialog. From that dialog you can display the properties of resources in <b>Info</b>,
<b>External Tools Builders</b>, <b>C/C++ Build</b> (managed only) <b>File Types</b>, <b>Indexer options</b>,
<b>C/C++ Make Project</b> (standard only), <b>C/C++ Project Paths</b> (standard only),
<b>Include Paths and Symbols</b> (standard only), and <b>Project References</b>. </td>
<td><strong>Properties</strong></td>
<td>Displays the <strong>Properties</strong> dialog. From that dialog you can display the properties of resources in <strong>Info</strong>,
<strong>External Tools Builders</strong>, <strong>C/C++ Build</strong> (managed only) <strong>File Types</strong>, <strong>Indexer options</strong>,
<strong>C/C++ Make Project</strong> (standard only), <strong>C/C++ Project Paths</strong> (standard only),
<strong>Include Paths and Symbols</strong> (standard only), and <strong>Project References</strong>. </td>
<td>&nbsp;</td>
</tr>
</table></p>

2
doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_refactor.htm
View file

@ -18,7 +18,7 @@
<tr><th>Name</th><th>Function</th><th>Keyboard Shortcut</th></tr>
<tr>
<td><b>Rename...</b></td>
<td><strong>Rename...</strong></td>
<td>Renames selected object (variable, method, etc...) and propagates changes to other files in project.</td>
<td>Alt+Shit+R</td>
</table></p>

18
doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_run.htm
View file

@ -18,55 +18,55 @@
<tr><th>Name</th><th>Function</th><th>Keyboard Shortcut</th></tr>
<tr valign="top">
<td valign="top"><b>Run</b></td>
<td valign="top"><strong>Run</strong></td>
<td valign="top"> This command allows you to quickly repeat the most recent launch in run mode.</td>
<td valign="top">Ctrl+F11</td>
</tr>
<tr valign="top">
<td valign="top"><b>Debug</b></td>
<td valign="top"><strong>Debug</strong></td>
<td valign="top"> This command allows you to quickly repeat the most recent launch in debug mode.</td>
<td valign="top">F11</td>
</tr>
<tr>
<td valign="top"><b>Run History</b></td>
<td valign="top"><strong>Run History</strong></td>
<td valign="top"> Presents a sub menu of the recent history of launch configurations launched in run mode.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Run As</b></td>
<td valign="top"><strong>Run As</strong></td>
<td valign="top">Presents a sub menu of registered run launch shortcuts. Launch shortcuts provide support for workbench or active editor selection sensitive launching.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Open Run Dialog...</b></td>
<td valign="top"><strong>Open Run Dialog...</strong></td>
<td valign="top">This command realizes the launch configuration dialog to manage run mode launch configurations. </td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Debug History</b></td>
<td valign="top"><strong>Debug History</strong></td>
<td valign="top">Presents a sub menu of the recent history of launch configurations launched in debug mode.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Debug As</b></td>
<td valign="top"><strong>Debug As</strong></td>
<td valign="top">Presents a sub menu of registered debug launch shortcuts. Launch shortcuts provide support for workbench or active editor selection sensitive launching.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr>
<td valign="top"><b>Open Debug Dialog...</b></td>
<td valign="top"><strong>Open Debug Dialog...</strong></td>
<td valign="top">This command realizes the launch configuration dialog to manage debug mode launch configurations.</td>
<td valign="top">&nbsp;</td>
</tr>
<tr valign="top">
<td valign="top"><b>External Tools</b></td>
<td valign="top"><strong>External Tools</strong></td>
<td valign="top">Presents a sub menu of links to external run configuration dialogs to manage run mode launch configurations.</td>
<td valign="top">&nbsp;</td>
</tr>

10
doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_search.htm
View file

@ -9,7 +9,7 @@
</head>
<body>
<h1>Search Menu actions</h1>
<p><b>Search</b> menu commands open the search dialog. There are specialized tabs on the general <b>Search</b> dialog to help you search for:</p>
<p><strong>Search</strong> menu commands open the search dialog. There are specialized tabs on the general <strong>Search</strong> dialog to help you search for:</p>
<ul>
<li>Files, or for text in files</li>
<li>Elements in C/C++ files</li>
@ -26,22 +26,22 @@
<th>Keyboard Shortcut </th>
</tr>
<tr>
<td><b>C/C++...</b></td>
<td><strong>C/C++...</strong></td>
<td>Opens the search dialog on the C/C++ search page</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Search...</b></td>
<td><strong>Search...</strong></td>
<td>Opens the search dialog for your current editor</td>
<td>Ctrl + H </td>
</tr>
<tr>
<td><b>File...</b></td>
<td><strong>File...</strong></td>
<td>Opens the search dialog on the File search page</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Text</b></td>
<td><strong>Text</strong></td>
<td>Opens the submenu for full-text search in given scope (workspace, project, file or working set)</td>
<td>&nbsp;</td>
</tr>

58
doc/org.eclipse.cdt.doc.user/reference/cdt_u_m_window.htm
View file

@ -16,97 +16,97 @@
<tr><th>Name</th><th>Function</th><th>Keyboard Shortcut</th></tr>
<tr>
<td><b>New Window</b></td>
<td><strong>New Window</strong></td>
<td>Opens new Window </td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>New Editor</b></td>
<td><strong>New Editor</strong></td>
<td>This command opens a new empty editor in this Workbench window. </td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Open Perspective</b></td>
<td><strong>Open Perspective</strong></td>
<td>This command opens a new perspective in this Workbench window.
This preference can be changed in the <b>Window &gt; Preferences &gt; Workbench &gt; Perspectives</b> page.
This preference can be changed in the <strong>Window &gt; Preferences &gt; Workbench &gt; Perspectives</strong> page.
All of the perspectives that are open within the Workbench window are shown on the shortcut bar.
The perspectives you will likely want to open are listed first.This list is dependent on the current perspective.
From the <b>Other...</b> submenu you can open any perspective.</td>
From the <strong>Other...</strong> submenu you can open any perspective.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Show View</b></td>
<td><strong>Show View</strong></td>
<td>This command displays the selected view in the current perspective.
You can configure how views are opened in the <b>Window &gt; Preferences &gt; Workbench &gt; Perspectives page</b>.
You can configure how views are opened in the <strong>Window &gt; Preferences &gt; Workbench &gt; Perspectives page</strong>.
Views you are likely to want to open are listed first.This list is dependent on the current perspective.
From the <b>Other...</b> submenu you can open any view.
From the <strong>Other...</strong> submenu you can open any view.
The views are sorted into categories in the Show View dialog.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Customize Perspective</b></td>
<td><strong>Customize Perspective</strong></td>
<td>Each perspective includes a predefined set of actions that are accessible from the menu bar and Workbench toolbar.
Related actions are grouped into action sets.
This command allows you to customize the current perspective by showing or hiding various action sets.
The first three (<b>File &gt; New</b>, <b>Window &gt; Open Perspective</b>, <b>Window &gt; Show View</b>) control which actions appear as top level items in their respective menus.
The last category (<b>Other</b>) controls which action sets are visible in the perspective.</td>
The first three (<strong>File &gt; New</strong>, <strong>Window &gt; Open Perspective</strong>, <strong>Window &gt; Show View</strong>) control which actions appear as top level items in their respective menus.
The last category (<strong>Other</strong>) controls which action sets are visible in the perspective.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Save Perspective As</b></td>
<td><strong>Save Perspective As</strong></td>
<td>This command allows you to save the current perspective, creating your own custom perspective.
You can open more perspectives of this type using the <b>Window &gt; Open Perspective &gt; Other</b> menu item once you have saved a perspective.</td>
You can open more perspectives of this type using the <strong>Window &gt; Open Perspective &gt; Other</strong> menu item once you have saved a perspective.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Reset Perspective</b></td>
<td><strong>Reset Perspective</strong></td>
<td>This command changes the layout of the current perspective to its original configuration.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Close Perspective</b></td>
<td><strong>Close Perspective</strong></td>
<td>This command closes the active perspective.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Close All Perspectives</b></td>
<td><strong>Close All Perspectives</strong></td>
<td>This command closes all open perspectives in the Workbench window.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Navigation</b></td>
<td><strong>Navigation</strong></td>
<td>This submenu contains shortcut keys for navigating between the views, perspectives, and editors in the Workbench window.
<ul>
<li><b>Show System Menu</b>: Shows the menu that is used for resizing, closing or pinning the current view or editor.</li>
<li><b>Show View Menu</b>: Shows the drop down menu that is available in the toolbar of the active view.</li>
<li><b>Maximize Active View or Editor</b>: Maximizes the current view or editor to fill the workbench.</li>
<li><b>Activate Editor</b>: Makes the current editor active.</li>
<li><b>Next Editor</b>: Activates the next open editor in the list of most recently used editors.</li>
<li><b>Previous Editor</b>: Activates the previous open editor in the list of most recently used editors.</li>
<li><b>Next View</b>: Activates the next open view in the list of most recently used views.</li>
<li><b>Previous View</b>: Activates the previous open view in the list of most recently used views.</li>
<li><b>Next Perspective</b>: Activates the next open perspective in the list of most recently used perspectives.</li>
<li><b>Previous Perspective</b>: Activates the previous open perspective in the list of most recently used perspectives.</li>
<li><strong>Show System Menu</strong>: Shows the menu that is used for resizing, closing or pinning the current view or editor.</li>
<li><strong>Show View Menu</strong>: Shows the drop down menu that is available in the toolbar of the active view.</li>
<li><strong>Maximize Active View or Editor</strong>: Maximizes the current view or editor to fill the workbench.</li>
<li><strong>Activate Editor</strong>: Makes the current editor active.</li>
<li><strong>Next Editor</strong>: Activates the next open editor in the list of most recently used editors.</li>
<li><strong>Previous Editor</strong>: Activates the previous open editor in the list of most recently used editors.</li>
<li><strong>Next View</strong>: Activates the next open view in the list of most recently used views.</li>
<li><strong>Previous View</strong>: Activates the previous open view in the list of most recently used views.</li>
<li><strong>Next Perspective</strong>: Activates the next open perspective in the list of most recently used perspectives.</li>
<li><strong>Previous Perspective</strong>: Activates the previous open perspective in the list of most recently used perspectives.</li>
</ul>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Working sets</b></td>
<td><strong>Working sets</strong></td>
<td>Dialog displayed to edit working sets</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><b>Preferences</b></td>
<td><strong>Preferences</strong></td>
<td>This command allows you to indicate your preferences for using the Workbench.
There are a wide variety of preferences for configuring the appearance of the Workbench and its views, and for customizing the behavior of all tools that are installed in the Workbench.
See the <a href="cdt_u_c_pref.htm">C/C++ Page Preference Window</a> section for more details on the CDT preferences.</td>

18
doc/org.eclipse.cdt.doc.user/reference/cdt_u_make_settings_pref.htm
View file

@ -12,38 +12,38 @@
<h1>Settings preferences</h1>
<p>Use the <b>Settings</b> preference panel in the Preferences window to specify the Makefile style and include directories.</p>
<p>Use the <strong>Settings</strong> preference panel in the Preferences window to specify the Makefile style and include directories.</p>
<p><img src="../images/make_settings_prefs.png" alt="Settings Preferences Window"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Settings Preference Options</b></caption>
<caption><strong>Settings Preference Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Posix Make</b></td>
<td><strong>Posix Make</strong></td>
<td>Enable to generate makefiles that are POSIX Make compatible.</td>
</tr>
<tr>
<td><b>GNU Make</b></td>
<td><strong>GNU Make</strong></td>
<td>Enable to generate makefiles that are GNU Make compatible.</td>
</tr>
<tr>
<td><b>New...</b></td>
<td>Opens the <b>Browse for Folder</b> dialog to select a directory.</td>
<td><strong>New...</strong></td>
<td>Opens the <strong>Browse for Folder</strong> dialog to select a directory.</td>
</tr>
<tr>
<td><b>Remove</b></td>
<td><strong>Remove</strong></td>
<td>Click to remove the currently selected directory from the Makefile include directories list.</td>
</tr>
<tr>
<td><b>Up</b></td>
<td><strong>Up</strong></td>
<td>Click to move the currently selected directory up in the list.</td>
</tr>
<tr>
<td><b>Down</b></td>
<td><strong>Down</strong></td>
<td>Click to move the currently selected directory down in the list.</td>
</tr>
</tbody>

18
doc/org.eclipse.cdt.doc.user/reference/cdt_u_makefile_settings_pref.htm
View file

@ -12,40 +12,40 @@
<h1>Makefile Editor preferences</h1>
<p>Use the <b>Makefile Editor</b> preference panel in the Preferences window to set syntax and folding options for the Makefile editor.</p>
<p>Use the <strong>Makefile Editor</strong> preference panel in the Preferences window to set syntax and folding options for the Makefile editor.</p>
<p><img src="../images/makefile_editor_prefs.png" alt="Makefile Editor Syntax tab"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Makefile Editor Syntax Options</b></caption>
<caption><strong>Makefile Editor Syntax Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Color</b></td>
<td><strong>Color</strong></td>
<td>Click to set the selected syntax item to a specific color.</td>
</tr>
<tr>
<td><b>Bold</b></td>
<td>If enabled, set the selected syntax item to <b>bold</b>.</td>
<td><strong>Bold</strong></td>
<td>If enabled, set the selected syntax item to <strong>bold</strong>.</td>
</tr>
<tr>
<td><b>Italic</b></td>
<td>If enabled, set the selected syntax item to <i>italic</i>.</td>
<td><strong>Italic</strong></td>
<td>If enabled, set the selected syntax item to <em>italic</em>.</td>
</tr>
</tbody>
</table>
<p><img src="../images/makefile_editor_folding_prefs.png" alt="Makefile Editor Folding tab"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption><b>Makefile Editor Folding Tab Options</b></caption>
<caption><strong>Makefile Editor Folding Tab Options</strong></caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><b>Enable folding when opening a new editor</b></td>
<td><strong>Enable folding when opening a new editor</strong></td>
<td>If enabled, activate folding when a new Makefile editor is opened.</td>
</tr>
</tbody>

38
doc/org.eclipse.cdt.doc.user/reference/cdt_u_memoryview.htm
View file

@ -13,17 +13,17 @@
<h1>Memory view</h1>
<p>The <b>Memory</b> view of the Debug
<p>The <strong>Memory</strong> view of the Debug
perspective lets you monitor and modify your process memory. The process memory
is presented as a list of so called <b>memory monitors</b>. Each monitor represents
a section of memory specified by it's location called <b>base address</b>. Each
memory monitor can be displayed in different predefined data formats -- <b>memory
renderings</b>. The debugger supports five rendering types -- <b>hexadecimal</b>
(default), <b>ascii</b>, <b>signed integer</b> and <b>unsigned integer</b>. The
is presented as a list of so called <strong>memory monitors</strong>. Each monitor represents
a section of memory specified by it's location called <strong>base address</strong>. Each
memory monitor can be displayed in different predefined data formats -- <strong>memory
renderings</strong>. The debugger supports five rendering types -- <strong>hexadecimal</strong>
(default), <strong>ascii</strong>, <strong>signed integer</strong> and <strong>unsigned integer</strong>. The
default rendering is displayed automatically on the monitor creation.</p>
<p><img src="../images/view_memory.png" width="718" height="235" alt="Memory View"></p>
<p>The Memory view contains two
panes -- the <b>Memory Monitors</b> pane and the <b>Memory Renderings</b> pane. The
panes -- the <strong>Memory Monitors</strong> pane and the <strong>Memory Renderings</strong> pane. The
Memory Monitors pane displays the list of memory monitors added to the debug
session currently selected in the Debug view. The content of the Memory
Renderings pane is controlled by the selection in the Memory Monitors pane and
@ -34,9 +34,9 @@ configured to display two renderings simultaneously.</p>
<p>The table below lists the icons displayed in the Memory view toolbar.</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td width="16%" align="left"><div align="center"><b>Command</b></div></td>
<td width="32%"><div align="center"><b>Name</b></div></td>
<td width="52%"><div align="center"><b>Description</b></div></td>
<td width="16%" align="left"><div align="center"><strong>Command</strong></div></td>
<td width="32%"><div align="center"><strong>Name</strong></div></td>
<td width="52%"><div align="center"><strong>Description</strong></div></td>
</tr>
<tr>
<td valign="top"><div align="center"><img src="../images/icon_new_memory_view.png" width="22" height="21" alt="New Memory View icon"></div></td>
@ -78,9 +78,9 @@ configured to display two renderings simultaneously.</p>
<td valign="top">Menu &gt; Preferences </td>
<td valign="top"><p>Opens the Preferences window allowing you to set:</p>
<ul>
<li><b>Reset Memory Monitor</b> - set to reset only visible or all renderings when reseting a memory monitor </li>
<li><b>Padded String</b> - enter strings to show unretrievable memory </li>
<li><b>Select Codepages</b> - specify the standard to convert memory to ASCII and EBCDIC strings </li>
<li><strong>Reset Memory Monitor</strong> - set to reset only visible or all renderings when reseting a memory monitor </li>
<li><strong>Padded String</strong> - enter strings to show unretrievable memory </li>
<li><strong>Select Codepages</strong> - specify the standard to convert memory to ASCII and EBCDIC strings </li>
</ul> </tr>
<tr>
<td valign="top">&nbsp;</td>
@ -93,9 +93,9 @@ configured to display two renderings simultaneously.</p>
<p>The Monitors pane context menu inside the Memory view includes:</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td width="19%" align="left"><div align="center"><b>Command</b></div></td>
<td width="35%"><div align="center"><b>Name</b></div></td>
<td width="46%"><div align="center"><b>Description</b></div></td>
<td width="19%" align="left"><div align="center"><strong>Command</strong></div></td>
<td width="35%"><div align="center"><strong>Name</strong></div></td>
<td width="46%"><div align="center"><strong>Description</strong></div></td>
</tr>
<tr>
<td valign="top"><div align="center"><img src="../images/icon_add_mem_monitor.png" width="18" height="18" alt="Add Memory Monitor icon"></div></td>
@ -118,9 +118,9 @@ configured to display two renderings simultaneously.</p>
<p>The Rendering pane context menu inside the Memory view includes:</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td width="19%" align="left"><div align="center"><b>Command</b></div></td>
<td width="35%"><div align="center"><b>Name</b></div></td>
<td width="46%"><div align="center"><b>Description</b></div></td>
<td width="19%" align="left"><div align="center"><strong>Command</strong></div></td>
<td width="35%"><div align="center"><strong>Name</strong></div></td>
<td width="46%"><div align="center"><strong>Description</strong></div></td>
</tr>
<tr>
<td valign="top"><div align="center"><img src="../images/icon_add_mem_monitor.png" width="18" height="18" alt="Add Rendering icon"></div></td>

14
doc/org.eclipse.cdt.doc.user/reference/cdt_u_modules_view.htm
View file

@ -14,7 +14,7 @@
<h1>Modules view</h1>
<p>The <b>Modules</b> view of the Debug
<p>The <strong>Modules</strong> view of the Debug
perspective lets you view information about the modules loaded in the current
debug session, including executables and shared libraries. The view consists
of two areas: the modules tree and the detail pane. The detail pane displays
@ -30,9 +30,9 @@ source files, etc.</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td width="10%" align="left"><b>Command</b></td>
<td width="30%"><b>Name</b></td>
<td width="60%"><b>Description</b></td>
<td width="10%" align="left"><strong>Command</strong></td>
<td width="30%"><strong>Name</strong></td>
<td width="60%"><strong>Description</strong></td>
</tr>
<tr>
<td><img border="0" src="../images/icon_load_all_modules.png" alt="Load Symbols for all modules icon"></td>
@ -47,9 +47,9 @@ source files, etc.</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
<tr>
<td width="10%" align="left"><b>Command</b></td>
<td width="30%"><b>Name</b></td>
<td width="60%"><b>Description</b></td>
<td width="10%" align="left"><strong>Command</strong></td>
<td width="30%"><strong>Name</strong></td>
<td width="60%"><strong>Description</strong></td>
</tr>
<tr>
<td><img border="0" src="../images/icon_load_all_modules.png" alt="load symbols for all icon"></td>

26
doc/org.eclipse.cdt.doc.user/reference/cdt_u_navigator_view.htm
View file

@ -23,24 +23,24 @@
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_con_min.png" alt="Minimize icon"></td>
<td valign="top"><b>Minimize</b></td>
<td valign="top"><strong>Minimize</strong></td>
<td valign="top">Minimizes the Navigator view.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_con_max.png" alt="Maximize icon"></td>
<td valign="top"><b>Maximize</b></td>
<td valign="top"><strong>Maximize</strong></td>
<td valign="top">Maximizes the Navigator view.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_back.png" alt="Back Icon"></td>
<td valign="top"><b>Back</b></td>
<td valign="top"><strong>Back</strong></td>
<td valign="top">This command displays the hierarchy that was displayed immediately prior to the current display.&nbsp;
For example, if you Go Into a resource, then the Back command in the resulting display returns the view to the same hierarchy from which you activated the
<i> Go Into</i> command. The hover help for this button tells you where it will take you. This command is similar to the Back button in a web browser.</td>
<em> Go Into</em> command. The hover help for this button tells you where it will take you. This command is similar to the Back button in a web browser.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_forward.png" alt="Forward Icon"></td>
<td valign="top"><b>Forward</b></td>
<td valign="top"><strong>Forward</strong></td>
<td valign="top">This command displays the hierarchy that was displayed immediately after the current display.&nbsp;
For example, if you've just selected the Back command, then selecting the Forward command in the resulting display returns the view to the same hierarchy from which you activated the Back command.&nbsp;The
hover help for this button tells you where it will take you.
@ -48,36 +48,36 @@
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_up.png" alt="Up Icon"></td>
<td valign="top"><b>Up</b></td>
<td valign="top"><strong>Up</strong></td>
<td valign="top">This command displays the hierarchy of the parent of the current highest level resource. The hover help for this button tells you where it will take you.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_collapse_all.png" alt="Collapse All Icon"></td>
<td valign="top"><b>Collapse All</b></td>
<td valign="top"><strong>Collapse All</strong></td>
<td valign="top">This command collapses the tree expansion state of all resources in the view.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_link_with_editor.png" alt="Link with Editor Icon"></td>
<td valign="top"><b>Link with Editor</b></td>
<td valign="top"><strong>Link with Editor</strong></td>
<td valign="top">This command toggles whether the Navigator view selection is linked to the active editor.
When this option is selected, changing the active editor will automatically update the Navigator selection to the resource being edited.</td>
</tr>
<tr>
<td align="center" valign="top"><img src="../images/icon_menu.png" alt="Menu Icon"></td>
<td valign="top"><b>Menu</b></td>
<td valign="top"><strong>Menu</strong></td>
<td valign="top">Click the black upside-down triangle icon to open a menu of items specific to the Navigator view.<br><br>
<dl>
<p><dt>Select Working Set</dt>
<dd>Opens the <B>Select Working Set</B> dialog to allow selecting a working set for the Navigator view.</dd></p>
<dd>Opens the <strong>Select Working Set</strong> dialog to allow selecting a working set for the Navigator view.</dd></p>
<p><dt>Deselect Working Set</dt>
<dd>Deselects the current working set. </dd></p>
<p><dt>Edit Active Working Set</dt>
<dd>Opens the <B>Edit Working Set</B> dialog to allow changing the current working set.</dd></p>
<dd>Opens the <strong>Edit Working Set</strong> dialog to allow changing the current working set.</dd></p>
<p><dt>Sort</dt>
<dd>This command sorts the resources in the Navigator view according to the selected schema:<br>
<ul>
<li><b>By Name</b>:&nbsp; Resources are sorted alphabetically, according to the full name of the resource (e.g., A.TXT, then B.DOC, then C.HTML, etc.)</li>
<li><b>By Type</b>:&nbsp; Resources are sorted alphabetically by file type/extension (e.g., all DOC files, then all HTML files, then all TXT files, etc.).</li>
<li><strong>By Name</strong>:&nbsp; Resources are sorted alphabetically, according to the full name of the resource (e.g., A.TXT, then B.DOC, then C.HTML, etc.)</li>
<li><strong>By Type</strong>:&nbsp; Resources are sorted alphabetically by file type/extension (e.g., all DOC files, then all HTML files, then all TXT files, etc.).</li>
</ul></p>
<p><dt>Filters</dt>
<dd>This command allows you to select filters to apply to the view so that you can show or hide various resources as needed.

12
doc/org.eclipse.cdt.doc.user/reference/cdt_u_new_proj_wiz.htm
View file

@ -8,18 +8,18 @@
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<h1>New Project Wizard</h1>
<p>The <b>New Project</b> wizard helps you create a new C or C++ project in the workbench.
<p>The <strong>New Project</strong> wizard helps you create a new C or C++ project in the workbench.
To access the wizard, from the menu bar select
<b>File > New > Project</b>.
The <b>New Project</b> wizard appears:
<strong>File > New > Project</strong>.
The <strong>New Project</strong> wizard appears:
</p>
<p><img src="../images/new_project_wizard.png" alt="New Project Wizard"></p>
<p>With the <b>New Project</b> wizard you can choose to:</p>
<p>With the <strong>New Project</strong> wizard you can choose to:</p>
<ul>
<li>Create <b>C Project</b></li>
<li>Create <b>C++ Project</b></li>
<li>Create <strong>C Project</strong></li>
<li>Create <strong>C++ Project</strong></li>
</ul>
<p>
You can either provide your makefile to build new project,

12
doc/org.eclipse.cdt.doc.user/reference/cdt_u_new_proj_wiz_config.htm
View file

@ -19,30 +19,30 @@
<th>Function</th>
</tr>
<tr>
<td><b>Project type</b></td>
<td><strong>Project type</strong></td>
<td>Selected project type.</td>
</tr>
<tr>
<td><b>Tool-chains</b></td>
<td><strong>Tool-chains</strong></td>
<td>One or more selected tool chains</td>
</tr>
<tr>
<td><b>Configurations</b></td>
<td><strong>Configurations</strong></td>
<td>List of all build configurations to be created.
Check items you want to create.
At least one configuration must be checked.
</td>
</tr>
<tr>
<td><b>Select all</b></td>
<td><strong>Select all</strong></td>
<td>Checks all configurations</td>
</tr>
<tr>
<td><b>Deselect all</b></td>
<td><strong>Deselect all</strong></td>
<td>Unchecks all configurations</td>
</tr>
<tr>
<td><b>Advanced settings ...</b></td>
<td><strong>Advanced settings ...</strong></td>
<td>Displays properties dialog for new project.</td>
</tr>
</tbody>

12
doc/org.eclipse.cdt.doc.user/reference/cdt_u_new_proj_wiz_name.htm
View file

@ -9,8 +9,8 @@
<body>
<h1>New Project Wizard - Select Name and Location</h1>
<p>Select a name for the project. You can also enter a new path for
your project by deselecting the <b>Use Default Location</b> checkbox
and entering the new path in the <b>Location</b> text box.</p>
your project by deselecting the <strong>Use Default Location</strong> checkbox
and entering the new path in the <strong>Location</strong> text box.</p>
<p><img src="../images/new_proj_wz_name.png"
alt="New Project Wizard - Select Name and Location"></p>
<p>
@ -21,17 +21,17 @@ and entering the new path in the <b>Location</b> text box.</p>
<th>Function</th>
</tr>
<tr>
<td><b>Name</b></td>
<td><strong>Name</strong></td>
<td>Specifies the name of the project.</td>
</tr>
<tr>
<td><b>Use Default Location</b></td>
<td><strong>Use Default Location</strong></td>
<td>When selected, creates the new project in the default
workspace location.</td>
</tr>
<tr>
<td><b>Location</b></td>
<td>If <b>Use Default Location</b> is not selected, specifies
<td><strong>Location</strong></td>
<td>If <strong>Use Default Location</strong> is not selected, specifies
the location where the project is to be created.</td>
</tr>
</tbody>

Some files were not shown because too many files have changed in this diff Show more