Skip to main content
summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorL. Frank Turovich2010-05-12 16:44:44 -0400
committerL. Frank Turovich2010-05-12 16:44:44 -0400
commit7c0b1af07724d529ff8b84e15c2c96837fbee94d (patch)
tree7aa4986f139d57e71a47dc4b1d2aa8a6397993f0 /doc
parent2af46568e4f744982f5cb651a54298a7b6770a90 (diff)
downloadorg.eclipse.cdt-7c0b1af07724d529ff8b84e15c2c96837fbee94d.tar.gz
org.eclipse.cdt-7c0b1af07724d529ff8b84e15c2c96837fbee94d.tar.xz
org.eclipse.cdt-7c0b1af07724d529ff8b84e15c2c96837fbee94d.zip
Bug 309605 - Revised Create Make Target, Debug Breadcrumb, and GDB pref panel pages
Diffstat (limited to 'doc')
-rw-r--r--doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm49
-rw-r--r--doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_breadcrumb.htm6
-rw-r--r--doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm43
3 files changed, 69 insertions, 29 deletions
diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm
index 8b1445bb94..641cc21b74 100644
--- a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm
+++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm
@@ -11,20 +11,45 @@
<h1>Create a Make Target</h1>
-<p>You can define build settings when you create a Make Target.</p>
+<p>Use the <strong>Create a Make Target</strong> dialog box to define build settings when creating a Make Target.</p>
<p><img img src="../images/create_make_target_win.png" alt="Create a Make Target Window"></p>
-
-<dl>
- <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 <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>
-
+<p><table border="1" cellpadding="4" cellspacing="0" width="700px" bordercolor="#DDDDDD" >
+ <caption><strong>Create a Make Target options</strong></caption>
+ <colgroup>
+ <col width="25%" valign="top" >
+ <col width="75%" valign="top" >
+ </colgroup>
+ <tr>
+ <th>Option</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Target Name</strong></td>
+ <td valign="top">Name of the Make Target.</td>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Make Target</strong></td>
+ <td valign="top">The reference to the make section in your makefile.</td>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Use default</strong></td>
+ <td valign="top">Select this checkbox to use the default make command. Clear the check box to specify a new make command.</td>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Build command</strong></td>
+ <td valign="top">If you clear the <strong>Use default</strong> checkbox type a new make command in this field.</td>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Stop on first build error</strong></td>
+ <td valign="top">Stops the build when an error occurs.</td>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Run all project builders</strong></td>
+ <td valign="top">Runs additional project builders such as discovery.</td>
+ </tr>
+</table>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
@@ -36,7 +61,7 @@
<a href="../tasks/cdt_t_proj_build_set.htm">Defining Project Build settings</a></p>
-
+<hr />
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" >
diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_breadcrumb.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_breadcrumb.htm
index 4d86970369..be4c8a234b 100644
--- a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_breadcrumb.htm
+++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_breadcrumb.htm
@@ -9,10 +9,10 @@
<body>
<h1> Debug Breadcrumb </h1>
-<p> Debug Breadcrumb is a compact presentation of the currently active debug context and its parents. </p>
+<p> Use the <strong>Debug Breadcrumb</strong> layout to show a compact presentation of the currently active debug context and its parents. </p>
<p> <img src="../images/view_debug_breadcrumb.png" alt="Debug Breadcrumb"> </p>
-<p> To enable the Debug Breadcrumb, change the <a href="cdt_u_dbg_view.htm"><strong>Debug View</strong></a> layout to Breadcrumb (Select <strong>Layout-&gt;Breadcrumb</strong> in the Debug View menu). Alternatively, resize the Debug View such that the height of the view is small enough to fit only one line of text. This will cause the view to change over to the Breadcrumb layout automatically. </p>
-<p> The Debug Breadcrumb allows to invoke actions on any element shown in the breadcrumb. Actions can be invoked through the context menu or through key bindings. To select an element in the breadcrumb click on it or activate the Debug view and use the <strong>left</strong> and <strong>right</strong> arrow keys.
+<p> To show the Debug Breadcrumb layout, in the <strong>Debug</strong> view toolbar select <strong>View Menu &gt; Layout &gt; Breadcrumb</strong>. Alternatively, resize the Debug view such that the height of the view is small enough to fit only one line of text. This causes the view to change over to the Breadcrumb layout automatically. </p>
+<p> The Debug Breadcrumb allows you to invoke actions on any element shown in the breadcrumb. Actions can be invoked through the context menu or through key bindings. To select an element in the breadcrumb click on it or activate the Debug view and use the <strong>left</strong> and <strong>right</strong> arrow keys.
<p> You can also change the active debug context using the breadcrumb. Click on one of the arrows or any element top open a drop-down window. The drop-down shows all the siblings of the element for which the drop-down was opened. Click on an element to make it the new active debug context. To open the drop-down with the keyboard, select and element and press the <strong>down</strong> key.
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm
index ab44169345..34cf61cc82 100644
--- a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm
+++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm
@@ -6,30 +6,45 @@
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>GDB Debugging Preferences</title>
<link rel="stylesheet" type="text/css" href="../help.css">
+ <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body>
<h1>GDB Debugging Preferences</h1>
-<p>This preferences page lets you control how the CDT debugger behaves when debugging with GDB,
+<p>Use the <strong>GDB</strong> preferences panel to control how the CDT debugger behaves when debugging with GDB,
specifically when using a <em>GDB (DSF)</em> launcher.
The page is accessible at:
<strong>Window &gt; Preferences &gt; C/C++ &gt; Debug &gt; GDB</strong>.</p>
+<p><img src="../images/cdt_dsfgdb_preferences_page.png" alt="GDB preferences panel"></p>
-<img src="../images/cdt_dsfgdb_preferences_page.png" alt="GDB preferences page">
-<dl>
- <dt>Enable GDB traces</dt>
- <dd>When checked, the debug session will produce an additional console which will contain all the gdb/mi activity. Basically, this details the
+
+<p><table border="1" cellpadding="4" cellspacing="0" width="700px" bordercolor="#DDDDDD" >
+ <caption><strong>GDB Preference Panel Options</strong></caption>
+ <colgroup>
+ <col width="25%" valign="top" >
+ <col width="75%" valign="top" >
+ </colgroup>
+ <tr>
+ <th>Option</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Enable GDB traces</strong></td>
+ <td valign="top">When checked, the debug session will produce an additional console which will contain all the gdb/mi activity. Basically, this details the
interaction between the CDT debugger and GDB. This information is often critical when the debugger is not behaving as you expect. Turn this on and submit
- the console output when submitting a bugzilla report against the CDT debugger.
- </dd>
- <dt>Terminate GDB when last process exits</dt>
- <dd>When checked, the CDT debugger will terminate the GDB host process's after all the target processes it is debugging have terminated. Otherwise it will leave it running.</dd>
- <dt>Use enhanced debug hover</dt>
- <dd>When checked, hovering over an expression in the editor during a debug session will bring up an <em>enhanced</em> expression evaluation control. Otherwise, a more basic control is used. This, of course, assumes that you have the debugger's hovering capability turned on in C/C++ > Editor > Hovers. If not, this checkbox has no effect.<br>
- <img src="../images/cdt_debug_hover_modes.png" alt="debug hover modes">
- </dd>
-</dl>
+ the console output when submitting a bugzilla report against the CDT debugger.</td>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Terminate GDB when last process exits</strong></td>
+ <td valign="top">When checked, the CDT debugger will terminate the GDB host process's after all the target processes it is debugging have terminated. Otherwise it will leave it running.</td>
+ </tr>
+ <tr>
+ <td valign="top"><strong>Use enhanced debug hover</strong></td>
+ <td valign="top">When checked, hovering over an expression in the editor during a debug session will bring up an <em>enhanced</em> expression evaluation control. Otherwise, a more basic control is used. This, of course, assumes that you have the debugger's hovering capability turned on in C/C++ > Editor > Hovers. If not, this checkbox has no effect.<br>
+ <img src="../images/cdt_debug_hover_modes.png" alt="debug hover modes"></td>
+ </tr>
+</table>
</body>

Back to the top