mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-23 17:05:26 +02:00
Code Issues Wiki Activity

bug 269419 - [Accessibility] DL, DT and DD tag issues

Browse source
This commit is contained in:
Vivian Kong 2009-05-05 18:50:26 +00:00
parent 67dcd86f35
commit 566589ba46
46 changed files with 309 additions and 312 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -23,35 +23,35 @@
</colgroup>
<tbody>
<tr>
<td><dt>Always clear console before building</dt></td>
<td><b>Always clear console before building</b></td>
<td>Select this option to clear the contents of the Console view every time you perform a build.</td>
</tr>
<tr>
<td><dt>Open console when building</dt></td>
<td><b>Open console when building</b></td>
<td>Select this option to open the Console view when you perform a build.</td>
</tr>
<tr>
<td><dt>Bring console to top when building (if present)</dt></td>
<td><b>Bring console to top when building (if present)</b></td>
<td>Select this option to make the Console view the active window when you perform a build.</td>
</tr>
<tr>
<td><dt>Limit console output (#lines)</dt></td>
<td><b>Limit console output (#lines)</b></td>
<td>Specify the maximum number of lines that can display in the Console view.</td>
</tr>
<tr>
<td><dt>Display tab width</dt></td>
<td><b>Display tab width</b></td>
<td>Specify the number of spaces for a tab.</td>
</tr>
<tr>
<td><dt>Output text color</dt></td>
<td><b>Output text color</b></td>
<td>Customize the color of text in the Console view.</td>
</tr>
<tr>
<td><dt>Information message text color</dt></td>
<td><b>Information message text color</b></td>
<td>Customize the color of information text messages in the Console view.</td>
</tr>
<tr>
<td><dt>Error message text color</dt></td>
<td><b>Error message text color</b></td>
<td>Customize the color of error messages in the Console view.</td>
</tr>
</tbody>

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

@ -24,31 +24,31 @@
</colgroup>
<tbody>
<tr>
<td><dt>Enable semantic highlighting</dt></td>
<td><b>Enable semantic highlighting</b></td>
<td>Checkmark to activate semantic highlighting of specific structures in the elements listed.</td>
</tr>
<tr>
<td><dt>Enable</dt></td>
<td><b>Enable</b></td>
<td>Makes the selected element active for syntax coloring.</td>
</tr>
<tr>
<td><dt>Color</dt></td>
<td><b>Color</b></td>
<td>Specifies the color in which to display the selected element.</td>
</tr>
<tr>
<td><dt>Bold</dt></td>
<td><b>Bold</b></td>
<td>Makes the selected element <b>bold</b>.</td>
</tr>
<tr>
<td><dt>Italic</dt></td>
<td><b>Italic</b></td>
<td>Makes the selected element <i>italic</i>.</td>
</tr>
<tr>
<td><dt>Strikethrough</dt></td>
<td><b>Strikethrough</b></td>
<td>Makes the selected element <s>strikethrough</s>.</td>
</tr>
<tr>
<td><dt>Underline</dt></td>
<td><b>Underline</b></td>
<td>Makes the selected element <u>underlined</u>.</td>
</tr>
</tbody>

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

@ -23,33 +23,33 @@
</colgroup>
<tbody>
<tr>
<td><dt>Insert single proposals automatically</dt></td>
<td><b>Insert single proposals automatically</b></td>
<td>Inserts an element into your code when the Content Assist feature finds only one proposal.</td>
</tr>
<tr>
<td><dt>Insert common prefixes automatically</dt></td>
<td><b>Insert common prefixes automatically</b></td>
<td>Inserts common prefixes.</td>
</tr>
<tr>
<td><dt>Completion Proposal Filter</dt></td>
<td><b>Completion Proposal Filter</b></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><dt>Enable "." as trigger</dt></td>
<td><b>Enable "." as trigger</b></td>
<td>Enable to use "." as a trigger for auto-completion.</td>
</tr>
<tr>
<td><dt>Enable "->" as trigger</dt></td>
<td><b>Enable "->" as trigger</b></td>
<td>Enable to use "->" as a trigger for auto-completion.</td>
</tr>
<tr>
<td><dt>Enable "::" as trigger</dt></td>
<td><b>Enable "::" as trigger</b></td>
<td>Enable to use "::" as a trigger for auto-completion.</td>
</tr>
<tr>
<td><dt>delay (ms)</dt></td>
<td><b>delay (ms)</b></td>
<td>Specifies the number of milliseconds before Content Assist is activated.</td>
</tr>
</tbody>

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

@ -22,19 +22,19 @@
</colgroup>
<tbody>
<tr>
<td><dt>Default Proposal Kindsy</dt></td>
<td><b>Default Proposal Kindsy</b></td>
<td>Specifies the types of proposals Content Assist uses and the key bindings assigned.</td>
</tr>
<tr>
<td><dt>Content Assist Cycling</dt></td>
<td><b>Content Assist Cycling</b></td>
<td>Specifies the order and types of proposals Content Assist will cycle through.</td>
</tr>
<tr>
<td><dt>Up</dt></td>
<td><b>Up</b></td>
<td>Moves the selected proposal item up in the cycling list.</td>
</tr>
<tr>
<td><dt>Down</dt></td>
<td><b>Down</b></td>
<td>Moves the selected proposal item down in the cycling list.</td>
</tr>
</tbody>

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

@ -22,57 +22,57 @@
</colgroup>
<tbody>
<tr>
<td><dt>Option</dt></td>
<td><dt>Description</dt></td>
<td><dt>Default</dt></td>
<td><b>Option</b></td>
<td><b>Description</b></td>
<td><b>Default</b></td>
</tr>
<tr>
<td><dt>Enable folding when opening a new editor</dt></td>
<td><b>Enable folding when opening a new editor</b></td>
<td>If enabled, apply folding rules to the new editor.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><dt>Select folding to use</dt></td>
<td><b>Select folding to use</b></td>
<td>Select the folding to use from the available choices.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><dt>Enable folding of preprocessor branches (#if/#endif)</dt></td>
<td><b>Enable folding of preprocessor branches (#if/#endif)</b></td>
<td>If enabled, fold preprocessor branches.</td>
<td>&nbsp;</td>
</tr>
<tr>
<td><dt>Macros</dt></td>
<td><b>Macros</b></td>
<td>If enabled, fold macro definitions.</td>
<td>On</td>
</tr>
<tr>
<td><dt>Functions</dt></td>
<td><b>Functions</b></td>
<td>If enabled, fold functions.</td>
<td>Off</td>
</tr>
<tr>
<td><dt>Methods</dt></td>
<td><b>Methods</b></td>
<td>If enabled, fold methods.</td>
<td>Off</td>
</tr>
<tr>
<td><dt>Structures</dt></td>
<td><b>Structures</b></td>
<td>If enabled, fold structures.</td>
<td>On</td>
</tr>
<tr>
<td><dt>Comments</dt></td>
<td><b>Comments</b></td>
<td>If enabled, fold comments.</td>
<td>Off</td>
</tr>
<tr>
<td><dt>Header Comments</dt></td>
<td><b>Header Comments</b></td>
<td>If enabled, fold header comments.</td>
<td>On</td>
</tr>
<tr>
<td><dt>Inactive Preprocessor Branches</dt></td>
<td><b>Inactive Preprocessor Branches</b></td>
<td>If enabled, fold inactive processor branches.</td>
<td>On</td>
</tr>

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

@ -22,27 +22,27 @@
</colgroup>
<tbody>
<tr>
<td><dt>Smart caret positioning in identifiers</dt></td>
<td><b>Smart caret positioning in identifiers</b></td>
<td>If enabled, there are additional word boundaries inside identifiers.</td>
</tr>
<tr>
<td><dt>Highlight matching brackets</dt></td>
<td><b>Highlight matching brackets</b></td>
<td>When the cursor is beside a bracket, the matching bracket is highlighted.</td>
</tr>
<tr>
<td><dt>Highlight inactive code</dt></td>
<td><b>Highlight inactive code</b></td>
<td>Highlights inactive code when the cursor is positioned inside it.</td>
</tr>
<tr>
<td><dt>Appearance color options</dt></td>
<td><b>Appearance color options</b></td>
<td>Lists the items for which you can specify a color.</td>
</tr>
<tr>
<td><dt>Color</dt></td>
<td><b>Color</b></td>
<td>Specifies the color in which to display the selected item.</td>
</tr>
<tr>
<td><dt>Documentation tool comments</dt></td>
<td><b>Documentation tool comments</b></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

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

@ -21,11 +21,11 @@
</colgroup>
<tbody>
<tr>
<td><dt>Enable editor problem annotation</dt></td>
<td><b>Enable editor problem annotation</b></td>
<td>When selected problems found will be highlighted in the editor.</td>
</tr>
<tr>
<td><dt>Text Hover key modifier preferences</dt></td>
<td><b>Text Hover key modifier preferences</b></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>

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

@ -13,6 +13,7 @@
<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>
<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>
<colgroup>
@ -21,38 +22,38 @@
</colgroup>
<tbody>
<tr>
<td><dt>Alert me when scalability mode will be turned on</dt></td>
<td><b>Alert me when scalability mode will be turned on</b></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><dt>Enable scalability mode options when the number of lines in the file is more than</dt></td>
<td><b>Enable scalability mode options when the number of lines in the file is more than</b></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><dt>Enable all scalability mode options</dt></td>
<td><b>Enable all scalability mode options</b></td>
<td>If enabled, all options below are enabled, too.</td>
</tr>
<tr>
<td><dt>Disable editor live parsing</dt></td>
<td><b>Disable editor live parsing</b></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><dt>Disable semantic highlighting</dt></td>
<td><b>Disable semantic highlighting</b></td>
<td>If enabled, C/C++ identifiers will not be colored.</td>
</tr>
<tr>
<td><dt>Disable syntax coloring</dt></td>
<td><b>Disable syntax coloring</b></td>
<td>If enabled, no coloring of keywords, comments and literals is done.</td>
</tr>
<tr>
<td><dt>Disable parsing-based content assist proposals</dt></td>
<td><b>Disable parsing-based content assist proposals</b></td>
<td>If enabled, content assist proposals which require parsing the file will not be available.</td>
</tr>
<tr>
<td><dt>Disable content assist auto activation</dt></td>
<td><b>Disable content assist auto activation</b></td>
<td>If enabled, content assist will not be activated automatically on trigger sequences, like '.', '::' or '->'.</td>
</tr>
</tbody>

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

@ -21,39 +21,39 @@
</colgroup>
<tbody>
<tr>
<td><dt>"Strings"</dt></td>
<td><b>"Strings"</b></td>
<td>If enabled, automatically close string quotes.</td>
</tr>
<tr>
<td><dt>(Parenthesis) and [square] brackets</dt></td>
<td><b>(Parenthesis) and [square] brackets</b></td>
<td>If enabled, automatically close parenthesis and square brackets.</td>
</tr>
<tr>
<td><dt>&lt;Angle&gt; brackets</dt></td>
<td><b>&lt;Angle&gt; brackets</b></td>
<td>If enabled, automatically close angle brackets.</td>
</tr>
<tr>
<td><dt>{Braces}</dt></td>
<td><b>{Braces}</b></td>
<td>If enabled, automatically close curly braces.</td>
</tr>
<tr>
<td><dt>Tab key indents the current line</dt></td>
<td><b>Tab key indents the current line</b></td>
<td>If enabled, indent the current line when the tab key is pressed.</td>
</tr>
<tr>
<td><dt>Adjust indentation</dt></td>
<td><b>Adjust indentation</b></td>
<td>Adjust the indentation of pasted text to match the current indentation level.</td>
</tr>
<tr>
<td><dt>Wrap automatically</dt></td>
<td><b>Wrap automatically</b></td>
<td>Enable to automatically wrap string literals when they exceed the max line length.</td>
</tr>
<tr>
<td><dt>Escape text when pasting into a literal string</dt></td>
<td><b>Escape text when pasting into a literal string</b></td>
<td>If enabled, special characters in pasted strings are escaped when pasted into an existing string literal.</td>
</tr>
<tr>
<td><dt>Automatically indent - New lines and braces</dt></td>
<td><b>Automatically indent - New lines and braces</b></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>

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

@ -22,7 +22,7 @@
</colgroup>
<tbody>
<tr>
<td width="30%" valign="top"><dt>Follow unindexed header files when producing the outline view</dt></td>
<td width="30%" valign="top"><b>Follow unindexed header files when producing the outline view</b></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_code_temp.htm
View file

@ -22,35 +22,35 @@ import, or create your own templates click <b>Window &gt; Preferences &gt; C/C++
</colgroup>
<tbody>
<tr>
<td><dt>New...</dt></td>
<td><b>New...</b></td>
<td>Opens the <b>New Template</b> dialog to create a new template.</td>
</tr>
<tr>
<td><dt>Edit...</dt></td>
<td><b>Edit...</b></td>
<td>Opens the <b>Edit Template</b> dialog to edit the selected template.</td>
</tr>
<tr>
<td><dt>Remove</dt></td>
<td><b>Remove</b></td>
<td>Removes the selected templates from the list.</td>
</tr>
<tr>
<td><dt>Restore Removed</dt></td>
<td><b>Restore Removed</b></td>
<td>Restores templates deleted by the last Remove action.</td>
</tr>
<tr>
<td><dt>Revert to Default</dt></td>
<td><b>Revert to Default</b></td>
<td>Removes the last edits made to the selected template restoring it to it's unmodified state.</td>
</tr>
<tr>
<td><dt>Import...</dt></td>
<td><b>Import...</b></td>
<td>Imports a template.</td>
</tr>
<tr>
<td><dt>Export...</dt></td>
<td><b>Export...</b></td>
<td>Exports the selected templates.</td>
</tr>
<tr>
<td><dt>Use code formatter</dt></td>
<td><b>Use code formatter</b></td>
<td>Enable to apply the currently selected code style to the template.</td>
</tr>
</tbody>

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

@ -22,16 +22,16 @@
</colgroup>
<tbody>
<tr>
<td width="30%" valign="top"><dt>New...</dt></td>
<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>
</tr>
<tr>
<td width="30%" valign="top"><dt>Edit...</dt></td>
<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>
</tr>
<tr>
<td width="30%" valign="top"><dt>Delete</dt></td>
<td width="30%" valign="top"><b>Delete</b></td>
<td valign="top">To delete the currently selected action, click <b>Delete</b>. </td>
</tr>
</tbody>

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

@ -21,27 +21,27 @@
</colgroup>
<tbody>
<tr>
<td width="30%" valign="top"><dt>Show full paths</dt></td>
<td width="30%" valign="top"><b>Show full paths</b></td>
<td valign="top">Displays the full path of resources.</td>
</tr>
<tr>
<td width="30%" valign="top"><dt>Default variable format</dt></td>
<td width="30%" valign="top"><b>Default variable format</b></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"><dt>Default expression format</dt></td>
<td width="30%" valign="top"><b>Default expression format</b></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"><dt>Default register format</dt></td>
<td width="30%" valign="top"><b>Default register format</b></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"><dt>Maximum number of displayed instructions</dt></td>
<td width="30%" valign="top"><b>Maximum number of displayed instructions</b></td>
<td valign="top">The maximum number of assembler instructions displayed in the Disassembly view.</td>
</tr>
<tr>
<td width="30%" valign="top"><dt>Color of source lines</dt></td>
<td width="30%" valign="top"><b>Color of source lines</b></td>
<td valign="top">The color of source lines in the Disassembly view if mixed source/disassembly code is shown.</td>
</tr>
<tr>

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

@ -14,7 +14,7 @@
<p>Use the <b>Common Source Lookup Path</b> 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>
<dl>
<table width="600px" cellpadding="5" cellspacing="0" border="1" >
<caption>
<b>Common Source Lookup Path Options </b>
@ -25,7 +25,7 @@
</colgroup>
<tbody>
<tr>
<td width="99" valign="top"><dt>Add...</dt></td>
<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>
<ul>
<li>File System Directory</li>
@ -37,15 +37,15 @@
</td>
</tr>
<tr>
<td valign="top"><dt>Edit...</dt></td>
<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>
</tr>
<tr>
<td valign="top"><dt>Remove</dt></td>
<td valign="top"><b>Remove</b></td>
<td>Remove the currently selected souce container.</td>
</tr>
<tr>
<td valign="top"><dt>Up</dt></td>
<td valign="top"><b>Up</b></td>
<td>Move the currently selected source container higher in the list.</td>
</tr>
<tr>
@ -54,7 +54,7 @@
</tr>
</tbody>
</table>
</dl>
<p><img src="../images/nokia2007Copyright.png" alt="Nokia Copyright Statement" ><br>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" ></p>
</body>

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

@ -173,7 +173,7 @@ debugging attached processes).</td>
</table>
<h3>Debug view context menu commands </h3>
<dl>
<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>
@ -340,7 +340,7 @@ debugging attached processes).</td>
<td>Opens the <b>Properties for</b> window showing the process properties. </td>
</tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="../concepts/cdt_c_over_dbg.htm">Debug overview</a><br>

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

@ -22,7 +22,7 @@
<h3>Disassembly view context menu commands </h3>
<dl>
<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>
@ -41,7 +41,7 @@
<td valign="top">Resume program execution from the line selected in the Disassembly view. </td>
</tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21"> <br>
<a href="../concepts/cdt_c_dbg_info.htm">Debug information</a></p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21"> <br>

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

@ -11,8 +11,7 @@
<p>You can define the discovery options on the Discovery Options page
of a C/C++ project's properties window.<br>
</p>
<dl>
</dl>
<p style="margin-left: 40px;"><img img=""
src="../images/cdt_file_discovery.png"
alt="C/C++ File Properties, Discovery Options"
@ -29,15 +28,15 @@ of a C/C++ project's properties window.<br>
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Exclude resource from build</dt></td>
<td><b>Exclude resource from build</b></td>
<td>Excludes the selected file from the build process.</td>
</tr>
<tr>
@ -45,25 +44,25 @@ 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><dt>Automate discovery of paths and symbols</dt></td>
<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>
</tr>
<tr>
<td><dt>Report path detection problems</dt></td>
<td><b>Report path detection problems</b></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><dt>Discovery profile options</dt></td>
<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>
</tr>
<tr>
<td><dt>Enable generate scanner info command</dt></td>
<td><b>Enable generate scanner info command</b></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>
</td>
</tr>
<tr>
<td><dt>Compiler invocation command</dt></td>
<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.
<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>
@ -85,7 +84,7 @@ of a C/C++ project's properties window.<br>
</td>
</tr>
<tr>
<td><dt>Browse</dt></td>
<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>
</tr>
</tbody>

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

@ -22,11 +22,11 @@ Customizes the tools and tool options used in your build configuration.
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>

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

@ -11,8 +11,7 @@
<p>You can define the discovery options on the Discovery Options page
of a C/C++ project's properties window.<br>
</p>
<dl>
</dl>
<p style="margin-left: 40px;"><img img=""
src="../images/cdt_fold_discovery.png"
alt="C/C++ Folder Properties, Discovery Options"
@ -29,15 +28,15 @@ of a C/C++ project's properties window.<br>
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Exclude resource from build</dt></td>
<td><b>Exclude resource from build</b></td>
<td>Excludes the selected folder from the build process.</td>
</tr>
<tr>
@ -45,25 +44,25 @@ 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><dt>Automate discovery of paths and symbols</dt></td>
<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>
</tr>
<tr>
<td><dt>Report path detection problems</dt></td>
<td><b>Report path detection problems</b></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><dt>Discovery profile options</dt></td>
<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>
</tr>
<tr>
<td><dt>Enable generate scanner info command</dt></td>
<td><b>Enable generate scanner info command</b></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>
</td>
</tr>
<tr>
<td><dt>Compiler invocation command</dt></td>
<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.
<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>
@ -85,7 +84,7 @@ of a C/C++ project's properties window.<br>
</td>
</tr>
<tr>
<td><dt>Browse</dt></td>
<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>
</tr>
</tbody>

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

@ -26,11 +26,11 @@ Customizes the tools and tool options used in your build configuration.
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>

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

@ -23,27 +23,27 @@
</colgroup>
<tbody>
<tr>
<td><dt>Posix Make</dt></td>
<td><b>Posix Make</b></td>
<td>Enable to generate makefiles that are POSIX Make compatible.</td>
</tr>
<tr>
<td><dt>GNU Make</dt></td>
<td><b>GNU Make</b></td>
<td>Enable to generate makefiles that are GNU Make compatible.</td>
</tr>
<tr>
<td><dt>New...</dt></td>
<td><b>New...</b></td>
<td>Opens the <b>Browse for Folder</b> dialog to select a directory.</td>
</tr>
<tr>
<td><dt>Remove</dt></td>
<td><b>Remove</b></td>
<td>Click to remove the currently selected directory from the Makefile include directories list.</td>
</tr>
<tr>
<td><dt>Up</dt></td>
<td><b>Up</b></td>
<td>Click to move the currently selected directory up in the list.</td>
</tr>
<tr>
<td><dt>Down</dt></td>
<td><b>Down</b></td>
<td>Click to move the currently selected directory down in the list.</td>
</tr>
</tbody>

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

@ -23,15 +23,15 @@
</colgroup>
<tbody>
<tr>
<td><dt>Color</dt></td>
<td><b>Color</b></td>
<td>Click to set the selected syntax item to a specific color.</td>
</tr>
<tr>
<td><dt>Bold</dt></td>
<td><b>Bold</b></td>
<td>If enabled, set the selected syntax item to <b>bold</b>.</td>
</tr>
<tr>
<td><dt>Italic</dt></td>
<td><b>Italic</b></td>
<td>If enabled, set the selected syntax item to <i>italic</i>.</td>
</tr>
</tbody>
@ -45,7 +45,7 @@
</colgroup>
<tbody>
<tr>
<td><dt>Enable folding when opening a new editor</dt></td>
<td><b>Enable folding when opening a new editor</b></td>
<td>If enabled, activate folding when a new Makefile editor is opened.</td>
</tr>
</tbody>

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

@ -30,7 +30,7 @@ Renderings pane is controlled by the selection in the Memory Monitors pane and
consists of the tabs that display renderings. The Memory Renderings pane can be
configured to display two renderings simultaneously.</p>
<dl><h3>Memory view toolbar icons</h3>
<h3>Memory view toolbar icons</h3>
<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>
@ -88,9 +88,7 @@ configured to display two renderings simultaneously.</p>
<td valign="top">Specify the memory loading mode to use when rendering scrolls to the end of the buffer. </td>
</tr>
</table>
</dl>
<dl>
<h3>Monitors pane context menu </h3>
<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">
@ -115,8 +113,7 @@ configured to display two renderings simultaneously.</p>
<td valign="top">Resets the current memory monitor view. </td>
</tr>
</table>
</dl>
<dl>
<h3>Rendering pane context menu </h3>
<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">
@ -181,7 +178,7 @@ configured to display two renderings simultaneously.</p>
<td valign="top">Refreshes the Rendering pane. </td>
</tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="../concepts/cdt_c_dbg_info.htm">Debug information</a></p>

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

@ -27,7 +27,7 @@
<td valign="top">Define the scope as configuration-wide or per language for this profile. </td>
</tr>
<tr>
<td width="217" valign="top"><dt><b>Automate discovery of paths and symbols</b></dt></td>
<td width="217" valign="top"><b>Automate discovery of paths and symbols</b></td>
<td width="357" valign="top">Activate this checkbox to scan the build output to populate the paths and symbol tables.</td>
</tr>
<tr>

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

@ -24,11 +24,11 @@ to handle configurations.
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td>Specifies the type of configuration(s) for the selected project. A <b>Debug</b> configuration lets you see what's going on "inside" a program as it executes. To debug your application, you must use executables compiled for debugging. These executables contain additional debug information that lets the debugger make direct associations between the source code and the binaries generated from the original source. A <b>Release</b> configuration provides the tools with options set to create an application with the best performance.</td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td>Opens the Manage Configurations dialog where you can set which configurations are active based on the toolchain(s) that were specified for the selected project. In addition, you can also create new configurations, rename an existing configuration, or remove ones that are no longer required.
<p><b>Note:</b>The <b>Configuration</b> selection that you specify in this dialog (unlike the behavior of CDT 3.x) affects only these property pages. This means that the selected configuration is not made the active configuration (the one used to build project).</p>
</td>

48
doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_build.htm
View file

@ -29,53 +29,53 @@ and, moreover, change the visibility of other property pages.
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for its description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for its description.</a></td>
</tr>
<tr>
<td><dt>Builder type</dt></td>
<td><b>Builder type</b></td>
<td>Specifies the type of builder to use: <b>Internal builder</b> (builds C/C++ programs using a compiler that implements the C/C++ Language Specificationt) and <b>External builder</b> (external tools let you configure and run programs and Ant buildfiles using the Workbench, which can saved and run at a later time to perform a build).</td>
</tr>
<tr>
<td><dt>Use default build command</dt></td>
<td><b>Use default build command</b></td>
<td>When enabled, this option indicates that you want to use the default <b>make</b> command. When disabled, it indicates the use of a new <b>make</b> command. This option is only available when the <b>Build type</b> option is set to <b>External</b>.</td>
</tr>
<tr>
<td><dt>Build command</dt></td>
<td><b>Build command</b></td>
<td>Specifies the default command used to start the build utility for your specific toolchain. Use this field if you want to use a build utility other than the default <b>make</b> command (when the <b>Use default build command</b> is not selected the field is active, and when you use an external builder or a custom makefile, you can provide your specific commands).</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td><b>Variables</b></td>
<td>Opens the Select build variable dialog where you can add environment variables and custom variables to the build command.
<p><img img src="../images/prop_cbuild_selbldvar.png" alt="C/C++ Project Properties, C/C++ Build, Select build variable"></p>
<br>
</tr>
<tr>
<td><dt>Generate Makefiles automatically</dt></td>
<td><b>Generate Makefiles automatically</b></td>
<td>When selected, Eclipse changes between two different CDT modes: it either uses the customer's makefile for the build (referred to as a 'Standard Make project' in CDT 3.x) if one exists, or it generate makefiles for the user (called 'Managed build project' in CDT 3.x). By default, this option is automatically set.</td>
</tr>
<tr>
<td><dt>Expand Env. Variable Refs in Makefiles</dt></td>
<td><b>Expand Env. Variable Refs in Makefiles</b></td>
<td>Defines whether environment variables ( ${xxx} ) should be expanded in makefile. By default, this option is automatically set.</td>
</tr>
<tr>
<td><dt>Build directory</dt></td>
<td><b>Build directory</b></td>
<td>Defines the location where the build operation takes place. This location will contain the generated artifacts from the build process. This option is disabled when the <b>Generate Makefiles automatically</b> option is enabled.</td>
</tr>
<tr>
<td><dt>Workspace</dt></td>
<td><b>Workspace</b></td>
<td>Opens the Folder Selection dialog where you can select a workspace location for the project. This is the directory that will contain the plug-ins and features to build, including any generated artifacts. This button is only visible when <b>Generate makefiles automatically</b> is set not selected.</td>
</tr>
<tr>
<td><dt>File system</dt></td>
<td><b>File system</b></td>
<td>Opens the file system navigator where you can specify another file system to use. This button is only visible when <b>Generate makefiles automatically</b> is set not selected.</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td><b>Variables</b></td>
<td>Opens the Select build variable dialog where you can select a variable to specify as an argument for the build directory, or create and configure simple build variables which you can reference in build configurations that support variables. This button is only visible when <b>Generate makefiles automatically</b> is set not selected.</td>
</tr>
</tbody>
@ -94,12 +94,12 @@ and, moreover, change the visibility of other property pages.
</colgroup>
<tbody>
<tr>
<td><dt>Stop on first build error</dt></td>
<td><b>Stop on first build error</b></td>
<td>Stops building when Eclipse encounters an error.
<p><b>Note:</b> If this option is not selected, it is helpful for building large projects because it tells <b>make</b> to continue making other independent rules even when one rule fails.</p></td>
</tr>
<tr>
<td><dt>Use parallel build</dt></td>
<td><b>Use parallel build</b></td>
<td>When enabled, this option indicates the activation of the generation of parallel builds.
<p>If you enable this option, you need to determine the number of parallel jobs to perform:</p>
@ -110,47 +110,47 @@ and, moreover, change the visibility of other property pages.
</td>
</tr>
<tr>
<td><dt>Workbench build behavior</dt></td>
<td><b>Workbench build behavior</b></td>
<td>By default, the following settings are what the builder uses when instructed to build, rebuild, clean, and so on. You can change these settings so that new projects can use different targets if these defaults are not appropriate.</td>
</tr>
<tr>
<td><dt>Build on resource save (Auto build)</dt></td>
<td><b>Build on resource save (Auto build)</b></td>
<td>When selected, builds your project whenever resources are saved. By default, this option is selected and builds occur automatically each time resources are modified. When this option is not selected, a build occurs only manually using a menu item. If you require more control over when builds occur (for example, when a build should wait until you finish a large assortment of changes), disable this option and manually invoke builds yourself.</td>
</tr>
<tr>
<td><dt>make build target</dt> ( for Build on resource save (Auto build))</td>
<td><b>make build target</b> ( for Build on resource save (Auto build))</td>
<td>To build your project when resources are saved and change the default <b>make</b> build target, enable the <b>Build on resource save (Auto Build)</b> option, and specify a new build target in the <b>Make build target</b> field.</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td><b>Variables</b></td>
<td>Opens the Select build variable dialog where you can add variables to the build command.
<p><img img src="../images/prop_cbuild_selbldvar.png" alt="C/C++ Project Properties, C/C++ Build, Select build variable"></p>
</tr>
<tr>
<td><dt>Build (Incremental build)</dt></td>
<td><b>Build (Incremental build)</b></td>
<td>Defines what the builder calls when an incremental build is performed. When this option is enabled, an incremental build occurs meaning that only resources that have changed since the last build are considered. If this option is disabled, a full build occurs, meaning that all resources within the scope of the build are considered.
</td>
</tr>
<tr>
<td><dt>make build target</dt> (for Build (Incremental build))</td>
<td><b>make build target</b> (for Build (Incremental build))</td>
<td>To change the build default <b>make</b> build target, enable the <b>Build (Incremental build)</b> option, and specify a new build target in the <b>Make build target</b> field.</td>
</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td><b>Variables</b></td>
<td>Opens the Select build variable dialog where you can add variables to the <b>make build target</b> command.</td>
</tr>
<tr>
<td><dt>Clean</dt></td>
<td><b>Clean</b></td>
<td>Defines what the builder calls when a clean is performed. The <b>make clean</b> is defined in the <b>makefile</b>.</td>
</tr>
<tr>
<td><dt>make build target</dt> (for Clean)</td>
<td><b>make build target</b> (for Clean)</td>
<td>To change the rebuild default <b>make</b> build target, enable the <b>Clean</b> option, and specify a new build target in the <b>Make build target</b> field.</td>
</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td><b>Variables</b></td>
<td>Opens the Select build variable dialog where you can add variables to the <b>make build target</b> command.</td></td>
</tr>
</tbody>

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

@ -23,15 +23,15 @@
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Discovery Profiles Scope</dt></td>
<td><b>Discovery Profiles Scope</b></td>
<td>Specifies the type of profile to set for discovery:
<ul>
<li><b>Per Language</b> - Enables the association of different profiles with different resource types (different tools and input types), to have different settings discovered, e.g. for C and C++ source files and for different tools used by the project.
@ -49,47 +49,47 @@ the entire project (configuration). This means that both the project and per-fil
<td>Shows a list of language specific compilers. Select a language from the list.</td>
</tr>
<tr>
<td><dt>Automate discovery of paths and symbols</dt></td>
<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, and include files.</td>
</tr>
<tr>
<td><dt>Report path detection problems</dt></td>
<td><b>Report path detection problems</b></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><dt>Discovery profile</dt></td>
<td><b>Discovery profile</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.</td>
</tr>
<tr>
<td><dt>Enable build output scanner info discovery</dt></td>
<td><b>Enable build output scanner info discovery</b></td>
<td>Configures the scanner to parse the output from a build for compiler commands with options that specify the definition of preprocessor symbols, and include search paths (for GCC compiler, -D and -I respectively). 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>
</tr>
<tr>
<td><dt>Load</dt></td>
<td><b>Load</b></td>
<td>Lets you load a file to discover paths and symbols based on a previous builds' output. To activate the discovery select a build log file and then the <b>Load</b> button. 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>.
<p><b>Note:</b> Click <b>Variables</b> to open the Select Variables window to define a build output file.</p>
</td>
</tr>
<tr>
<td><dt>Load build output from file</dt></td>
<td><b>Load build output from file</b></td>
<td>Specifies the name of the file you selected to load the build output from. 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>
</tr>
<tr>
<td><dt>Browse</dt></td>
<td><b>Browse</b></td>
<td>Click to locate a previously built output file to load the build output from. 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>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td><b>Variables</b></td>
<td>Click to specify an argument for, or create and configure simple launch variables which you can reference in launch configurations that support variables. 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>
</tr>
<tr>
<td><dt>Enable generate scanner info command</dt></td>
<td><b>Enable generate scanner info command</b></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>
</td>
</tr>
<tr>
<td><dt>Compiler invocation command</dt></td>
<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.
<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>
@ -111,7 +111,7 @@ the entire project (configuration). This means that both the project and per-fil
</td>
</tr>
<tr>
<td><dt>Browse</dt></td>
<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>
</tr>
</tbody>

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

@ -24,56 +24,56 @@ Customizes the build environment for all projects in the workspace; it lets you
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Environment variables to set</dt></td>
<td><b>Environment variables to set</b></td>
<td>Shows the current list of environment variables and their corresponding value. These are the environment variable values used when building.</td>
</tr>
<tr>
<td><dt>Variable</dt></td>
<td><b>Variable</b></td>
<td>Specifies the name of the environment variable.</td>
</tr>
<tr>
<td><dt>Value</dt></td>
<td><b>Value</b></td>
<td>Specifies the value of the environment variable.</td>
</tr>
<tr>
<td><dt>Append variables to native environment</dt></td>
<td><b>Append variables to native environment</b></td>
<td>Appends the variables to the native environment during its execution.</td>
</tr>
<tr>
<td><dt>Replace native environment with specified one </dt></td>
<td><b>Replace native environment with specified one </b></td>
<td>Replaces the native environment with the specified variables, and then restores the native environment upon its completion.</td>
</tr>
<tr>
<td><dt>New</dt></td>
<td><b>New</b></td>
<td>Opens a dialog to create a new environment variable and value. Custom environment variables that you create appear in bold within the list.
<p><img img="" src="../images/cdt_buildenv_newenvvar.png" alt="C/C++ Project Properties, Environment, New environment variable"></p> <br>
<p>Click <b>Variables</b> to Select variables by name to include in the value. Select <b>Add to all configurations</b> to make this new environment variable available to all configurations for the selected project; otherwise, the variable is only available for the currently selected configuration.</p>
</td>
</tr>
<tr>
<td><dt>Select</dt></td>
<td><b>Select</b></td>
<td>Opens the Select variables dialog where you can choose from a list of system variables.
<p><img img="" src="../images/cdt_buildenv_selectvar.png" alt="C/C++ Project Properties, Environment, New environment variable"></p></td>
</td>
</tr>
<tr>
<td><dt>Edit</dt></td>
<td><b>Edit</b></td>
<td>Modifies the name and value of the selected environment variable.</td>
</tr>
<tr>
<td><dt>Remove</dt></td>
<td><b>Remove</b></td>
<td>Removes the selected environment variables from the list.</td>
</tr>
<tr>
<td><dt>Undefine</dt></td>
<td><b>Undefine</b></td>
<td>Undefines the currently selected variable; however, some variables, such as the PATH variable, cannot be undefined.
</td>
</tr>

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

@ -23,27 +23,27 @@
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Artifact Type</dt></td>
<td><b>Artifact Type</b></td>
<td>Show the type for the selected artifact. Select an artifact type that is built by the currently selected build configuration (such as an <b>Executable</b>, <b>Static library</b>, and <b>Shared library</b>).</td>
</tr>
<tr>
<td><dt>Artifact name</dt></td>
<td><b>Artifact name</b></td>
<td>Indicates the name of artifact. By default, the name is the same as project name.</td>
</tr>
<tr>
<td><dt>Artifact extension</dt></td>
<td><b>Artifact extension</b></td>
<td>Specifies the file extension for the specified artifact type.</td>
</tr>
<tr>
<td><dt>Output prefix</dt></td>
<td><b>Output prefix</b></td>
<td>Indicates a prefix that you want to prepend to the output results. </td>
</tr>
</tbody>

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

@ -28,27 +28,27 @@ symbols of the object file using the C/C++ Projects view.</p>
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Binary Parser</dt> (top pane)</td>
<td><b>Binary Parser</b> (top pane)</td>
<td>Lists all of the binary parsers currently known to CDT. Select the parsers that you want to use, and select the corresponding line to edit parser's options, if required.</td>
</tr>
<tr>
<td><dt>Binary Parser Option</dt></td>
<td><b>Binary Parser Option</b></td>
<td>Shows the parameters for the currently selected parser in the list above. Depending on the parser you select, the options in the list will be different (in particular, some may have no options at all).</td>
</tr>
<tr>
<td><dt>Move up</dt></td>
<td><b>Move up</b></td>
<td>Moves the selected parser higher in list. <b>Note:</b> The order matters for selected parsers only: they are applied to binaries in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.</td>
</tr>
<tr>
<td><dt>Move down</dt></td>
<td><b>Move down</b></td>
<td>Move the selected parser lower in list. <b>Note:</b> The order matters for selected parsers only: they are applied to binaries in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.</td>
</tr>
</tbody>

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

@ -23,31 +23,31 @@ build output log.</p>
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Error Parsers</dt></td>
<td><b>Error Parsers</b></td>
<td>Lists all of the error parsers currently known to CDT. Select the parsers that you want to use, and select the corresponding line to edit parser's options, if required.</td>
</tr>
<tr>
<td><dt>Move up</dt></td>
<td><b>Move up</b></td>
<td>Moves the selected parser higher in list. <b>Note:</b> The order matters for selected parsers only: they are applied to error logs in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.</td>
</tr>
<tr>
<td><dt>Move down</dt></td>
<td><b>Move down</b></td>
<td>Move the selected parser lower in list. <b>Note:</b> The order matters for selected parsers only: they are applied to error logs in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.</td>
</tr>
<tr>
<td><dt>Check all</dt></td>
<td><b>Check all</b></td>
<td>Selects all error parsers in the list.</td>
</tr>
<tr>
<td><dt>Uncheck all</dt></td>
<td><b>Uncheck all</b></td>
<td>Makes all error parsers in the list unselected.</td>
</tr>
</tbody>

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

@ -36,39 +36,39 @@ including pre-build or post-build steps.<br>
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Pre-build Steps</dt></td>
<td><b>Pre-build Steps</b></td>
<td>Identifies any steps that are to occur before the build takes place.
<p><b>Note:</b> The pre-build step is not executed if the state of the main build is determined to be up to date; otherwise it is executed. An attempt to execute the main build will occur regardless of the success or failure of executing the pre-build step.</p>
</td>
</tr>
<tr>
<td><dt>Command</dt></td>
<td><b>Command</b></td>
<td>Specifies one or more commands to execute immediately before the execution of the build. Use semicolons to separate multiple commands.</td>
</tr>
<tr>
<td><dt>Description</dt></td>
<td><b>Description</b></td>
<td>Specifies optional descriptive text associated with the pre-build step that is displayed in the build output immediately before the execution of the pre-build step command (or commands).</td>
</tr>
<tr>
<td><dt>Post-build steps</dt></td>
<td><b>Post-build steps</b></td>
<td>Identifies any steps that are to occur after the build takes place.
<p><b>Note:</b> The post-build step is not executed if the state of the main build is determined to be up to date. It will be executed only if the main-build has executed successfully.</p>
</td>
</tr>
<tr>
<td><dt>Command</dt></td>
<td><b>Command</b></td>
<td>Specifies one or more commands to execute immediately after the execution of the build. Use semicolons to separate multiple commands.</td>
</tr>
<tr>
<td><dt>Description</dt></td>
<td><b>Description</b></td>
<td>Specifies optional descriptive text associated with the post-build step that is displayed in the build output immediately after the execution of the post-build step command (or commands).</td>
</tr>
</tbody>

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

@ -23,11 +23,11 @@ Customizes the tools and tool options used in your build configuration.
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>

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

@ -24,31 +24,31 @@ you specify which tools the builder needs to include when it builds the project
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Display compatible toolchains only</dt></td>
<td><b>Display compatible toolchains only</b></td>
<td>When selected, it shows a list of toochains that are only compatible with the current configuration. When this option is not selected, it shows a list of all toolchains known to the Eclipse CDT. A Toolchain is compatible if it can run on given platform. .</td>
</tr>
<tr>
<td><dt>Current toolchain</dt></td>
<td><b>Current toolchain</b></td>
<td>Indicates the toolchain to use with the current configuration. 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.</td>
</tr>
<tr>
<td><dt>Current builder</dt></td>
<td><b>Current builder</b></td>
<td>Indicates the builder used to build the selected configuration. A builder refers to an external <b>make</b> utility, such as GNU make, that the Eclipse CDT uses (and relies on) to build a project. The CDT can generate <b>makefiles</b> automatically when you create a Make C or C++ project, or you have the option of creating a C or C++ Make project where you provide the makefile yourself.</td>
</tr>
<tr>
<td><dt>Used tools</dt></td>
<td><b>Used tools</b></td>
<td>Shows a list of tools currently included for the selected toolchain. You can click <b>Select Tools</b> to modify this list.</td>
</tr>
<tr>
<td><dt>Select Tools</dt></td>
<td><b>Select Tools</b></td>
<td>Opens the Select Tools dialog that lets you add or remove tools from the list of tools for the selected toolchain.</td>
</tr>
</tbody>

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

@ -23,47 +23,47 @@ you control the environment variables used by the build to for the purposes of b
</colgroup>
<tbody>
<tr>
<td><dt>Environment variables to set</dt></td>
<td><b>Environment variables to set</b></td>
<td>Shows the current list of environment variables and their corresponding value. These are the environment variable values used when running an application.</td>
</tr>
<tr>
<td><dt>Configuration</dt></td>
<td><b>Configuration</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><b>Manage configurations</b></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>(The variables table)</dt></td>
<td><b>(The variables table)</b></td>
<td>Lists the CDT build variables and system variables, by <b>Name</b>, <b>Type</b>, and the <b>Value</b>. Custom Build variables are identified by the name being highlighted using a <b>bold</b> font.</td>
</tr>
<tr>
<td><dt>Name</dt></td>
<td><b>Name</b></td>
<td>Indicates the name of the variable, either a user defined variable or a system variable.</td>
</tr>
<tr>
<td><dt>Type</dt></td>
<td><b>Type</b></td>
<td>Shows the type for the variable.</td>
</tr>
<tr>
<td><dt>Value</dt></td>
<td><b>Value</b></td>
<td>Specifies the value of the variable.</td>
</tr>
<tr>
<td><dt>Show system variables</dt></td>
<td><b>Show system variables</b></td>
<td>When selected, system variables are included in the Variables table; otherwise, they are excluded so that only user defined variables appear in the Variables list.</td>
</tr>
<tr>
<td><dt>Add</dt></td>
<td><b>Add</b></td>
<td>Creates a new variable and corresponding value.</td>
</td>
</tr>
<tr>
<td><dt>Edit</dt></td>
<td><b>Edit</b></td>
<td>Modifies the name and value of the selected variable.</tr>
<tr>
<td><dt>Delete</dt></td>
<td><b>Delete</b></td>
<td>Removes the selected variables from the list. <b>Note:</b> Some variables are read-only and cannot be removed.
</td>
</tr>

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

@ -24,24 +24,24 @@ which order they are used.</p>
</colgroup>
<tbody>
<tr>
<td><dt>Configure the builders for the project</dt></td>
<td><b>Configure the builders for the project</b></td>
<td>Selects which builders to enable from the list. You can disable the CDT Builder and you can control when the CDT Builder runs with respect to the project builders that you define.
</td>
</tr>
<tr>
<td><dt>New...</dt></td>
<td><b>New...</b></td>
<td>Opens the Choose configuration type dialog so that you can add a new builder to the list. <p>
</p><p><img img="" src="../images/prop_builders_newbldr.png"
alt="C/C++ Project Properties, Builders, Choose configuration type"></p>
<p>The <b>Ant Builder</b> option lets you configure and deploy projects; however, if you want to use some other tool or prefer to do it yourself, you can set up a <b>Program</b> external tool project builder. This type allows you to customize the deployment of your project as you require, while maintaining the convenience of automatically running your script every time your project is built.</p>
<p>The <b>Program</b> option lets you to define an external tool for any executable file that is accessible on your local or network file system. For example, if instead of Ant you prefer to use your own shell scripts or Windows .bat files to package and deploy your Eclipse projects, you can then create a <b>Program</b> external tool that would specify where and how to execute that script.</p></tr>
<tr>
<td><dt>Import...</dt></td>
<td><b>Import...</b></td>
<td>Opens the Import launch configuration dialog so that you can import a builder to include it in the list.<p></p>
</p><p><img img="" src="../images/prop_builders_imprtlnchcnfg.png">
<p></p></tr>
<tr>
<td><dt>Edit...</dt></td>
<td><b>Edit...</b></td>
<td>Opens the Configure Builder dialog that lets you specify when to run the selected builder.<p></p>
</p><p><img img="" src="../images/prop_builders_editbldr.png">
<p></p>
@ -54,13 +54,13 @@ which order they are used.</p>
</ul>
</p></tr>
<tr>
<td><dt>Remove</dt></td>
<td><b>Remove</b></td>
<td>Removes the selected builder from the list.</tr>
<tr>
<td><dt>Up</dt></td>
<td><b>Up</b></td>
<td>Moves the currently selected builder higher in the list to change the builder order.</tr>
<tr>
<td><dt>Down</dt></td>
<td><b>Down</b></td>
<td>Moves the currently selected builder lower in the list to change the builder order.</tr>
</tbody>
</table>

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

@ -23,44 +23,44 @@
</colgroup>
<tbody>
<tr>
<td><dt>Path</dt></td>
<td><b>Path</b></td>
<td>Specifies the location of the selected resource type within the workspace. For example, similar to folders, projects map to directories in the file system.</td>
</tr>
<tr>
<td><dt>Type</dt></td>
<td><b>Type</b></td>
<td>Indicates the type for the selected resource: <b>Folder</b>, <b>Project</b>, or <b>File</b>.</td>
</tr>
<tr>
<td><dt>Location</dt></td>
<td><b>Location</b></td>
<td>Specifics the location of the selected resource within the file system.</td>
</tr>
<tr>
<td><dt>Last modified</dt></td>
<td><b>Last modified</b></td>
<td>Shows the date that the selected resource was last modified.</td>
</tr>
<tr>
<td><dt>Text file encoding</dt></td>
<td><b>Text file encoding</b></td>
<td>Sets an alternate text encoding. Because text files are encoded differently (depending on the locale and platform), use the default text file encoding for the locale of your host operating system. However, if you want to work with text files that originate from another source (for example, to work with text files that use a different encoding scheme than your native one, so that you can easily exchange files with another team), choose <b>Other</b> and select an appropriate one from the list.</td>
</tr>
<tr>
<td><dt>Inherited from container</dt></td>
<td><b>Inherited from container</b></td>
<td>When enabled, the selected resource inherits the text encoding specified for it's container resource.</td>
</tr>
<tr>
<td><dt>Other</dt></td>
<td><b>Other</b></td>
<td>When enabled, the selected resource uses an alternate text encoding other than that specified for its container resource. You can enable this option if you want to work with text files that originate from another source (ones that use a different encoding scheme than your native one), so that you can easily exchange files with others.</td>
</td>
</tr>
<tr>
<td><dt>New text file line delimiter</dt></td>
<td><b>New text file line delimiter</b></td>
<td>Specifies the end of line character(s) to use for new text files being created.</td>
</tr>
<tr>
<td><dt>Inherited from container</dt></td>
<td><b>Inherited from container</b></td>
<td>When enabled, the selected resource inherits the character line ending for new text files specified for it's container resource.</td>
</tr>
<tr>
<td><dt>Other</dt></td>
<td><b>Other</b></td>
<td>When enabled, the selected resource uses an alternate end of line character(s) for new text files other than that specified for its container resource. For example, you can set the <b>Text file encoding</b> option to UTF-8, and then set the line endings character for new files to <b>Unix</b>, so that text files are saved in a format that is not specific to the Windows operating system, and the files can easily be shared amongst various developer systems.</td>
</td>
</tr>

7
doc/org.eclipse.cdt.doc.user/reference/cdt_u_registersview.htm
View file

@ -17,7 +17,7 @@
Values that have changed are highlighted in the Registers view when your program
stops. </p>
<p><img src="../images/view_registers.png" width="414" height="269"></p>
<dl>
<h3>Registers view toolbar icons</h3>
<p>The table below lists the icons displayed in the Registers view toolbar.</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
@ -47,8 +47,7 @@ stops. </p>
<td valign="top">Provides multiple layout options for the Breakpoints view. </td>
</tr>
</table>
</dl>
<dl>
<h3>Registers view context menu commands </h3>
<p>The Registers view context menu commands include:</p>
<table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#999999" width="600">
@ -173,7 +172,7 @@ stops. </p>
<td valign="top">Activate to wrap the text contents within the visible area of the Details pane of the Registers view. </td>
</tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="../concepts/cdt_c_dbg_info.htm">Debug information</a></p>

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

@ -18,18 +18,18 @@ that an application uses and the working directory for a run or debug configurat
<img src="../images/run_debug_arguments.png">
<p></p>
<dl>
<table width="580" fgcolor="#DDD" border="1" cellpadding="2" cellspacing="0" >
<tr ><th>Component</th><th>Description</th></tr>
<tr><td width="30%"><dt>Program arguments</dt></td><td>Specifies the arguments that are passed on the command line.</td></tr>
<tr><td><dt>Variables...</dt></td><td>Select variables by name to include in the program arguments list.</td></tr>
<tr><td><dt>Working directory</dt></td><td>Specifies the run/debug configuration working directory.</td></tr>
<tr><td><dt>Use default</dt></td><td>Checkmark to specify the local directory or uncheck to specify a different workspace, a file system location, or variable.</td></tr>
<tr><td><dt>Workspace...</dt></td><td>Specifies the path of, or browse to, a workspace relative working directory.</td></tr>
<tr><td><dt>File System...</dt></td><td>Specifies the path of, or browse to, a file system directory.</td></tr>
<tr><td><dt>Variables...</dt></td><td>Select variables by name to include in the working directory.</td></tr>
<tr><td width="30%"><b>Program arguments</b></td><td>Specifies the arguments that are passed on the command line.</td></tr>
<tr><td><b>Variables...</b></td><td>Select variables by name to include in the program arguments list.</td></tr>
<tr><td><b>Working directory</b></td><td>Specifies the run/debug configuration working directory.</td></tr>
<tr><td><b>Use default</b></td><td>Checkmark to specify the local directory or uncheck to specify a different workspace, a file system location, or variable.</td></tr>
<tr><td><b>Workspace...</b></td><td>Specifies the path of, or browse to, a workspace relative working directory.</td></tr>
<tr><td><b>File System...</b></td><td>Specifies the path of, or browse to, a file system directory.</td></tr>
<tr><td><b>Variables...</b></td><td>Select variables by name to include in the working directory.</td></tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>

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

@ -18,22 +18,22 @@ the location in which to store your run configuration and how you access it, how
<img src="../images/run_debug_common.png">
<p></p>
<dl>
<table width="580" border="1" cellpadding="2" cellspacing="0" >
<tr><th>Component</th><th>Description</th></tr>
<tr><td width="30%"><dt>Local file</dt></td><td>Saves the launch configuration locally.</td></tr>
<tr><td><dt>Shared file</dt></td><td>Specifies the path of, or browse to, a workspace to store the launch configuration file, and be able to commit it to CVS.</td></tr>
<tr><td><dt>Display in favorites menu</dt></td><td>Add configuration name to Run or Debug menus for easy selection.</td></p></tr>
<tr><td><dt>Console Encoding</dt></td><td>Specify encoding scheme to use for console output.</td></tr>
<tr><td><dt>Allocate Console (necessary for input)</dt></td><td>Check to assign a console view to receive the output.</td></tr>
<tr><td><dt>File</dt></td><td>Specify file name to save output.</td></tr>
<tr><td><dt>Browse Workspace...</dt></td><td>Specifies the path of, or browse to, a workspace to store the output file.</td></tr>
<tr><td><dt>Browse File System...</dt></td><td>Specifies the path of, or browse to, a file system directory to store the output file.</td></tr>
<tr><td><dt>Variables...</dt></td><td>Select variables by name to include in the output file.</td></tr>
<tr><td><dt>Append</dt></td><td>Check to append output. Uncheck to recreate file each time.</td></tr>
<tr><td><dt>Launch in background</dt></td><td>Check to launch configuration in background mode.</td></tr>
<tr><td width="30%"><b>Local file</b></td><td>Saves the launch configuration locally.</td></tr>
<tr><td><b>Shared file</b></td><td>Specifies the path of, or browse to, a workspace to store the launch configuration file, and be able to commit it to CVS.</td></tr>
<tr><td><b>Display in favorites menu</b></td><td>Add configuration name to Run or Debug menus for easy selection.</td></p></tr>
<tr><td><b>Console Encoding</b></td><td>Specify encoding scheme to use for console output.</td></tr>
<tr><td><b>Allocate Console (necessary for input)</b></td><td>Check to assign a console view to receive the output.</td></tr>
<tr><td><b>File</b></td><td>Specify file name to save output.</td></tr>
<tr><td><b>Browse Workspace...</b></td><td>Specifies the path of, or browse to, a workspace to store the output file.</td></tr>
<tr><td><b>Browse File System...</b></td><td>Specifies the path of, or browse to, a file system directory to store the output file.</td></tr>
<tr><td><b>Variables...</b></td><td>Select variables by name to include in the output file.</td></tr>
<tr><td><b>Append</b></td><td>Check to append output. Uncheck to recreate file each time.</td></tr>
<tr><td><b>Launch in background</b></td><td>Check to launch configuration in background mode.</td></tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>

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

@ -17,16 +17,16 @@
<img src="../images/run_debug_debugger.png">
<p></p>
<dl>
<table width="580" fgcolor="#DDD" border="1" cellpadding="2" cellspacing="0" >
<tr ><th>Component</th><th>Description</th></tr>
<tr><td width="30%"><dt>Debugger</dt></td><td>Selects debugger type from the list.</td></tr>
<tr><td><dt>Stop on startup at</dt></td><td>Stops program at specified location.</td></tr>
<tr><td valign="top"><dt>Advanced</dt></td><td>Opens the Advanced Options dialog.<br><p><img src="../images/run_debug_debugger_advopt.png">
<tr><td width="30%"><b>Debugger</b></td><td>Selects debugger type from the list.</td></tr>
<tr><td><b>Stop on startup at</b></td><td>Stops program at specified location.</td></tr>
<tr><td valign="top"><b>Advanced</b></td><td>Opens the Advanced Options dialog.<br><p><img src="../images/run_debug_debugger_advopt.png">
</td></p></tr>
<tr><td><dt>Debugger Options</dt></td><td>Displays options specific to the selected debugger type.</td></tr>
<tr><td><b>Debugger Options</b></td><td>Displays options specific to the selected debugger type.</td></tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>

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

@ -18,19 +18,19 @@ set environment variables and values to use when an application runs.</p>
<img src="../images/run_debug_environment.png">
<p></p>
<dl>
<table width="580" fgcolor="#DDD" border="1" cellpadding="2" cellspacing="0" >
<tr ><th>Component</th><th>Description</th></tr>
<tr><td width="30%"><dt>Name</dt></td><td>Displays the name of environment variables.</td></tr>
<tr><td><dt>Value</dt></td><td>Displays the value of environment variables.</td></tr>
<tr><td><dt>New</dt></td><td>Creates a new environment variable.</td></tr>
<tr><td><dt>Select...</dt></td><td>Select one or more environment variables to set.</td></tr>
<tr><td><dt>Edit</dt></td><td>Modifies the name and value of an environment variable.</td></tr>
<tr><td><dt>Remove</dt></td><td>Removes selected environment variables from the list.</td></tr>
<tr><td><dt>Append environment to native environment</dt></td><td>Append the environment variables shown to the current native environment.</td></tr>
<tr><td><dt>Replace native environment with specified environment</dt></td><td>Replaces the current native environment with the specified environment set shown.</td></tr>
<tr><td width="30%"><b>Name</b></td><td>Displays the name of environment variables.</td></tr>
<tr><td><b>Value</b></td><td>Displays the value of environment variables.</td></tr>
<tr><td><b>New</b></td><td>Creates a new environment variable.</td></tr>
<tr><td><b>Select...</b></td><td>Select one or more environment variables to set.</td></tr>
<tr><td><b>Edit</b></td><td>Modifies the name and value of an environment variable.</td></tr>
<tr><td><b>Remove</b></td><td>Removes selected environment variables from the list.</td></tr>
<tr><td><b>Append environment to native environment</b></td><td>Append the environment variables shown to the current native environment.</td></tr>
<tr><td><b>Replace native environment with specified environment</b></td><td>Replaces the current native environment with the specified environment set shown.</td></tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>

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

@ -17,15 +17,15 @@
<img src="../images/run_debug_main.png">
<p></p>
<dl>
<table width="640" fgcolor="#DDD" border="1" cellpadding="2" cellspacing="0" >
<tr ><th>Component</th><th>Description</th></tr>
<tr><td width="30%"><dt>Project</dt></td><td>Specifies the name of the project.</td></tr>
<tr><td><dt>C/C++ Application</dt></td><td>Specifies the name of the application.</td></tr>
<tr><td><dt>Search Project...</dt></td><td>Specifies the binary or binaries to run within the project.</td></tr>
<tr><td><dt>Connect process input output to a terminal</dt></td><td>&nbsp;</td></tr>
<tr><td width="30%"><b>Project</b></td><td>Specifies the name of the project.</td></tr>
<tr><td><b>C/C++ Application</b></td><td>Specifies the name of the application.</td></tr>
<tr><td><b>Search Project...</b></td><td>Specifies the binary or binaries to run within the project.</td></tr>
<tr><td><b>Connect process input output to a terminal</b></td><td>&nbsp;</td></tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>

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

@ -19,18 +19,18 @@ application. By default, this information is taken from the build path of your p
<img src="../images/run_debug_source.png">
<p></p>
<dl>
<table width="580" fgcolor="#DDD" border="1" cellpadding="2" cellspacing="0" >
<tr ><th>Component</th><th>Description</th></tr>
<tr><td width="30%"><dt>Add</dt></td><td>Adds new source containers to the Source Lookup Path search list.</td></tr>
<tr><td><dt>Edit...</dt></td><td>Modifies the content of the selected source container.</td></tr>
<tr><td><dt>Remove</dt></td><td>Removes selected items from the Source Lookup Path list.</td></p></tr>
<tr><td><dt>Up</dt></td><td>Moves selected items up the Source Lookup Path list.</td></tr>
<tr><td><dt>Down</dt></td><td>Moves selected items down the Source Lookup Path list.</td></tr>
<tr><td><dt>Restore Default</dt></td><td>Restores the default source search list.</td></tr>
<tr><td><dt>Search for duplicate source files on the path</dt></td><td valign="top">Controls whether to continue search for files with the same name.</td></tr>
<tr><td width="30%"><b>Add</b></td><td>Adds new source containers to the Source Lookup Path search list.</td></tr>
<tr><td><b>Edit...</b></td><td>Modifies the content of the selected source container.</td></tr>
<tr><td><b>Remove</b></td><td>Removes selected items from the Source Lookup Path list.</td></p></tr>
<tr><td><b>Up</b></td><td>Moves selected items up the Source Lookup Path list.</td></tr>
<tr><td><b>Down</b></td><td>Moves selected items down the Source Lookup Path list.</td></tr>
<tr><td><b>Restore Default</b></td><td>Restores the default source search list.</td></tr>
<tr><td><b>Search for duplicate source files on the path</b></td><td valign="top">Controls whether to continue search for files with the same name.</td></tr>
</table>
</dl>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>

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

@ -10,6 +10,7 @@
<h1>C/C++ search</h1>
<p><img alt="Search Dialog Box" src="../images/search.png"></p>
<p> </p>
<dl>
<dt>Search string</dt>
<dd>Specifies a search string.</dd>
<dd>The search functions support the following wildcards:</dd>
@ -174,6 +175,7 @@ projects (plus the include paths) of the selected resource <br>
</dd>
<br>
<dd>Working sets can be created and used from within the search dialog.</dd>
</dl>
<p><img height="21" width="143" alt="Related concepts"
src="../images/ngconcepts.gif" border="0"> <br>
<a href="../concepts/cdt_o_code_entry.htm">Coding aids</a><br>

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

@ -27,22 +27,22 @@ debugger handles each one.</p>
</colgroup>
<tbody>
<tr>
<td width="99"><dt>Name</dt></td>
<td width="99"><b>Name</b></td>
<td width="475">Displays the name of the signal.</td>
</tr>
<tr>
<td><dt>Pass</dt></td>
<td><b>Pass</b></td>
<td>Where &quot;yes&quot; is displayed, the debugger lets your program see the
signal. Your program can handle the signal, or else it may terminate if the
signal is fatal and not handled.</td>
</tr>
<tr>
<td><dt>Suspend</dt></td>
<td><b>Suspend</b></td>
<td>Where &quot;yes&quot; is displayed, the debugger suspends your program when this
signal is handled.</td>
</tr>
<tr>
<td><dt>Description</dt></td>
<td><b>Description</b></td>
<td>Displays a description of the signal.</td>
</tr>
</tbody>