This is the raw content from QNX's Momentics guide, being donated to

the CDT project.
author: Sebastien Marineau 2003-06-13 22:29:43 +0000
committer: Sebastien Marineau 2003-06-13 22:29:43 +0000
commit: e380c8ea03d2ea2f35fe4fee83a8a1cb75afc4de (patch)
tree: c5293e694b9cb530f968365f06e9eb2763ee8535 /doc
parent: 22eb93f0e4b6acccdca274b53db680aee2be910d (diff)
download: org.eclipse.cdt-e380c8ea03d2ea2f35fe4fee83a8a1cb75afc4de.tar.gz
org.eclipse.cdt-e380c8ea03d2ea2f35fe4fee83a8a1cb75afc4de.tar.xz
org.eclipse.cdt-e380c8ea03d2ea2f35fe4fee83a8a1cb75afc4de.zip
111 files changed, 3212 insertions, 0 deletions
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/about.html b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/about.html
new file mode 100644
index 00000000000..5ee8cf34cec
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/about.html
@@ -0,0 +1,115 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.ord/TR/html4/loose.dtd">
+<html>
+
+<head>
+
+<title>About This Guide</title>
+
+</head>
+<body bgcolor="#ffffff" text="#000000">
+
+<h1><a name="id1">About This Guide</a></h1>
+
+
+
+
+<p>The C/C++ Development Tools (CDT) <cite>User's Guide</cite> describes the components
+of the CDT Eclipse plugins that are available as part of the Eclipse project. This guide 
+describes how to use the CDT tools environment to build your C/C++ based applications.
+
+</p>
+
+<p>The following may help you find information quickly: 
+
+</p>
+<table border=1 width="100%">
+
+<tr>
+<th>If you want to:</th>
+<th>See:</th>
+</tr>
+<tr>
+<td>Learn about perspectives, views, and editors 	</td>
+<td><a href="conc.html">IDE Concepts</a></td>
+</tr>
+<tr>
+<td>Create a C or C++ program	</td>
+<td><a href="cdev.html">Developing C/C++ Programs</a></td>
+</tr>
+<tr>
+<td>Track and control different versions of software	</td>
+<td><a href="cvs.html">Source Control</a></td>
+</tr>
+<tr>
+<td>Debug your executables </td>
+<td><a href="dbug.html">Debugging Programs</a></td>
+</tr>
+<tr>
+<td>Create a new QNX C Application project	</td>
+<td><a href="cwiz.html">Common Wizards</a></td>
+</tr>
+<tr>
+<td>Run or debug your program	</td>
+<td><a href="lnch.html">Starting Your Programs</a></td>
+</tr>
+</table>
+
+
+</p>
+<p>This book is organized so you can learn what you need to know quickly and easily. Each chapter has these common sections:
+ </p>
+<ul>
+<li>The overview gives you a quick synopsis of what you're about to learn.  
+	</li>
+<li>The suggested reading section tells you what you should know before starting each chapter.
+ 	</li>
+<li>The related information section gives you a quick list of the supporting material, including tutorials and movies. Some are marked "recommended."
+	</li>
+<li>The "How ... works" section gives you an idea of what's happening "underneath the covers" -- how the IDE, the host, and the target work together.</li>
+</ul>
+<p>The tutorials are in a separate guide so you can print and use them side by side with the corresponding chapters in this guide.</p>
+<p>
+
+ </p>
+
+
+<h1><a name="id3">Assumptions</a></h1>
+
+<p>This guide assumes the following:
+
+
+</p>
+<ul>
+<li>You've already installed the base Eclipse components.</li>
+<li>You've installed the C/C++ Development Tools (CDT) plugin feature.</li>
+<li>You can write code in C or C++.</li>
+</ul>
+
+<h1><a name="id5">Note to Windows users</a></h1>
+
+<p>In our documentation, we use a forward slash
+(<tt>/</tt>) as a delimiter in <em>all</em> pathnames,
+including those pointing to Windows files.
+
+
+</p>
+<p>We also generally follow POSIX/UNIX filesystem conventions.
+
+</p>
+
+</body>
+
+</html>
+
+<!--
+/**********************************************************************
+ * Copyright (c) 2002,2003 QNX Software Systems Ltd. and others.
+ * All rights reserved.   This program and the accompanying materials
+ * are made available under the terms of the Common Public License v0.5
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v05.html
+ * 
+ * Contributors: 
+ * QNX Software Systems - Initial API and implementation
+***********************************************************************/
+-->
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cdev.html b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cdev.html
new file mode 100644
index 00000000000..76b5c2c6bff
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cdev.html
@@ -0,0 +1,812 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.ord/TR/html4/loose.dtd">
+<html>
+
+<head>
+
+<title>Developing C/C++ Programs</title>
+
+</head>
+<body bgcolor="#ffffff" text="#000000">
+<hr>
+
+
+<h1><a name="id1">Developing C/C++ Programs</a></h1>
+
+
+
+
+<p>
+
+The <b>C/C++ Development</b> perspective is probably the perspective 
+where you'll spend most of your time. In it, you'll develop and build 
+your programs. As you move further through your project, you'll likely 
+use this perspective as the jump point for doing your debugging, program 
+analysis, and target system integration.</p>
+<p>
+
+Suggested prior reading:</p>
+<ul>
+<li>the <a href="conc.html">IDE Concepts</a> chapter</li>
+</ul>
+<p>
+
+Related information:</p>
+<ul>
+<li>the <a href="cwiz.html">Common Wizards</a> chapter
+   </li>
+<li>the <a href="lnch.html">Starting Your Programs</a> chapter
+   </li>
+</ul>
+<p></p>
+In this chapter:
+
+<ul>
+<li><a href="#how">Introduction</a>
+   </li>
+<li><a href="#view_c_projects">Controlling the IDE (C/C++ Projects view)</a>
+   </li>
+<li><a href="#creating">Creating projects (New Projects wizard)</a>
+   </li>
+<li><a href="#building">Building projects ( <tt>make</tt>)</a>
+   </li>
+<li><a href="#running">Running programs (launcher)</a>
+   </li>
+<li><a href="#editor_c">Writing code (C/C++ Editor)</a>
+   </li>
+<li><a href="#more">More development features</a>
+   </li>
+</ul> 
+
+<h1><a name="how">Introduction</a></h1>
+
+
+<p>
+
+Before you begin C/C++ development, you must create a project to contain your code; in the IDE, all your work must be contained in projects.</p>
+<p>
+
+The views in the <b>C/C++ Development</b> perspective are driven primarily by selections you make in the <b>C/C++ Editor</b> and the <b>C/C++ Projects</b> view, a specialized version of the <b>Navigator</b> view. Ensure you understand their functionality thoroughly.
+
+</p>
+
+<h2><a name="id4">Wizards and the Launch Configurations dialog</a></h2>
+
+<p>In addition to perspectives and views, the IDE has two major "sections": wizards and the <b>Launch Configurations</b> dialog. To create and run your first program, you need both. The wizards let you quickly create a new project; the <b>Launch Configurations</b> dialog lets you set up how your program runs. 
+Once you've used all these parts of the IDE for the first time, you'll be able to create, build, and run your programs very quickly. For more information, see the <a href="cwiz.html">Common Wizards</a> and <a href="lnch.html">Starting Your Programs</a> chapters.</p>
+<p>
+
+The <b>C/C++ Development</b> perspective also has many features that help you develop code quickly. Once you've learned the basics of creating programs and running them (in this chapter), take some time to browse through this chapter. </p>
+<p>
+
+ </p>
+
+<h1><a name="view_c_projects">Controlling the IDE (C/C++ Projects view)</a></h1>
+
+<p><img src="./images/view_cprojects.jpg" alt="C/C++ Projects view"></p>
+<p>The <b>C/C++ Projects</b> view is probably the most important view in the IDE because you control your projects with it. The selections you make in the <b>C/C++ Projects</b> view greatly affect what information the other views display.</p>
+<p>
+
+The <b>C/C++ Projects</b> view offers a filtered and slightly rearranged version of the <b>Navigator</b> view. </p>
+<p>The <b>Navigator</b> view is part of the core Eclipse platform, so some of the features are documented there:
+
+</p>
+<ul>
+<li>For information about the <b>Navigator</b> view toolbar and icons, follow these links in the <cite>Workbench User Guide</cite>: <b>Concepts</b>--><b>Views</b>--><b>Navigator view</b>.
+   
+   </li>
+<li>For information about the right-click context menu in the <b>Navigator</b> view, follow these links in the <cite>Workbench User Guide</cite>: <b>Reference</b>--><b>User interface information</b>--><b>Views and Editors</b>--><b>Navigator View</b>.
+   </li>
+</ul>
+<p>The <b>C/C++ Projects</b> view has many of the same features as the <b>Navigator</b> view, but is configured specifically for C and C++ development. At first glance, the two may seem identical, but the <b>C/C++ Projects</b> view:</p>
+<ul>
+<li>shows only open C/C++ projects
+   </li>
+<li>pretends that the project's executables are stored in a virtual subdirectory called <tt>bin</tt>
+   </li>
+<li>for a library project, pretends that the project's libraries are in a virtual subdirectory called <tt>lib</tt>
+   </li>
+<li>hides certain files
+   </li>
+<li>includes <b>Build Project</b> and related commands in its right-click menu
+   </li>
+<li>gives an outline of <tt>*.c</tt>, <tt>*.cc</tt>, <tt>*.cpp</tt>, <tt>*.h</tt>, and binary files.
+   </li>
+</ul>
+
+<h2><a name="id7">Opening files</a></h2>
+
+<p>To open files and display them in the editor area:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>C/C++ Projects</b> view, double-click the file to be opened.
+The file  --  even if it's executable  --  opens in the editor area.</td></tr>
+</table>
+
+
+
+<h2><a name="id9">Opening projects</a></h2>
+
+<p>Because the <b>C/C++ Projects</b> view hides closed projects, you must use the <b>Navigator</b> view to open them.</p>
+<p>
+
+To open projects:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>Navigator</b> view, right-click your project, and select <b>Open Project</b>.
+The project opens and appears in the <b>C/C++ Projects</b> view.</td></tr>
+</table>
+
+
+
+<h2><a name="id11">Filtering files</a></h2>
+
+<p>To filter files in the <b>C/C++ Projects</b> view:</p>
+<ol>
+
+<li>In the <b>C/C++ Projects</b> view, click the menu dropdown button <img src="./images/icon_menu.gif" alt="Icon; menu dropdown">.
+   </li>
+<li>Select <b>Filter</b>.
+   The <b>File Filter</b> dialog appears:<p>   	<img src="./images/view_cprojects_filter.jpg" alt="C/C++ Projects view; File Filter dialog">
+   </p></li>
+<li>In the filter pane, select the types of files you wish to hide. The <b>.*</b> selection hides files that start with a period, such as <tt>.cdtproject</tt> and <tt>.project</tt>.
+   </li>
+<li>Click <b>OK</b>.
+   The <b>C/C++ Projects</b> view automatically refreshes and shows only the unfiltered file types.
+   </li>
+</ol>
+
+
+<h2><a name="id13">Outlines of source and executable files</a></h2>
+
+<p>
+
+The <b>C/C++ Projects</b> view shows you the outline of <tt>.c</tt>, <tt>.cc</tt>, and <tt>.h</tt> files:</p>
+<p><img src="./images/view_cprojects_outline_source.jpg" alt="C/C++ Projects view; outline; source"></p>
+<p>This outline is similar to that found in the <b>Outline</b> view. To learn more about the <b>Outline</b> view, see the <a href="#view_outline">"Code synopsis (Outline view)"</a> section in this chapter.</p>
+<p></p>
+<p>The <b>C/C++ Projects</b> view shows you the outlines of executables as well. You can examine the structure of executables to see not only the functions that you declared and used in the file, but the elements that were called indirectly, such as <i>malloc()</i>, <i>_init()</i>, and <i>errno</i>:</p>
+<p><img src="./images/view_cprojects_outline_executable.jpg" alt="C/C++ Projects view; outline; executable"></p>
+ </p>
+<p>To view a file outline in the <b>C/C++ Project</b> view:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>C/C++ Projects</b> view, click the "+" symbol to the left of any <tt>.c</tt>, <tt>.cc</tt>, or <tt>.h</tt>, or executable file. All the executables are grouped in the virtual <tt>bin</tt> directory. The tree expands to show the outline for that file. Click the "-" symbol to collapse the tree again.</td></tr>
+</table>
+
+
+
+<h1><a name="creating">Creating projects (New Project wizard)</a></h1>
+
+<H3>
+@@@ NOTE I've left this in even though it is QNX specific, we would have to 
+customize it to make it CDT generic 
+</H3>
+
+<p>If you're creating an application from scratch, you'll probably want to create a <b>QNX C Application Project</b> or a <b>QNX C ++ Application Project</b>. </p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>For examples of creating specific types of projects, see the <cite>Tutorials</cite> book. We recommend that you create a few tutorial projects before you do too much reading. Having hands-on experience with the IDE gives you a better context for what you read in this guide.
+<p>
+
+For a complete explanation of all the C/C++ project types and options, see the <a href="cwiz.html">Common Wizards</a> chapter.</p></td></tr>
+</table>
+<hr>
+
+
+<p>To create a "Hello World!" <b>QNX C Application Project</b>:</p>
+<ol>
+
+<li>In the <b>C/C++ Development</b> perspective, click the <b>Create a new QNX C Application Project</b> button <img src="./images/icon_newcqnx_app.gif" alt="Icon: Create a QNX C Application Project button">.
+   The <b>New Project</b> dialog appears:<p>   <img src="./images/cwiz_c.jpg" alt="Wizard: Create a QNX C Application Project"> 
+   </p></li>
+<li>In the <b>Name</b> field, type a name for your project (e.g. <tt>myHelloWorldProject</tt>).
+   </li>
+<li>Click <b>Next</b>. The dialog displays the appropriate with tabs.
+   </li>
+<li>In the <b>Options</b> tab, enable <b>Build debug version</b> and <b>Build release version</b>:<p>	<img src="./images/cwiz_c_options.jpg" alt="Common wizards: C/C++ Projects; Options tab">
+
+   </p></li>
+<li>Click <b>Finish</b>.
+   The IDE creates the project and displays the C file (e.g. <tt>myHelloWorldProject.c</tt> in the <b>C Editor</b>. It contains a working "Hello, World!" program:<p>   <img src="./images/editor_c_helloworld.jpg" alt="C/C++ Editor; Hello World! program">
+   </p></li>
+</ol>
+
+
+<h1><a name="building">Building projects (<tt>make</tt>)</a></h1>
+
+<p>Once you've created your project, you can build it. The IDE uses the same <tt>make</tt> utility and makefiles used on the command line. The IDE can perform makes automatically or let you do them manually. When you do manual builds, you can also decide on the scope of the build.</p>
+<p>
+
+You can watch the progress and see the build information in the <b>C-Build</b> view. If building your programs generates any errors or warnings, you can see them in the <b>Tasks</b> view.</p>
+<p>This section includes:</p>
+<ul>
+<li><a href="#make_terminology">Build terminology</a>
+   </li>
+<li><a href="#make_choosing">Choosing autobuild or manual build</a>
+   </li>
+<li><a href="#make_auto">Autobuilds</a>
+   </li>
+<li><a href="#make_manual">Manual builds</a>
+   </li>
+<li><a href="#make_configuring">Configuring the project build order</a>
+   </li>
+<li><a href="#make_personaloptions">Creating personal build options (<tt>make</tt> targets)</a></li>
+</ul>
+
+<h2><a name="make_terminology">Build terminology</a></h2>
+
+<p>The IDE uses a number of terms to describe the scope of the build:
+
+</p>
+<dl>
+
+<dt><b>Build</b>
+	</dt>
+<dd>Build only the components affected by modified files in that particular project (i.e. <tt>make all</tt>).
+	</dd>
+<dt><b>Clean</b>
+	</dt>
+<dd>	Delete all the built components (i.e. <tt>.o</tt>, <tt>.so</tt>, <tt>.exe</tt>, and so on) without building anything (i.e. <tt>make clean</tt>).
+	</dd>
+<dt><b>Rebuild</b>
+	</dt>
+<dd>Build every component from scratch. A <b>Rebuild</b> is really a <b>Clean</b> followed by a <b>Build</b> (i.e. <tt>make clean; make all</tt>).
+
+</dd>
+</dl>
+
+
+<h2><a name="make_choosing">Choosing autobuild or manual build</a></h2>
+
+<p>By default, the IDE automatically rebuilds every time you change a resource (e.g. file). This is handy if you have only a few open projects and if they're small. As the projects get larger, this feature can become a bit of a hindrance. You may find that you prefer to turn autobuilding off.</p>
+<p>
+
+To turn off autobuilding:</p>
+<ol>
+
+<li>From the main menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>Workbench</b>.
+   The dialog displays your workbench preferences:<p>   <img src="./images/window_preferences_workbench.jpg" alt="Window; Preferences; Workbench">
+   </p></li>
+<li>In the right pane, disable the <b>Perform build automatically on resource modification</b> option. The IDE now builds only when you ask it to.
+
+</li>
+</ol>
+
+
+<h2><a name="make_auto">Autobuilds</a></h2>
+
+<p>
+
+The IDE builds automatically every time you save a change. Thus, if you're using the default IDE configuration, you don't need to do anything. Even in this setting, you can build manually as well. Because the IDE always does incremental builds while in autobuild mode, you may wish to manually do a clean build to ensure you have fresh executables.</p>
+
+<h2><a name="make_manual">Manual builds</a></h2>
+
+<p>Manual builds let you  choose the scope of the build, as well as whether to do a <b>Build</b>, a <b>Clean</b>, or a <b>Rebuild</b>.</p>
+
+<h3><a name="id21">Building everything</a></h3>
+
+<p>The IDE lets you manually choose to rebuild all your open projects. Depending on the number of projects, the size of the projects, and the number of target architectures, this can take a significant amount of time.</p>
+<p>
+
+To rebuild all your open projects:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>From the main menu, select <b>Project</b>--><b>Rebuild All</b>.</td></tr>
+</table>
+
+
+
+<h3><a name="id23">Building selected projects</a></h3>
+
+<p>Because rebuilding all your open projects may be time-consuming, you may often wish to build only certain projects individually.</p>
+<p>
+
+To rebuild a single project:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>C/C++ Projects</b> view, right-click a project and select one of:
+<ul>
+<li><b>Build</b>
+   </li>
+<li><b>Rebuild</b>
+   </li>
+<li><b>Clean</b>.</li>
+</ul>
+<p>The IDE builds the selected project as you desired. For more information on the build methods, see the <a href="#make_terminology">"Build terminology"</a> section in this chapter.</p><p><img src="./images/view_cprojects_building.jpg" alt="C/C++ Projects view; building"></p></td></tr>
+</table>
+
+
+
+<h3><a name="id25">Manual build preferences</a></h3>
+
+<p>To have the IDE save your unsaved resources before manual builds:</p>
+<ol>
+
+<li>From the main menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>Workbench</b>.
+   </li>
+<li>In the right  pane, enable the <b>Save all modified resources automatically prior to manual build</b> option. 
+   The IDE saves your resources before it builds.</li>
+</ol>
+
+
+<h2><a name="make_configuring">Configuring project build order</a></h2>
+
+<p>The IDE lets you determine the build order of your projects. If certain projects must be built before others, you can set that. If your project refers to another project, the IDE builds that project first.
+
+</p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>Setting the build order doesn't cause the IDE to rebuild projects that depend on the project; you must rebuild all projects to ensure all the changes are propagated.</td></tr>
+</table>
+<hr>
+
+
+<p>
+
+To manually configure the project build order:</p>
+<ol>
+
+<li>From the main menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>Build Order</b>.
+   </li>
+<li>Disable the <b>Use default build order</b> option.
+   You may now configure the build order as you desire. When you're done, click <b>Apply</b>, then <b>OK</b>.</li>
+</ol>
+
+
+<h2><a name="make_personaloptions">Creating personal build options (<tt>make</tt> targets)</a></h2>
+
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>In this subsection, "targets" refer to actions in the makefiles, not target machines.</td></tr>
+</table>
+<hr>
+
+
+<p>A <tt>make</tt> <i>target</i> is an action called by the <tt>make</tt> utility to perform a customized build-related task. For example, many makefiles support a target named <tt><b>clean</b></tt>, which gets called as <tt>make clean</tt>. The IDE lets you call your own target such as <tt><b><i>myMakeAction</i></b></tt> to be called as <tt>make <i>myMakeAction</i></tt>. You can also use a <tt>make</tt> target to pass options such as <tt><b>CPULIST=x86</b></tt>, which causes the <tt>make</tt> utility to build only for x86. Of course, these options work only if they're already defined in the makefile. </p>
+<p>
+
+If you've added your own <tt>make</tt> targets, you can configure the IDE to call them specifically. </p>
+<p>
+
+To add a customized <tt>make</tt> target to the <b>C/C++ Project</b> view right-click menu:</p>
+<ol>
+
+<li>In the <b>C/C++ Projects</b> view, right-click a project and select <b>Add Make Targets</b>.
+   </li>
+<li>Type the name of the <tt>make</tt> target (e.g. <tt>myMakeOption</tt>):
+   <p><img src="./images/view_cprojects_target_add.jpg" alt="C/C++ Projects view; Targets Dialog dialog">   </p></li>
+<li>Click <b>OK</b>.
+   The target option appears in the right-click menu of the <b>C/C++ Projects</b> view.</li>
+</ol>
+
+<p>
+
+To use a customized <tt>make</tt> target:</p>
+<ol>
+
+<li>In the <b>C/C++ Projects</b> view, right-click a project. The right-click context menu appears. If there are any customized <tt>make</tt> targets for your project, the <b>Make</b> item is selectable.
+   </li>
+<li>Choose your make target from the <b>Make</b> menu:
+   <p>   <img src="./images/view_cprojects_target_use.jpg" alt="C/C++ Projects view; make target; using"></p></li>
+</ol>
+
+
+<h1><a name="running">Running projects (launcher)</a></h1>
+<H3>
+@@@ Again the same thing applies here about stripping out the QNX
+specific information (ie regarding needing a target for launch) and
+replacing it with generic CDT information.  I've much of it in for
+context.
+</H3>
+<p>
+
+Once you've built your project, you'll want to run it. The IDE lets you 
+run or debug your executables on either a local or a remote QNX Neutrino 
+target machine. For a description of local and remote targets, see the 
+<a href="conc.html">IDE Concepts</a> chapter. </p>
+<p>
+
+To run or debug your program, you must create a <b>QNX Target System Project</b> 
+that specifies how the IDE communicates with your target. You must also create 
+a <b>Launch Configuration</b> that describes how the program runs on your target. 
+</p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>For a complete description of the <b>Launch Configurations</b> dialog and the available options, see the <a href="lnch.html">Starting Your Programs</a> chapter.</p></td></tr>
+</table>
+<hr>
+
+To run your "Hello World!" <b>QNX C Application Project</b>:</p>
+<ol>
+
+<li>In the <b>C/C++ Projects</b> view, select your project (e.g. <b><i>myHelloWorldProject</i></b>).
+   </li>
+<li>In the <b>C/C++ Development</b> perspective, click the dropdown menu <img src="./images/icon_menu.gif" alt="Icon: Menu dropdown"> part of the run menu button set <img src="./images/icon_run_exc.gif" alt="Icon: Run"><img src="./images/icon_menu.gif" alt="Icon: Menu dropdown">.
+   </li>
+<li>Select <b>Run</b>.
+  The <b>Launch Configurations</b> dialog appears:<p>  <img src="./images/lnch.jpg" alt="Launcher">
+   </p></li>
+<li>In the left pane, select <b>C/C++ QNX QConn (IP)</b>.
+   </li>
+<li>Click <b>New</b>.
+	The dialog displays the appropriate tabs:<p>   <img src="./images/lnch_main.jpg" alt="Launcher; Main tab">
+   </p></li>
+<li>In the <b>Name</b> field, type a meaningful name for your launch configuration (e.g. <tt>myHelloProject IP launch</tt>).
+ The IDE automatically fills in the <b>Project</b> field.
+   </li>
+<li>Click the <b>Search</b> button beside the <b>C/C++ Application field</b>.
+   The <b>Program Selection</b> dialog appears. 
+	
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>If the <b>Program Selection</b> dialog is blank, you must cancel and build your project. To learn how to build projects, see the <a href="#building">"Building projects (<tt>make</tt>)"</a> section.
+	</td></tr>
+</table>
+<hr>
+
+
+   </li>
+<li>Select a program to run. The <tt>_g</tt> indicates it's compiled with debug symbols. If you wish to run on an x86 target, select <b>myHelloWorldProject [x86le]</b>
+   </li>
+<li>Click <b>OK</b>.
+   </li>
+<li>In the <b>Target Options</b> pane, select your target.
+   </li>
+<li>Click <b>Run</b>.
+   Your program runs. The IDE displays the output in the <b>Console</b> view. For example:
+   <p>   <img src="./images/view_console_helloworld.jpg" alt="Console view; Hello World!">
+   </p></li>
+</ol>
+
+
+<h1><a name="editor_c">Writing code (C/C++ Editor)</a></h1>
+
+<p>Within the C/C++ Development perspective, the <b>C/C++ Editor</b> is where you'll likely spend the great majority of your time  --  you use it to write and modify your code:</p>
+<p><img src="./images/editor_c.jpg" alt="C/C++ Editor"></p>
+<p>The <b>C/C++ Editor</b> drives many of the other views. As you code, many of the other views update dynamically (even if you haven't saved).</p>
+<p>This section includes:</p>
+<ul>
+<li><a href="#c_editor_layout">C/C++ Editor layout</a>
+   </li>
+<li><a href="#c_editor_contentassist">Finishing function names (Content Assist)</a>
+	</li>
+<li><a href="#c_editor_codetemplates">Inserting code snippets (Code Templates)</a>
+   </li>
+<li><a href="#c_editor_addinclude">Adding <tt>#include</tt> directives (Add include)</a>
+   </li>
+<li><a href="#c_editor_help">Hover help</a>
+   </li>
+<li><a href="#c_editor_codecommenting">Commenting out code</a>
+   </li>
+<li><a href="#c_editor_customizing">Customizing the C/C++ Editor appearance</a>
+   </li>
+<li><a href="#c_editor_alternateeditors">Using other editors</a></li>
+</ul>
+
+<h2><a name="c_editor_layout">C/C++ Editor layout</a></h2>
+
+<p>The <b>C/C++ Editor</b> has a gray border on each side. The border on the <em>left</em> margin might contain icons that flag errors, warnings, or problems detected by the IDE. It also displays icons for any bookmarks, breakpoints, or tasks from the <b>Tasks</b> view. The icons in the left margin correspond to the line of code.</p>
+<p>The border on the <em>right</em> margin displays red and yellow bars that correspond to the errors and warnings from the <b>Tasks</b> view. Unlike the left margin, the right margin displays the icons for the entire length of the file.</p>
+<p>
+
+
+</p>
+
+<h2><a name="c_editor_contentassist">Finishing function names (Content Assist)</a></h2>
+
+<p>The IDE can help you finish the names of functions if they're long, or you can't remember the exact spelling.</p>
+<p>
+
+To use <b>Content Assist</b>:</p>
+<ol>
+
+<li>In the <b>C/C++ Editor</b>, type at least the first letter of the function.
+	</li>
+<li>Press <font face="Helvetica"><b>Ctrl</b></font>-<font face="Helvetica"><b>Space</b></font>. (Or, right-click near the cursor and select <b>Content Assist</b>).
+	A menu with the available functions appears:<p>	<img src="./images/editor_c_contentassist.jpg" alt="C/C++ Editor; Content Assist">
+	</p></li>
+<li>You may do one of the following:
+	<ul>
+<li>Continue typing. The list shortens. When there's only one function that matches, it's automatically inserted.
+		</li>
+<li>Scroll with the up and down arrows. Press <font face="Helvetica"><b>Enter</b></font> to select the function.
+		</li>
+<li>Scroll with the mouse. Double-click a function to select it.
+		</li>
+<li>Press <font face="Helvetica"><b>Esc</b></font> to close the <b>Content Assist</b> window.
+	</li>
+</ul></li>
+</ol>
+
+
+<h2><a name="c_editor_codetemplates">Inserting code snippets (Code Templates)</a></h2>
+
+<p>
+
+The IDE can help you by inserting snippets of code such as an empty <tt>do-while</tt> structure. If you've used the <b>Content Assist</b> feature, you may have already noticed this feature; you access it the same way.</p>
+<p>
+
+To use <b>Code Templates</b>:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>Follow the procedure for using <b>Content Assist</b>, with the following exception:
+<ul>
+<li>If any code templates start with the letter combination you've typed, they appear first in the list and have a different icon:<p>	<img src="./images/editor_c_codetemplates_use.jpg" alt="C/C++ Editor; Code Templates; using"></p></li>
+</ul></td></tr>
+</table>
+
+
+<p>To add <b>Code Templates</b>:</p>
+<ol>
+
+<li>From the main menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>C/C++</b>--><b>Code Templates</b>.
+   </li>
+<li>Click <b>New</b>.
+   A dialog for adding new templates appears. You can view the format of existing templates by selecting them and clicking <b>Edit</b>: <p>   <img src="./images/window_preferences_c_codetemplates.jpg" alt="Window; Preferences; C/C++; Code Templates dialog"></p></li>
+</ol>
+
+
+<h2><a name="c_editor_addinclude">Adding <tt>#include</tt> directives (Add Include)</a></h2>
+
+<p>To insert the <tt>#include</tt> directive for any documented QNX Neutrino function:</p>
+<ol>
+
+<li>In the <b>C/C++ Editor</b>, highlight the entire function name by double-clicking  it. Don't highlight the parentheses or any leading tabs or spaces.
+   </li>
+<li>Right-click and select <b>Add Include</b>.
+   The IDE automatically adds the <tt>#include</tt> statement to the top of the file, if it isn't already there.</li>
+</ol>
+
+
+<h2><a name="c_editor_help">Hover help</a></h2>
+
+<p>The IDE can give you information about functions while you're coding.</p>
+<p>
+
+To use hover help:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>C/C++ Editor</b>, place your pointer over a function.
+A tag appears, showing the function summary and synopsis:<p><img src="./images/editor_c_hoverhelp.jpg" alt="C/C++ Editor; Hover help"></p></td></tr>
+</table>
+
+
+
+<h2><a name="c_editor_codecommenting">Commenting out code</a></h2>
+
+<p>The IDE makes it easy to comment out large sections of code. You can quickly add <tt>//</tt> characters to the beginning of lines, letting you comment out large sections, even if they have <tt>/* */</tt> comments.
+When you uncomment lines, the IDE removes the leading <tt>//</tt> characters from all lines that have them, so be careful not to accidentally uncomment sections. Also, the IDE comments or uncomments the selected lines  --  if you select a partial line, the IDE comments out the entire line, not just the highlighted section of code. </p>
+<p>
+
+To comment or uncomment a block of code:</p>
+<ol>
+
+<li>In the <b>C/C++ Editor</b>, highlight a section of code to be commented or uncommented. For one line,  place your cursor on that line.
+   </li>
+<li>Right-click and select <b>Comment</b> or <b>Uncomment</b>.
+   </li>
+</ol>
+
+
+<h2><a name="c_editor_customizing">Customizing the C/C++ Editor appearance</a></h2>
+
+<p>You can change the font, set the background color, display line numbers, and control many other visual aspects of the C/C++ Editor. You can also configure context highlighting, and change how the <b>Code Assist</b> feature works.
+
+</p>
+<p>To access the <b>C/C++ Editor</b> preferences dialog:</p>
+<ol>
+
+<li>Select <b>Window</b>--><b>Preferences</b>.
+   The <b>Preferences</b> dialog appears.
+   </li>
+<li>In the left pane, select <b>C/C++</b>--><b>C/C++ Editor</b>.</li>
+</ol>
+
+
+<h2><a name="c_editor_alternateeditors">Using other editors</a></h2>
+
+<p>The IDE lets you use other editors, but you should consider the added functionality the <b>C/C++ Editor</b> offers before changing.</p>
+<p>
+
+The <b>C/C++ Editor</b> is highly integrated with the IDE. The other views are designed to support the <b>C/C++ Editor</b> by updating dynamically. Since other editors aren't designed to interface with the IDE, you won't get the support from the views that the IDE provides.</p>
+<p>
+
+You can use other editors either outside or inside the IDE.
+
+</p>
+
+<h3><a name="c_editor_alternateeditors_outside">Outside  the IDE</a></h3>
+
+<p>You can edit your code with an editor started outside of the IDE (e.g. from the command line). When you're done editing, you'll have to synchronize the IDE with the changes.</p>
+<p>
+
+To synchronize the IDE with changes you've made outside of the IDE:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>C/C++ Projects</b> view, right-click the tree pane and select <b>Refresh</b>.
+The IDE updates to reflect any changes you've made (such as creating new files).</td></tr>
+</table>
+
+
+
+<h3><a name="c_editor_alternateeditors_within">Within the IDE</a></h3>
+
+<p>
+
+The IDE lets you set file associations that determine the editor you use for each file type. For example, you can tell the IDE to use an external program such as WordPad to edit all <tt>.h</tt> files. Once that preference is set, you can double-click a file in the <b>C/C++ Projects</b> view, and the IDE automatically opens the file in your selected program.</p>
+<p>
+
+If the IDE doesn't have a set association for a certain file type, it uses the OS defaults. Thus, in Windows, double-clicking on a <tt>.DOC</tt> file automatically opens the file in MS Word or WordPad.</p>
+<p>
+
+For information about file associations, follow these links in the Eclipse <cite>Workbench User Guide</cite>: <b>Reference</b>--><b>Preferences</b>--><b>File Associations</b>.</p>
+<p> </p>
+
+<h1><a name="more">More development features </a></h1>
+
+<p>The IDE has many features that help you work faster. Not all the features are things you'd necessarily think to look for; after you've used the IDE for a while, take some time to read this entire section.</p>
+<p>
+
+This section includes:</p>
+<ul>
+<li><a href="#view_tasks">Tracking remaining work (Tasks view)</a>
+   </li>
+<li><a href="#view_outline">Code synopsis (Outline view)</a>
+   </li>
+<li><a href="#view_cbuild">Checking your build (C-Build view)</a></li>
+</ul>
+
+<h2><a name="view_tasks">Tracking remaining work (Tasks view)</a></h2>
+
+<p>
+
+The <b>Tasks</b> view provides you with a list of errors and warnings related to your projects. These are typically syntax errors, typos, and other programming errors found by the compiler:</p>
+<p><img src="./images/view_tasks.jpg" alt="Tasks view">
+
+</p>
+<p>The <b>Tasks</b> view is part of the core Eclipse platform. For more information about the <b>Tasks</b> view, follow these links in the <cite>Workbench User Guide</cite>: <b>Reference</b>--><b>User interface information</b>--><b>View and Editors</b>--><b>Tasks view</b>.</p>
+<p>
+
+The IDE also shows corresponding markers in several other locations:</p>
+<ul>
+<li><b>C/C++ Projects</b> view: on both the file that contained compile errors and the project
+   </li>
+<li><b>Outline</b> view: in the method (e.g. <i>main()</i>)
+   </li>
+<li><b>C/C++ Editor</b>: on the left side, beside the offending line of code.</li>
+</ul>
+
+<h3><a name="id43">Jumping to errors</a></h3>
+
+<p>To quickly jump to the source of errors (if the IDE can determine where it is):</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>Tasks</b> view, double-click the error marker <img src="./images/icon_error_obj.gif" alt="Icon: Error marker"> or warning marker <img src="./images/icon_warning_obj.gif" alt="Icon: Warning marker">.
+The file opens in the editor area, and the cursor jumps to the offending line.</td></tr>
+</table>
+
+
+<p>
+
+To jump to errors sequentially:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>Click the <b>Jump to next error marker</b> button <img src="./images/icon_next_error_nav.gif" alt="Icon: Jump to next error marker button"> or <b>Jump to previous error marker</b> button <img src="./images/icon_prev_error_nav.gif" alt="Icon: Jump to previous error marker button">.</td></tr>
+</table>
+
+
+
+<h3><a name="id45">Filtering errors</a></h3>
+
+<p>Depending on the complexity and stage of your program, the IDE can generate an overwhelming number of errors. The IDE lets you customize the <b>Tasks</b> view so you see only the errors you want to see.</p>
+<p>
+
+To access the error filtering dialog:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>Tasks</b> view, click the <b>Filter</b> icon <img src="./images/icon_filter_tsk.gif" alt="Icon: Filter button">.
+The <b>Filter Tasks</b> dialog appears and lets you adjust the scope of the errors shown in the <b>Tasks</b> view. To see all errors and warnings, check all the boxes in <b>Show items of type</b> and enable <b>On any resource</b>:<p><img src="./images/view_tasks_filter_tasks.jpg" alt="Tasks view; Filter Tasks dialog"></p></td></tr>
+</table>
+
+
+
+<h3><a name="id47">Setting reminders</a></h3>
+
+<p>The <b>Tasks</b> view lets you create your own tasks. In addition to having the <b>Tasks</b> view automatically list build errors, you can set personal reminders regarding the unfinished function you're writing, the error handling routine you want to check, or <em>anything</em> else.</p>
+<p>
+
+To access the <b>New Tasks</b> dialog to add a personal task:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>Tasks</b> view, right-click the tasks pane and select <b>New Task</b>.
+A <b>New Tasks</b> dialog appears:<p><img src="./images/view_tasks_new_tasks.jpg" alt="Tasks view; New Tasks dialog"></p></td></tr>
+</table>
+
+
+<p>To remove a personal task:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>Tasks</b> view, right-click the task and select one of <b>Delete</b> or <b>Mark Completed</b>.</td></tr>
+</table>
+
+
+
+<h2><a name="view_outline">Code synopsis (Outline view)</a></h2>
+
+<p>
+
+The <b>Outline</b> view gives you a structural view of your C/C++ source code:</p>
+<p><img src="./images/view_outline.jpg" alt="Outline view"></p>
+<p> It shows the elements in the source file in the order they occur, including functions, libraries, and variables. You may also sort the list alphabetically. If you double-click an entry in the <b>Outline</b> view, the <b>C/C++ Editor</b> moves the cursor to the start of the item selected. (For example, to jump to the start of <i>main()</i> in the <b>C/C++ Editor</b>, double-click <i>main()</i> in the <b>Outline</b> view.)</p>
+
+<h2><a name="view_cbuild">Checking your build (C-Build view)</a></h2>
+
+<p>
+
+The IDE displays the output from the <tt>make</tt> utility in the <b>C-Build</b> view:</p>
+<p><img src="./images/view_cbuild.jpg" alt="C-Build view">
+
+</p>
+
+<h3><a name="id51">Customizing the C-Build view</a></h3>
+
+<p>You can choose to clear the <b>C-Build</b> view before each new build or let the results of each subsequent build to append to the display. You can have the <b>C-Build</b> view brought to the top when you build. </p>
+<p>
+
+To access the <b>C-Build</b> view configurations:</p>
+<ol>
+
+<li>From the main menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>C/C++</b>:<p>  <img src="./images/view_cbuild_configurations.jpg" alt="C-Build view; configurations"></p></li>
+</ol>
+
+
+
+</body>
+
+</html>
+
+<!--
+/**********************************************************************
+ * Copyright (c) 2002,2003 QNX Software Systems Ltd. and others.
+ * All rights reserved.   This program and the accompanying materials
+ * are made available under the terms of the Common Public License v0.5
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v05.html
+ * 
+ * Contributors: 
+ * QNX Software Systems - Initial API and implementation
+***********************************************************************/
+-->
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/conc.html b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/conc.html
new file mode 100644
index 00000000000..915c47f13f1
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/conc.html
@@ -0,0 +1,273 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.ord/TR/html4/loose.dtd">
+<html>
+
+<head>
+
+<title>IDE Concepts</title>
+
+</head>
+<body bgcolor="#ffffff" text="#000000">
+<hr>
+
+
+<h1><a name="id1">IDE Concepts</a></h1>
+
+
+
+
+
+<p>
+
+This chapter introduces a number of terms and concepts that are used throughout this 
+guide and the core Eclipse documentation.</p>
+<p>Related information:</p>
+<ul>
+<li>the <cite>Workbench User Guide</cite>: <b>Concepts</b> in the Eclipse documentation</li>
+</ul>
+<p></p>
+In this chapter:
+<ul>
+<li><a href="#work">Workbench</a>
+	</li>
+<li><a href="#pers">Perspectives</a>
+	</li>
+<li><a href="#edit">Editors and views</a>
+	</li>
+<li><a href="#proj">Projects and workspace</a>
+	</li>
+<li><a href="#host">Host and target machines</a>
+	</li>
+<li><a href="#targ">Target agent and the <tt>qconn</tt> daemon</a>
+	</li>
+<li><a href="#laun">Launcher</a>
+	</li>
+<li><a href="#reso">Resources</a>
+	</li>
+<li><a href="#wiza">Wizards</a></li>
+</ul>
+
+<h1><a name="work">Workbench</a></h1>
+
+<p>The <i>workbench</i> is the window that appears when you run the IDE. It includes:</p>
+<ul>
+<li>views
+   </li>
+<li>editors
+   </li>
+<li>the main menu
+   </li>
+<li>the control bars.</li>
+</ul>
+<p></p>
+<p></p>
+
+<hr>
+<p><img src="./images/first_look.jpg" alt="IDE Concepts; workbench with C/C++ Development perspective"></p>
+<hr>
+
+
+<p><i>Major components of the IDE workbench.</i></p>
+<pre>
+
+</pre>
+
+
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>Eclipse is written in JAVA and is interpreted by a Java Virtual Machine (JVM) 
+that's specific to the host OS. So, whether you run Eclipse on Windows, 
+QNX Neutrino, or Solaris, you're running the same code. However, you might 
+notice some differences in the user interface.</td></tr>
+</table>
+<hr>
+
+
+<p>The CDT provides a graphical development environment for C and C++
+developers.  The CDT works in a complimentary manner with many of the
+same tools that you use on the command line. The CDT communicates with 
+and interprets messages from many utilities, including:</p>
+<ul>
+<li><tt>make</tt></a> 
+(which drives compilers such as <tt>gcc</tt></a>)
+   </li>
+<li><tt>gdb</tt></a>
+   </li>
+<li><tt>ctags</tt></a></li>
+</ul>
+
+
+</p>
+
+<h1><a name="pers">Perspectives</a></h1>
+
+<p>A <i>perspective</i> is a task-oriented configuration of the workbench window.</p>
+<p>
+
+For example, if you're debugging, you use the preconfigured <b>Debug</b> 
+perspective. This perspective sets up the IDE to show all the tools related to 
+debugging, but doesn't show the elements and tools related to profiling, for example.
+You can customize a perspective by adding and removing views.<p>
+
+Perspectives generally consist of these components:</p>
+<ul>
+<li>toolbars
+   </li>
+<li>editors
+   </li>
+<li>views</li>
+</ul>
+
+<h1><a name="edit">Editors and views</a></h1>
+
+<p>
+
+<i>Editors</i> are what you use to change the content of your files. Each editor 
+in the IDE is for a specific set of files. The editor that you'll likely use 
+the most for C and C++ development is the <b>C/C++ Editor</b>.</p>
+<p>
+
+<i>Views</i> take information and organize it in various convenient ways. 
+For example, the <b>Outline</b> view shows you a list of all the function 
+names when you're editing a C file in the <b>C/C++ Editor</b>. 
+The <b>Outline</b> view is dynamic; if you declare a function called <i>mynewfunc()</i>, the <b>Outline</b> view immediately lists it, even if you haven't saved the file yet.</p>
+<p>Views provide:</p>
+<ul>
+<li>insight into editor contents (e.g. <b>Outline</b> view)
+   </li>
+<li>navigation (e.g. <b>Navigator</b> view)
+   </li>
+<li>information (e.g. <b>Tasks</b> view)
+   </li>
+<li>control (e.g. <b>Debug</b> view).</li>
+</ul>
+<p></p>
+<p>
+
+Different views may show you different interpretations of the same 
+information. For example, the <b>Navigator</b> view shows all 
+your projects; the <b>C/C++ Projects</b> view shows just the 
+C and C++ projects you have open.</p>
+<p>
+
+The <i>editor area</i> is a section of the workbench window reserved for editors. All the editors live together in the editor area; all the views can be anywhere except in the editor area.</p>
+<p>
+
+The IDE lets you rearrange views and editors so they're beside each other (tiled) or stacked on top of each other (tabbed), among other possibilities.</p>
+<p>
+
+To see how dynamic the interface is, see the <cite>Perspectives, Views, and Editors</cite> movie.
+
+</p>
+
+<h1><a name="proj">Projects and workspace</a></h1>
+
+<p><i>Projects</i> are generic containers for your source code, makefiles, 
+and binaries. Before you do any work in the IDE, you must create projects to 
+store your work. Developers using the CDT will most ofent work with <b>C Project</b>.</p>
+<p>Projects can be open or closed. If they're closed, you can't access them.</p>
+<p>When you create a file within a project, the IDE also creates a record 
+(local history) of every time you changed that file and how you changed it.</p>
+<p>
+
+Your <i>workspace</i> is where you keep your projects. For the exact location of your workspace, see the appendix <a href="file.html">Where Files Are Stored</a>.</p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>Don't use spaces in projects and filenames; they can cause problems with some tools, such as the <tt>make</tt> utility.
+<p>Also, don't use case alone to distinguish files and projects; Unix-based OS filenames are case-sensitive, but Windows filenames aren't. Thus, <tt>Hello.c</tt> and <tt>hello.c</tt> overwrite each other in Windows, but are separate files elsewhere. </p></td></tr>
+</table>
+<hr>
+
+
+
+<h2><a name="id7">How the IDE looks at projects</a></h2>
+
+<p>The IDE associates projects with <i>natures</i>, tags that tell the IDE about the properties of each project. 
+
+</p>
+<p>The IDE doesn't support nested projects; each project must be organized as a discrete entity. The IDE does support project dependencies by allowing a project to reference other projects that reside in your workspace. </p>
+<p>
+
+The most common projects look like this to the IDE:</p>
+<table border=1 width="100%">
+
+<tr>
+<th>Project		</th>
+<th>Associated natures</th>
+</tr>
+<tr>
+<td><b>Simple Project</b>	</td>
+<td>&nbsp;</td>
+</tr>
+<tr>
+<td><b>Standard Make C Application Project</b>	 	</td>
+<td>C</td>
+</tr>
+<tr>
+<td><b>Standard Make C++ Application Project</b>	 	</td>
+<td>C, C++</td>
+</tr>
+</table>
+
+<p>The natures tell the IDE what can and can't be done with each project. The IDE also uses the natures to filter out projects that would be contextually irrelevant (e.g. nonlibrary projects from a list of library projects).</p>
+<p>
+
+In this guide, you'll see mixed references such as:</p>
+<ul>
+<li><b>QNX C/C++ Applications</b>  --  refers to both <b>QNX C Application Projects</b> and <b>QNX C++ Application Projects</b>.
+	</li>
+<li><b>QNX Library Projects</b>  --  refers to both <b>QNX C Library Projects</b> and <b>QNX C++ Library Projects</b>.</li>
+</ul>
+<p>The IDE saves these natures and other information in <tt>.project</tt> and <tt>.cdtproject</tt> files in each project. To ensure the natures persist in CVS, include these files when you commit your project.
+
+
+
+</p>
+
+<h1><a name="laun">Launcher</a></h1>
+
+<p>Before you run any program, you must use the launcher to specify what 
+program to run, what arguments to pass to the program, and so on. </p>
+<p>
+
+If you want to run the program with different you can either modify
+an existing launch configuration or create a new <b>Launch Configuration</b>. 
+Once you save the <b>Launch Configuration</b>, you can quickly rerun 
+each configuration.
+
+</p>
+
+<h1><a name="reso">Resources</a></h1>
+
+<p><i>Resources</i> is a collective term for projects, folders, and files that exist in the workbench. You store all your resources in your workspace.</p>
+
+<h1><a name="wiza">Wizards</a></h1>
+
+<p><i>Wizards</i> guide you through a sequenced set of tasks. For example, to create a <b>QNX C Application Project</b>, you run a wizard that takes you through all the steps and gathers all the necessary information before creating the project. For more information, see the <a href="cwiz.html">Common Wizards</a> chapter.</p>
+<p>
+
+
+
+</p>
+
+
+</body>
+
+</html>
+
+<!--
+/**********************************************************************
+ * Copyright (c) 2002,2003 QNX Software Systems Ltd. and others.
+ * All rights reserved.   This program and the accompanying materials
+ * are made available under the terms of the Common Public License v0.5
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v05.html
+ * 
+ * Contributors: 
+ * QNX Software Systems - Initial API and implementation
+***********************************************************************/
+-->
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cvs.html b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cvs.html
new file mode 100644
index 00000000000..3e63d6c5726
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cvs.html
@@ -0,0 +1,130 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.ord/TR/html4/loose.dtd">
+<html>
+
+<head>
+
+<title>Source Control</title>
+
+</head>
+<body bgcolor="#ffffff" text="#000000">
+<hr>
+
+
+<h1><a name="id1">Source Control</a></h1>
+
+<p> 
+If you use CVS, you can check code in and out without leaving the IDE. </p>
+<p>
+
+Related information:</p>
+<ul>
+<li>the <cite>Source Control</cite> movie (recommended)
+   </li>
+<li>the following links in the Eclipse <cite>Workbench User Guide</cite>: <b>Tasks</b>--><b>Working in the team environment</b>--><b>Working with a CVS repository</b> (recommended)
+   </li>
+</ul>
+<p>Suggested prior reading:</p>
+<ul>
+<li>the <a href="conc.html">IDE Concepts</a> chapter</li>
+</ul>
+<p></p>
+In this chapter:
+<ul>
+<li><a href="#how">Introduction</a></li>
+</ul>
+
+<h1><a name="how">Introduction</a></h1>
+
+<p>The <b>CVS Repository Exploring</b> perspective lets you bring code from CVS into your workspace. 
+While you're working on your code, the IDE automatically keeps track of the changes you make; it lets you roll back to an earlier version of a file that you saved but didn't commit to CVS. If another developer changes the source in CVS while you're working on it, the IDE helps you synchronize with CVS and resolve any conflicts. Finally, the <b>CVS Repository Exploring</b> perspective lets you check the modified code back into CVS.</p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>The IDE stores project information in <tt>.project</tt> and <tt>.cdtproject</tt> 
+files; you must include them with your project when you commit it to CVS. Otherwise, 
+you must manually set the nature of the project (e.g. <b>Standard C Project</b>). 
+For more information about setting project natures, see the <a href="cwiz.html">Common 
+Wizards</a> chapter.</td></tr>
+</table>
+<hr>
+
+
+<p>Unlike many other components of the IDE, the <b>CVS Repository Exploring</b> perspective <em>doesn't</em> connect to a utility. Instead of connecting via the <tt>cvs</tt> utility, the IDE uses its own engine to connect directly to your CVS repository.
+
+</p>
+<p>Because the <b>CVS Repository Exploring</b> perspective is a core Eclipse feature, we've covered the perspective only lightly in this book. For more information, follow these links the Eclipse <cite>Workbench User Guide</cite>: <b>Tasks</b>--><b>Working in the team environment</b>.</p>
+<p></p>
+
+<p>This table may help you find information more easily:</p>
+<table border=1 width="100%">
+
+<tr>
+<th>If you want to:
+	</th>
+<th>See:</th>
+</tr>
+<tr>
+<td>Connect to a CVS repository
+	</td>
+<td><b>Tasks</b>--><b>Working in the team environment</b>--><b>Working with a CVS repository</b>--><b>Creating a CVS repository location</b></td>
+</tr>
+<tr>
+<td>Check code out of a CVS repository
+	</td>
+<td><b>Tasks</b>--><b>Working in the team environment</b>--><b>Working with projects shared with CVS</b>--><b>Checking out a project from a CVS repository</b></td>
+</tr>
+<tr>
+<td>Synchronize with a CVS repository
+	</td>
+<td><b>Tasks</b>--><b>Working in the team environment</b>--><b>Synchronizing with the repository</b>, especially the <b>Updating</b> section</td>
+</tr>
+<tr>
+<td>Resolve CVS conflicts
+	</td>
+<td><b>Tasks</b>--><b>Working in the team environment</b>--><b>Synchronizing with the repository</b>--><b>Resolving conflicts</b>
+	</td>
+</tr>
+<tr>
+<td>Prevent certain files from being committed to CVS
+	</td>
+<td><b>Tasks</b>--><b>Working in the team environment</b>--><b>Synchronizing with the repository</b>--><b>Version control life cycle: adding and ignoring resources</b>
+
+</td>
+</tr>
+<tr>
+<td>Create and apply a patch
+	</td>
+<td><b>Tasks</b>--><b>Working in the team environment</b>--><b>Working with patches</b></td>
+</tr>
+<tr>
+<td>Track code changes that haven't been committed to CVS
+	</td>
+<td><b>Tasks</b>--><b>Working with local history</b>, especially the <b>Comparing resources with the local history</b> section</td>
+</tr>
+<tr>
+<td>View an online FAQ about the <b>CVS Repository Exploring</b> perspective
+	</td>
+<td><b>Reference</b>--><b>Team Support</b>--><b>CVS</b></td>
+</tr>
+</table>
+
+
+
+</body>
+
+</html>
+
+<!--
+/**********************************************************************
+ * Copyright (c) 2002,2003 QNX Software Systems Ltd. and others.
+ * All rights reserved.   This program and the accompanying materials
+ * are made available under the terms of the Common Public License v0.5
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v05.html
+ * 
+ * Contributors: 
+ * QNX Software Systems - Initial API and implementation
+***********************************************************************/
+-->
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cwiz.html b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cwiz.html
new file mode 100644
index 00000000000..cb364e3f12b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/cwiz.html
@@ -0,0 +1,470 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.ord/TR/html4/loose.dtd">
+<html>
+
+<head>
+
+<title>Common Wizards</title>
+
+</head>
+<body bgcolor="#ffffff" text="#000000">
+<hr>
+
+
+<h1><a name="id1">Common Wizards</a></h1>
+
+<p>
+
+ </p>
+<p></p>
+In this chapter:
+<ul>
+<li><a href="#how">Introduction</a>
+   </li>
+<li><a href="#c">Creating a C/C++ Project (New Project wizard)</a>
+   </li>
+<li><a href="#convert">Converting projects (Convert to a QNX Project wizard)</a></li>
+</ul>
+<p></p>
+
+<h1><a name="how">Introduction</a></h1>
+
+<p>Wizards guide you through a sequenced set of tasks. In the IDE, these tasks may 
+be creating something new (e.g. a project) or converting one thing to another 
+(e.g. converting to a Standard C project). Most often, you use wizards to create 
+new projects and folders.</p>
+<p>
+
+Wizards aren't directly connected to any perspective, though you're more likely to call them from some perspectives than from others (most likely from the <b>C/C++ Development</b> perspective).</p>
+<p>You can access all the wizards from the main menu by selecting <b>File</b>--><b>New</b>. The <b>File</b>--><b>New</b>--><b>Project</b> selection filters out all the wizards except projects; <b>File</b>--><b>New</b>--><b>Other</b> doesn't filter anything. (The exception to this is <b>Target System Project</b>, which, while labeled as a project, isn't a project as far as the IDE is concerned.)</p>
+<p>In the <b>New Project</b> dialog, the wizards are further sorted: selecting <b>C</b> in the left pane displays all the projects with a C nature in the IDE; selecting <b>QNX</b> in the left pane shows all the projects with a QNX nature:</p>
+<p><img src="./images/cwiz.jpg" alt="Common wizards dialog"></p>
+<p> Notice the overlap: the <b>QNX C Application Project</b> wizard appears in the right pane for both <b>C</b> and <b>QNX</b>.</p>
+<p>
+
+So-called "simple" wizards show the very basic elements of projects: <b>Project</b>, <b>Folder</b>, and <b>File</b>. These elements have no natures associated with them. You can access the wizards for these by selecting <b>File</b>--><b>New</b>--><b>Other</b>, then selecting <b>Simple</b> from the left pane.</p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td><p>Although projects may appear as directories in your workspace, the IDE attaches special meaning to them. The IDE won't automatically recognize a directory you create in your <tt>workspace</tt> directory as a project.</p><p>
+
+The IDE automatically recognizes directories and new files of any type if you create them outside of the IDE (i.e. using Windows Explorer) and place them in a project directory. To have the IDE recognize them, in the <b>Navigator</b> view, right-click the navigator pane and select <b>Refresh</b>. </p></td></tr>
+</table>
+<hr>
+
+
+
+<h1><a name="c">Creating a C/C++ project (New Project wizard)</a></h1>
+
+<p>The <b>New Project</b> wizard helps you create a C or C++ project.</p>
+<p>This section includes:</p>
+<ul>
+<li><a href="#c_types">Types of projects</a>
+	</li>
+<li><a href="#c_creating">Creating your C/C++ Project (New Projects wizard)</a>
+	</li>
+<li><a href="#c_tabs">New C/C++ Project wizard tabs</a>	</li>
+</ul>
+
+<h2><a name="c_types">Types of projects</a></h2>
+
+<p>The IDE lets you create a variety of projects, each with certain properties. Most of these projects are also subdivided into C or C++ projects:
+
+</p>
+<dl>
+
+<dt><b>Standard Make C Project</b><br><b>Standard Make C++ Project</b>
+	</dt>
+<dd>A basic C or C++ project that uses a standard <tt>makefile</tt> and GNU <tt>make</tt> to build the source files. You don't get the added functionality provided by the QNX build organization and the <tt>common.mk</tt> file. 
+
+</dd>
+</dl>
+
+<h2><a name="c_creating">Creating your C/C++ project (New Projects wizard)</a></h2>
+
+<p>To create a C/C++ project :
+
+</p>
+<ol>
+
+<li>From the menu, select <b>File</b>--><b>New</b>--><b>Project</b>.
+The <b>New</b> dialog appears. Projects are filtered by the natures listed in the left pane.
+    </li>
+<li>In the left pane, select the nature in the table:<p></p><table border=1 width="100%">
+
+<tr>
+<th>If you want to build:
+	</th>
+<th>Select:</th>
+</tr>
+<tr>
+<td><b>Standard Make C Application Project</b>
+	</td>
+<td><b>C</b></td>
+</tr>
+<tr>
+<td><b>QNX C Application Project</b>
+	</td>
+<td><b>C</b> or <b>QNX</b></td>
+</tr>
+<tr>
+<td><b>QNX C Library Project</b>
+	</td>
+<td><b>C</b> or <b>QNX</b></td>
+</tr>
+<tr>
+<td><b>Standard Make C++ Application Project</b>
+	</td>
+<td><b>C++</b></td>
+</tr>
+<tr>
+<td><b>QNX C++ Application Project</b>
+	</td>
+<td><b>C++</b> or <b>QNX</b></td>
+</tr>
+<tr>
+<td><b>QNX C++ Library Project</b>
+	</td>
+<td><b>C++</b> or <b>QNX</b></td>
+</tr>
+</table>
+
+
+    </li>
+<li>In the right pane, select the type of project that you want (e.g. <b>QNX C Application Project</b>).
+    </li>
+<li>Click <b>Next</b>.
+    </li>
+<li>Type a name for your project in the <b>Name</b> field.
+    </li>
+<li>Ensure that <b>Use Default Location</b> is checked. Don't use a different location.
+    </li>
+<li>Click <b>Next</b>.
+	The wizard displays the appropriate tabs.
+    </li>
+<li>Select each tab and fill in the required information. The fields for each tab are described in the <a href="#c_tabs">"New C/C++ Project wizard tabs"</a> section, below.
+    </li>
+<li>Click <b>Finish</b>.
+The IDE creates your new project in your workspace. </li>
+</ol>
+
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>In the <b>C/C++ Development</b> perspective, you can also access the <b>QNX C/C++ Projects</b> with the 
+<img src="./images/icon_newccqnx_lib.gif" alt="Icon: QNX C++ Library Project"> &nbsp;
+<img src="./images/icon_newcqnx_lib.gif" alt="Icon: QNX C Library Project">&nbsp;
+<img src="./images/icon_newccqnx_app.gif" alt="Icon: QNX C++ Application Project">&nbsp;
+<img src="./images/icon_newcqnx_app.gif" alt="Icon: QNX C Application Project">&nbsp;
+ buttons.
+ </td></tr>
+</table>
+<hr>
+
+
+
+<h2><a name="c_tabs">New C/C++ Project wizard tabs</a></h2>
+
+<p>Depending on the type of project you choose, the <b>New Project</b> wizard displays different tabs:
+
+</p>
+<table border=1 width="100%">
+
+<tr>
+<th>Project Type
+	</th>
+<th>Architecture tab,<br>Options tab	
+	</th>
+<th>Projects tab,<br>Build Settings tab	
+	</th>
+<th>Library tab
+
+</th>
+</tr>
+<tr>
+<td><b>Standard Make C Project</b> or<br><b>Standard Make C++ Project</b>
+	</td>
+<td>Yes	
+	</td>
+<td>No
+	</td>
+<td>No
+
+</td>
+</tr>
+<tr>
+<td><b>QNX C Application Project</b> or<br><b>QNX C++ Application Project</b>
+	</td>
+<td>Yes
+	</td>
+<td>Yes	
+	</td>
+<td>No
+
+</td>
+</tr>
+<tr>
+<td><b>QNX C Library Project</b> or<br><b>QNX C++ Library Project</b>
+	</td>
+<td>Yes
+	</td>
+<td>Yes
+	</td>
+<td>Yes
+
+</td>
+</tr>
+</table>
+
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td> You can find the default settings for the <b>New Project</b> wizard by selecting <b>Window</b>--><b>Preferences</b> from the main menu. From the left pane, select <b>C/C++</b>, then <b>New QNX Projects</b>.</td></tr>
+</table>
+<hr>
+
+
+
+<h3><a name="id8">Architecture tab</a></h3>
+
+<p>The <b>Architecture</b> tab lets you choose the platforms to compile executables for:</p>
+<p><img src="./images/cwiz_c_architecture.jpg" alt="Common wizards: C/C++ Projects; Architecture tab"></p>
+<p>For example, to build for a PowerPC platform, enable <b>PPC (Big Endian)</b>.</p>
+<p>
+
+If you've already created a <b>QNX Target System Project</b>, you'll also see entries such as <b>Doug [localhost - x 86]</b>. These let you build specifically for a configured target. If you also enable <b>X86 (Little Endian)</b>, the IDE builds only one executable, not two.</p>
+<p>
+
+You must choose at least one platform.
+
+</p>
+
+<h3><a name="id10">Projects tab</a></h3>
+
+<p>The <b>Projects</b> tab lets you configure your preferred order of building:</p>
+<p><img src="./images/cwiz_c_projects.jpg" alt="Common wizards: C/C++ Projects; Projects tab"></p>
+<p>For example, if you associate <i>myProject</i> with <i>mySubProject</i>, the IDE builds <i>mySubProject</i> first during rebuilds. If you change <i>mySubProject</i>, the IDE doesn't automatically rebuild <i>myProject</i>.
+
+
+</p>
+
+<h3><a name="id12">Build Settings tab</a></h3>
+
+<p>The <b>Build Settings</b> tab lets you configure how the IDE handles <tt>make</tt> errors and what command to use to build your project:</p>
+<p><img src="./images/cwiz_c_buildsettings.jpg" alt="Common wizards: C/C++ Projects; Build Settings tab ">
+
+
+</p>
+<dl>
+
+<dt><b>Build Settings</b></dt>
+<dd>If you want the IDE to stop building when it encounters a <tt>make</tt> error, enable <b>Stop on Error</b>. Otherwise, enable <b>Keep Going On Error</b>.
+
+</dd>
+<dt><b>Build Command</b></dt>
+<dd>If you want the IDE to use the default <tt>make</tt> command, enable <b>Use Default</b>. If you want to use a different utility to build your project, disable <b>Use Default</b> and enter your own command in the <b>Build Command</b> field (e.g. <tt>C:\<i>myCustomizedMakeProgram</i></tt>).
+
+</dd>
+</dl>
+
+
+<h3><a name="id14">Options tab</a></h3>
+
+<p>The <b>Options</b> tab lets you choose what type of executables the IDE builds:</p>
+<p><img src="./images/cwiz_c_options.jpg" alt="Common wizards: C/C++ Projects; Options tab">
+
+</p>
+<dl>
+
+<dt><b>Build Type</b></dt>
+<dd>To build a regular executable, enable <b>Build release version</b>. To build a debuggable executable, enable <b>Build debug version</b> (debug versions have <tt>_g</tt> appended to their filename).
+<p>
+
+You must select at least one build type.
+
+
+</p></dd>
+<dt><b>Build Options</b></dt>
+<dd>To fully enable profiling with the <b>QNX Application Profiler</b> perspective, enable <b>Build with Profiling</b>. The IDE adds profiling code to all the versions selected in <b>Build Types</b>. See the <a href="prof.html">Profiling Your Application</a> chapter.</dd>
+</dl>
+
+
+<h3><a name="id16">Library tab</a></h3>
+
+<p>The <b>Library</b> tab lets you choose the type of library you wish to build (e.g. <b>Static library</b>, <b>Shared library</b>):</p>
+<p><img src="./images/cwiz_c_library.jpg" alt="Common wizards: C/C++ Projects; Library tab"></p>
+<dl>
+
+<dt>Static library (<tt>libxx.a</tt>)
+	</dt>
+<dd>Combine binary object files (i.e. <tt>*.o</tt>) into an archive that will later be directly linked into an executable.
+
+	</dd>
+<dt>Shared library (<tt>libxx.so</tt>)
+	</dt>
+<dd>Combine binary objects together and join them so they are relocatable and can be shared by many processes. Shared libraries are named using the format <tt>libxx.so.</tt><i>version</i>, where <i>version</i> is a number with a default of 1. The <tt>libxx.so</tt> file symlinks to the latest version.
+	
+	</dd>
+<dt>Static library for shared objects (<tt>libxxS.a</tt>)
+	</dt>
+<dd>Same as static library, but using position-independent code (PIC). Use this for a library that will later be linked into a shared object. The System Builder uses these types of libraries to create new shared libraries that contain only the symbols that are absolutely required by a specific set of programs.
+		
+	</dd>
+<dt>Shared library without export (<tt>xx.so</tt>)
+	</dt>
+<dd>A shared library without versioning. Generally, you manually open the library with the <a href="../../neutrino/lib_ref/d/dlopen.html"><i>dlopen()</i></a> function and look up specific functions with the <a href="../../neutrino/lib_ref/d/dlsym.html"><i>dlsym()</i></a> function.</dd>
+</dl>
+
+<p>You must choose one of the options.
+
+
+ </p>
+
+<h1><a name="target">Creating a target (New Target System Project wizard)</a></h1>
+
+<p>You must create a <b>Target System Project</b> for every target you have. When you create a launch configuration, you have the option of adding a new target from within the <b>Launch Configurations</b> dialog. When you do, the IDE opens up the <b>New Target System Project</b> wizard.</p>
+<p>
+
+To create a new target:</p>
+<ol>
+
+<li>From the menu, select <b>File</b>--><b>New</b>--><b>Other</b>.
+   </li>
+<li>In the left pane, select <b>QNX</b>.
+   </li>
+<li>In the right pane, select <b>QNX Target System Project</b>.
+   </li>
+<li>Click <b>Next</b>.
+   The <b>New QNX Target System Project</b> wizard appears:<p> 
+   <img src="./images/cwiz_target.jpg" alt="Common wizards: New Target System Project">
+   </p></li>
+<li>Fill in the fields described below:
+   <dl>
+
+<dt><b>Target Name</b>
+		</dt>
+<dd>Type a descriptive name for your <b>QNX Target System Project</b>.
+
+		</dd>
+<dt><b>Project contents</b>
+		</dt>
+<dd>Enable <b>Use default</b> to store it in your workspace, or disable it and select another location in the <b>Directory</b> field.
+
+		</dd>
+<dt><b>QNX Connector Selection</b>
+		</dt>
+<dd>Type the target connection in the <b>Hostname or IP</b> and <b>Port</b> fields. If you're running the IDE on a QNX Neutrino machine running <tt>qconn</tt>, make sure <b>Use local QNX Connector</b> is enabled; the IDE automatically fills in the connection information. (If you wish to connect to a different target, you may disable <b>Use local QNX Connector</b> and fill in the fields manually.)
+
+		</dd>
+<dt><b>Target Configuration</b>
+		</dt>
+<dd>This section is for a future feature.
+	</dd>
+</dl>
+
+
+   
+   </li>
+<li>Click <b>Finish</b>.
+   Your new <b>QNX Target System Project</b> appears in the <b>Navigator</b> view. When you create a <b>Launch Configuration</b>, the target is listed under the <b>Main</b> tab in the <b>Target Options</b> pane. 
+
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>You can also reach the <b>New Target System Project</b> wizard by right-clicking in the <b>Target Options</b> pane and selecting <b>Add target</b>.</td></tr>
+</table>
+<hr>
+
+
+   </li>
+</ol>
+
+
+<h1><a name="convert">Converting projects (Convert to a QNX Project wizard)</a></h1>
+
+<p>At various times, you may want to convert projects to give them a QNX nature. For example:</p>
+<ul>
+<li>if other developers committed a project to CVS without the <tt>.project</tt> and <tt>.cdtproject</tt> files, the IDE won't recognize the project as a <b>QNX</b> project when you get it from CVS
+   </li>
+<li>you wish to turn a <b>Standard Make C/C++ Project</b> into a <b>QNX C/C++ Application Project</b>.</li>
+</ul>
+<p>The QNX nature causes the IDE to use QNX <tt>make</tt> tools and the QNX <tt>make</tt> structure when building them.</p>
+<p></p>
+<p>The IDE lets you convert many projects in the same step, but the projects are all converted into projects of the same type.</p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>If you wish to convert a <b>QNX Project</b> back into a <b>Standard Make C/C++ Project</b>, you can use the <b>Convert C/C++ Projects</b> wizard. From the main menu, select <b>File</b>--><b>New</b>--><b>Project</b>. In the left pane, select <b>C</b>. In the right pane, select <b>Convert to a C or C++ Project</b>.</td></tr>
+</table>
+<hr>
+
+
+<p>
+
+To convert to a <b>QNX Project</b>:</p>
+<ol>
+
+<li>From the menu, select <b>File</b>--><b>New</b>--><b>Project</b>.
+   </li>
+<li>In the left pane, select <b>QNX</b>.
+   </li>
+<li>In the right pane, select <b>Convert to a QNX Project</b>:<p>	<img src="./images/cwiz_convert_1.jpg" alt="Common wizards: Convert to a QNX Project; selecting wizard">
+   </p></li>
+<li>Click <b>Next</b>.
+   </li>
+<li>Fill in the fields described below:
+   
+   <p>The fields let you to convert a selection of projects to one of the following types of projects:</p><ul>
+<li><b>QNX C Application Project</b>
+   </li>
+<li><b>QNX C Library Project</b>
+   </li>
+<li><b>QNX C++ Application Project</b>
+   </li>
+<li><b>QNX C++ Library Project</b></li>
+</ul>
+
+<dl>
+
+<dt><b>Candidates for conversion</b></dt>
+<dd>The IDE lists all the projects that can be converted. Check off all the projects you wish to convert.
+
+</dd>
+<dt><b>Convert to C or C++</b></dt>
+<dd>Select whether your projects are C or C++.
+
+</dd>
+<dt><b>Convert to QNX project type</b></dt>
+<dd>Select <b>QNX Application Project</b> or <b>QNX Library Project</b>, depending on whether or not your projects are applications or libraries.</dd>
+</dl>
+
+
+   
+   </li>
+<li>Click <b>Finish</b>.</li>
+</ol>
+
+
+
+</body>
+
+</html>
+
+<!--
+/**********************************************************************
+ * Copyright (c) 2002,2003 QNX Software Systems Ltd. and others.
+ * All rights reserved.   This program and the accompanying materials
+ * are made available under the terms of the Common Public License v0.5
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v05.html
+ * 
+ * Contributors: 
+ * QNX Software Systems - Initial API and implementation
+***********************************************************************/
+-->
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/dbug.html b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/dbug.html
new file mode 100644
index 00000000000..5d3a166c0e9
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/dbug.html
@@ -0,0 +1,942 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.ord/TR/html4/loose.dtd">
+<html>
+
+<head>
+
+<title>Debugging Programs</title>
+
+</head>
+<body bgcolor="#ffffff" text="#000000">
+<hr>
+
+
+<h1><a name="id1">Debugging Programs</a></h1>
+
+<p>
+
+Once you've written your program, you might need to debug it. The IDE debugger lets you detect and diagnose errors in your programs,  whether they're running locally or remotely.</p>
+<p>Suggested prior reading: </p>
+<ul>
+<li>the <a href="cdev.html">Developing C/C++ Programs</a> chapter</li>
+</ul>
+<p>Related information:</p>
+<ul>
+<li><tt>gdb</tt></a> utility 
+	</li>
+</ul>
+<p> </p>
+In this chapter:
+<ul>
+<li><a href="#how">Introduction</a>
+   </li>
+<li><a href="#debug">Debugging your program</a>
+   </li>
+<li><a href="#control">Controlling your debug session (Debug view)</a>
+   </li>
+<li><a href="#more">More debugging features</a></li>
+</ul>
+
+<h1><a name="how">Introduction</a></h1>
+
+<p>The debugger lets you see what's going on "inside" a program while it executes, and what it was doing at the moment it crashed or misbehaved.</p>
+<p>
+
+In order to use the full power of the <b>Debug</b> perspective, 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 that original source. The debuggable executables have <tt>_g</tt> appended to their filenames. </p>
+<p>
+
+The IDE debugger uses GDB as the underlying debug engine. It translates each GUI action into a sequence of GDB commands and processes the output from GDB to display the current state of the program being debugged. </p>
+<p>
+
+The views update only when the program is suspended.</p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>Editing the source after compiling causes the line numbering to be out of step because the debug information is tied directly to the source.
+Similarly, debugging optimized binaries can also cause unexpected jumps in the execution trace.</td></tr>
+</table>
+<hr>
+
+
+
+<h1><a name="debug">Debugging your program</a></h1>
+
+<p>To debug a program, you must build an executable and launch the debugging session. Once you've launched your debugging session, you'll want to control the session.</p>
+
+<h2><a name="id5">Building a debuggable executable</a></h2>
+
+<p>Although you can debug a regular executable, you get far more control by building debug variants of the executables. When you created your project, you may have already set the option to make the IDE build one. If so, you should have debuggable executables with <tt>_g</tt> appended to the filename. If not, you must set the IDE to build debug variants:</p>
+<ol>
+
+<li>In the <b>C/C++ Projects</b> view (or the <b>Navigator</b> view), right-click the project and select <b>Properties</b>.
+   </li>
+<li>In the left pane, select <b>QNX C/C++ Project</b>.
+   </li>
+<li>In the right pane, select the <b>Options</b> tab.
+   </li>
+<li>Under <b>Build Type</b>, ensure <b>Build debug version</b> is enabled:<p>   <img src="./images/persp_dbug_properties_options.jpg" alt="Properties dialog; options tab">
+   </p></li>
+<li>Click <b>Apply</b>.
+   </li>
+<li>Click <b>OK</b>.
+   </li>
+<li>If it's not done automatically, rebuild the project.</li>
+</ol>
+
+<p>For more information about setting project options, see the <a href="cwiz.html">Common Wizards</a> chapter.</p>
+
+<h2><a name="id7">Starting your debugging session</a></h2>
+
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>For a full description of starting your programs and the <b>Launch Configurations</b> options, see the <a href="lnch.html">Starting Your Programs</a> chapter.</td></tr>
+</table>
+<hr>
+
+
+<p>
+
+Once you've got a debuggable executable, you must create a launch configuration. </p>
+<p>
+
+To launch a debuggable executable:</p>
+<ol>
+
+<li>From the main menu, select <b>Run</b>--><b>Debug</b>. (This menu item appears by default in the <b>C/C++ Development</b> perspective. If it doesn't, or you wish to add it to another perspective, select <b>Window</b>--><b>Customize Perspective</b>. In the left pane, select <b>Other</b>--><b>Launch</b>. Enable <b>Launch</b>.)
+   The <b>Launch Configurations</b> dialog appears.
+   </li>
+<li>Create a launch configuration as you normally would, but don't click <b>OK</b>.
+   </li>
+<li>Select the <b>Debugger</b> tab.
+   </li>
+<li>Ensure <b>Run program in debugger</b> is selected.
+   </li>
+<li>Ensure <b>Stop at main() on startup</b> is enabled.
+   </li>
+<li>Click <b>Apply</b>.
+   </li>
+<li>By default, the IDE automatically changes to the <b>Debug</b> perspective when you debug a program. If the default is no longer set, or you wish to change to a different perspective when you debug, see the <a href="lnch.html#lnch_tabs">"Setting execution options (Launch Configurations tabs)"</a> section in the <a href="lnch.html">Starting Your Programs</a> chapter.
+   </li>
+<li>Click <b>Debug</b>.</li>
+</ol>
+
+
+<h1><a name="control">Controlling your debug session (Debug view)</a></h1>
+
+<p>The <b>Debug</b> view shows a listing of your debug sessions and lets you run your code step-by-step. The IDE is powerful; you can simultaneously debug multiple processes, each with multiple threads.</p>
+
+<h2><a name="id10">Understanding the Debug view</a></h2>
+
+<p>The <b>Debug</b> view lets you manage the debugging or running of a program in the workbench. This view displays the stack frame for the suspended threads for each target you're debugging. Each thread in your program appears as a node in the tree. The view displays the process for each program you're running. </p>
+<p><img src="./images/view_debug.jpg" alt="Debug view"></p>
+<p>The <b>Debug</b> view shows the target information in a tree hierarchy as follows (shown here with a sample of the possible icons):</p>
+<table border=1 width="100%">
+
+<tr>
+<th>Session item
+	</th>
+<th>Description
+	</th>
+<th>Possible<br>icons</th>
+</tr>
+<tr>
+<td>Launch instance
+	</td>
+<td>Launch configuration name and launch type (e.g. <tt>Stack Builder [C/C++ QNX QConn (IP)]</tt>)
+	</td>
+<td><img src="./images/icon_debug_exc.gif" alt="Icon: Debug executable">
+	<img src="./images/icon_run_exc.gif" alt="Icon: Run executable">
+
+</td>
+</tr>
+<tr>
+<td>Debugger instance
+	</td>
+<td>Debugger name and state (e.g. <tt>GDB Debugger (Breakpoint hit)</tt>)
+	</td>
+<td><img src="./images/icon_debugt_obj.gif" alt="Icon: Debugger">
+
+</td>
+</tr>
+<tr>
+<td>Thread instance
+	</td>
+<td>Thread number and state (e.g. <tt>Thread[1] (Suspended)</tt>)
+	</td>
+<td><img src="./images/icon_thread1.gif" alt="Icon: Thread; suspended">
+	<img src="./images/icon_thread2.gif" alt="Icon: Thread; running">
+	<img src="./images/icon_thread3.gif" alt="Icon: Thread; stopped">
+
+</td>
+</tr>
+<tr>
+<td>Stack frame instance
+	</td>
+<td>Stack frame number, function, filename, and file line number
+	</td>
+<td><img src="./images/icon_stackframe.gif" alt="Icon: Stackframe">
+	<img src="./images/icon_stackframe_running.gif" alt="Icon: Stack frame; running"></td>
+</tr>
+</table>
+
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>The number beside the thread label is a reference counter for the IDE, not a thread identification number (TID).</td></tr>
+</table>
+<hr>
+
+
+<p>
+
+The IDE displays stack frames as child elements. It displays the reason for the suspension beside the target, such as end of stepping range, breakpoint hit, signal received, and so on. When a program exits, the IDE displays the exit code. </p>
+<p>
+
+The label includes the thread's state. In the example above, the label indicates that the thread was suspended because the program hit a breakpoint. You can't suspend only one thread in a process; when one thread is suspended, they all are.</p>
+<p>
+
+The <b>Debug</b> view also drives the <b>C/C++ Editor</b>; as you step through your program, the <b>C/C++ Editor</b> highlights the location of the execution pointer. 
+
+</p>
+
+<h2><a name="id12">Controlling your debug execution</a></h2>
+
+<p>After you start your debug execution, it stops (by default) in <i>main()</i> and waits for your input. (For information about changing this setting, see the <a href="lnch.html#tab_debugger">"Debugger tab"</a> section in the <a href="lnch.html">Starting Your Programs</a> chapter.) You can control your debug execution in various ways, but they all rely on a core set of debug controls. </p>
+
+<h3><a name="id14">Debug execution controls</a></h3>
+
+<p>The debug execution controls appear in the following places (though they don't all appear in any one place):</p>
+<ul>
+<li>at the top of the <b>Debug</b> view as buttons
+	</li>
+<li>in the <b>Debug</b> view right-click context menu
+	</li>
+<li>in the main menu under <b>Run</b> (with hotkeys)
+	</li>
+<li>in the <b>C/C++ Editor</b>.</li>
+</ul>
+<p> The debug execution controls are superceded by breakpoints. For example, if you ask the program to step over a function (i.e. run until it finishes that function) and the program hits a breakpoint, it pauses, even though it hasn't finished the function.</p>
+<p>
+
+The icons and menu items are context-sensitive. For example, you can terminate a process, but you can't terminate a stack frame.</p>
+<table border=1 width="100%">
+
+<tr>
+<th>Action
+	</th>
+<th>Icon	
+	</th>
+<th>Hotkey	
+	</th>
+<th>Description
+	</th>
+</tr>
+<tr>
+<td><b>Resume</b>
+	</td>
+<td><img src="./images/icon_resume.gif" alt="Icon: Resume">
+	</td>
+<td><font face="Helvetica"><b>F8</b></font>
+	</td>
+<td>Run the process freely from current point	
+
+</td>
+</tr>
+<tr>
+<td><b>Suspend</b>
+	</td>
+<td><img src="./images/icon_suspend.gif" alt="Icon: Suspend">
+	</td>
+<td>&nbsp;
+
+	</td>
+<td>Regain control of the running process	
+		</td>
+</tr>
+<tr>
+<td><b>Terminate</b>
+	</td>
+<td><img src="./images/icon_terminate.gif" alt="Icon: Terminate">
+	</td>
+<td>&nbsp;
+
+	</td>
+<td>Kill the process	
+
+</td>
+</tr>
+<tr>
+<td><b>Restart</b>
+	</td>
+<td><img src="./images/icon_restart.gif" alt="Icon: Restart">
+	</td>
+<td>&nbsp;
+
+	</td>
+<td>Rerun the process from the beginning	
+	</td>
+</tr>
+<tr>
+<td><b>Step into</b>
+	</td>
+<td><img src="./images/icon_stepinto.gif" alt="Icon: Step Into">
+	</td>
+<td><font face="Helvetica"><b>F5</b></font>
+	</td>
+<td>Step forward one line, going into function calls	
+
+</td>
+</tr>
+<tr>
+<td><b>Step over</b>
+	</td>
+<td><img src="./images/icon_stepover.gif" alt="Icon: Step Over">
+	</td>
+<td><font face="Helvetica"><b>F6</b></font>
+	</td>
+<td>Step forward one line, not going into function calls	
+
+</td>
+</tr>
+<tr>
+<td><b>Run to return</b>
+	</td>
+<td><img src="./images/icon_stepreturn.gif" alt="Icon: Step Return">
+	</td>
+<td><font face="Helvetica"><b>F7</b></font>
+	</td>
+<td>Finish this function	</td>
+</tr>
+</table>
+
+
+<h3><a name="id16">Controlling your debug execution (Debug view)</a></h3>
+
+<p>You can control how many steps the program runs before it suspends again (if you want it to suspend at all). You'll probably use the <b>Debug</b> view primarily to control your program flow.</p>
+<p>
+
+To control your debug execution:</p>
+<p></p>
+<ol>
+
+<li>In the <b>Debug</b> view, select the thread you wish to control. 
+   </li>
+<li>Click one of the debug stepping icons described in the "Debug execution controls" section, above.
+   </li>
+<li>Repeat step 2 as desired.
+   </li>
+<li>Finish the debug session by choosing one of the controls described in the "Debug launch controls" section in this chapter.</li>
+</ol>
+
+
+<h3><a name="id18">Controlling your debug execution (hotkeys)</a></h3>
+
+<p>If you're running your debug session without the <b>Debug</b> view showing, you can use either the hotkeys or the <b>Run</b> menu to step through your program. The customization works on a per-perspective basis; if you want to use the hotkeys in another perspective, you must enable them there, too.</p>
+<p>
+
+To enable the debug hotkeys:</p>
+<ol>
+
+<li>Open the perspective you want to enable the hotkeys for.
+   </li>
+<li>From the menu, select <b>Window</b>--><b>Customize Perspective</b>.
+   </li>
+<li>In the left pane, select <b>Other</b>--><b>Debug</b>.
+   </li>
+<li>In the left pane, enable <b>Debug</b>.
+   </li>
+<li>Click <b>OK</b>.
+  The hotkeys are enabled for that particular perspective. You can also access the controls from the <b>Run</b> menu.
+   </li>
+</ol>
+
+
+<h3><a name="id20">Controlling your debug execution (C/C++ Editor)</a></h3>
+
+<p>You can control your debug session using the <b>C/C++ Editor</b> by having the program run until it hits the line your cursor is sitting on. (This is the same as the <tt>gdb until</tt> command.) If the program never hits that line, the program runs until it finishes. </p>
+<p>
+
+You enable this option on a per-perspective basis. The option is enabled by default in the <b>Debug</b> perspective.</p>
+<p>
+
+To enable debug execution using the <b>C/C++ Editor</b>:</p>
+<p></p>
+<ol>
+
+<li>From the menu, select <b>Window</b>--><b>Customize Perspective</b>.
+   </li>
+<li>In the left pane, select <b>Other</b>--><b>C/C++ Debug</b>.
+   </li>
+<li>In the left pane, enable <b>C/C++ Debug</b>.
+   </li>
+<li>Click <b>OK</b>.
+   The controls for debug execution in the <b>C/C++ Editor</b> are enabled for your active perspective.</li>
+</ol>
+
+<p>
+
+To debug using the <b>C/C++ Editor</b>:</p>
+<p></p>
+<ol>
+
+<li>In the <b>C/C++ Editor</b>, select a file associated with the process being debugged (e.g. <tt>myProgram.c</tt>).
+   </li>
+<li>Left-click to insert the cursor where you want to interrupt the execution.
+   </li>
+<li>Right-click near the cursor and select <b>Run to C/C++ Line</b>:
+   <p>   <img src="./images/view_debug_runtoline.jpg" alt="Debug view; run to line"></p><p>	The program continues running until it hits that line.</p></li>
+</ol>
+
+
+<h2><a name="id22">Debug launch controls</a></h2>
+
+<p>In addition to controlling the individual stepping of your programs, you can also control the debug session itself. You can perform actions such as terminating the session, stopping the program, and so on, using the debug launch controls available in the <b>Debug</b> view or in the <b>Debug</b> view's right-click context menu. As with the other debug controls, these are context-sensitive; some are disabled depending on whether you've selected a thread, a process, and so on, in the <b>Debug</b> view.</p>
+<p></p>
+<table border=1 width="100%">
+
+<tr>
+<th>Action
+	</th>
+<th>Icon
+	</th>
+<th>Description</th>
+</tr>
+<tr>
+<td><b>Terminate</b>
+	</td>
+<td><img src="./images/icon_terminate.gif" alt="Icon: Terminate">
+	</td>
+<td>Kill the selected process	</td>
+</tr>
+<tr>
+<td><b>Terminate &amp; Remove</b>
+	</td>
+<td><img src="./images/icon_terminate_rem.gif" alt="Icon: Terminate and Remove">
+	</td>
+<td>Kill the selected process and remove it from the <b>Debug</b> view	</td>
+</tr>
+<tr>
+<td><b>Terminate All</b>
+	</td>
+<td><img src="./images/icon_terminate_all.gif" alt="Icon: Terminate All">
+	</td>
+<td>Kill all active processes in the Debug view	</td>
+</tr>
+<tr>
+<td><b>Disconnect</b>
+	</td>
+<td><img src="./images/icon_disconnect.gif" alt="Icon: Disconnect">
+	</td>
+<td>Detach the debugger (i.e. <tt>gdb</tt>) from the selected process (useful for debugging attached processes)	</td>
+</tr>
+<tr>
+<td><b>Remove All Terminated Launches</b>
+	</td>
+<td><img src="./images/icon_remove_all.gif" alt="Icon: Remove All Terminated">
+	</td>
+<td>Clear all the killed processes from the Debug view	</td>
+</tr>
+<tr>
+<td><b>Relaunch</b>
+	</td>
+<td><img src="./images/icon_relaunch.gif" alt="Icon: Relaunch">
+	</td>
+<td>Restart the process</td>
+</tr>
+</table>
+
+
+<h2><a name="id24">Disassembly mode</a></h2>
+
+<p>When you're debugging, you can also examine your program as it steps into functions that you don't have source code for, such as <i>printf()</i>. Normally, the debugger steps over these functions, even when you click <b>Step Into</b>. When the instruction pointer enters functions for which it doesn't have the source, the IDE shows the function in the <b>Assembly Editor</b>.
+
+</p>
+<p>To step into assembler functions during debugging:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>Debug</b> view, click the <b>Disassembly Mode On/Off</b> toggle button <img src="./images/icon_disassembly.gif" alt="Icon: Disassembly Mode On/Off">.
+	As you <b>Step Into</b> assembler functions, the IDE shows the execution trace in the <b>Assembly Editor</b>.</td></tr>
+</table>
+
+
+
+<h1><a name="more">More debugging features</a></h1>
+
+<p>This section contains the following subsections:</p>
+<ul>
+<li><a href="#view_variables">Inspecting your variables (Variables view)</a>
+   </li>
+<li><a href="#view_breakpoints">Using breakpoints and watchpoints (Breakpoints view)</a>
+   </li>
+<li><a href="#view_expressions">Evaluating your expressions (Expressions view)</a>
+   </li>
+<li><a href="#view_registers">Inspecting your registers (Registers view)</a>
+   </li>
+<li><a href="#view_memory">Inspecting your process memory (Memory view)</a>
+   </li>
+<li><a href="#view_console">Viewing your output (Console view)</a>
+   </li>
+<li><a href="#view_console_gdb">Debugging with GDB (Console view)</a></li>
+</ul>
+
+<h2><a name="view_variables">Inspecting your variables (Variables view)</a></h2>
+
+<p>
+
+The <b>Variables</b> view displays information about the variables in the currently selected stack frame:</p>
+<p><img src="./images/view_variables.jpg" alt="Variables view"></p>
+<p> When the execution stops, the changed values are highlighted in red (by default). Like the other debug-related views, the <b>Variables</b> view doesn't try to keep up with the execution of a running program; it updates only when execution stops.
+
+</p>
+<p>You can set whether or not the variable type (e.g. <tt>int</tt>) is displayed by clicking the <b>Show Type Names</b> toggle button <img src="./images/icon_tnames.gif" alt="Icon: Show Type Names">.</p>
+
+<h3><a name="id28">Customizing the Variables view</a></h3>
+
+<p>You can customize the look of the <b>Variables</b> view and set the color of changed variables (red by default).
+
+</p>
+<p>To access the <b>Variables</b> view preferences:</p>
+<ol>
+
+<li>From the main menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>Debug</b>--><b>Variables View</b>:<p>   <img src="./images/view_variables_customize.jpg" alt="Variables view; customization"></p></li>
+</ol>
+
+
+<h3><a name="id30">Changing variable values</a></h3>
+
+<p>During the course of debugging, you may wish to artificially change the value of a variable to test how your program handles the setting or to speed through a loop.</p>
+<p>
+
+To change a variable value while debugging:</p>
+<p></p>
+<ol>
+
+<li>In the <b>Variables</b> view, right-click the variable and select <b>Change Variable Value</b>.
+   </li>
+<li>Enter the new value in the available field.</li>
+</ol>
+
+
+<h2><a name="view_breakpoints">Using breakpoints and watchpoints (Breakpoints view)</a></h2>
+
+<p>The <b>Breakpoints</b> view lists all the breakpoints and watchpoints you've set in your open projects:</p>
+<p><img src="./images/view_breakpoints.jpg" alt="Breakpoints view">
+
+</p>
+<p>A <i>breakpoint</i> makes your program stop whenever a certain point in the program is reached. For each breakpoint, you can add conditions to better control whether or not your program stops.</p>
+<p>
+
+A <i>watchpoint</i> is a special breakpoint that stops the program's execution whenever the value of an expression changes, without specifying where this may happen. Unlike breakpoints, which are line-specific, watchpoints are event-specific and take effect whenever a specified condition is true, regardless of when or where it occurred.</p>
+<p></p>
+<table border=1 width="100%">
+
+<tr>
+<th>Object
+	</th>
+<th>Icon</th>
+</tr>
+<tr>
+<td>Breakpoint
+	</td>
+<td><img src="./images/icon_breakpoint_obj.gif" alt="Icon: Breakpoint"></td>
+</tr>
+<tr>
+<td>Watchpoint (read)
+	</td>
+<td><img src="./images/icon_watchpoint_read_obj.gif" alt="Icon: Watchpoint; read"></td>
+</tr>
+<tr>
+<td>Watchpoint (write)
+	</td>
+<td><img src="./images/icon_watchpoint_write_obj.gif" alt="Icon: Watchpoint; write"></td>
+</tr>
+<tr>
+<td>Watchpoint (read and write)
+	</td>
+<td><img src="./images/icon_watchpoint_readwrite_obj.gif" alt="Icon: Watchpoint; read and write"></td>
+</tr>
+</table>
+
+<p>If the breakpoint or watchpoint is for a connected target, a check mark <img src="./images/icon_installed_ovr.gif" alt="Icon: Checkmark; overlay"> is superimposed on the icon.
+
+
+</p>
+<p>The rest of this section describes how to:
+
+</p>
+<ul>
+<li><a href="#view_breakpoints_add_break">Add breakpoints</a>
+	</li>
+<li><a href="#view_breakpoints_add_watch">Add watchpoints</a>
+	</li>
+<li><a href="#view_breakpoints_setprop">Set properties of breakpoints and watchpoints</a>
+	</li>
+<li><a href="#view_breakpoints_disable">Disable and enable breakpoints and watchpoints</a>
+	</li>
+<li><a href="#view_breakpoints_remove">Remove breakpoints and watchpoints</a></li>
+</ul>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>While the <b>Breakpoints</b> view displays both breakpoints and watchpoints, the procedures for setting them differ somewhat. </td></tr>
+</table>
+<hr>
+
+
+
+<h3><a name="view_breakpoints_add_break">Adding breakpoints</a></h3>
+
+<p>You set breakpoints on an executable line of a program. If the breakpoint is enabled when you debug, the execution suspends <em>before</em> that line of code executes. </p>
+<p>
+
+To add a breakpoint:</p>
+<ol>
+
+<li>In the editor area, open the file that you want to add the breakpoint to (e.g. <tt>myProgram.c</tt>).
+   </li>
+<li>Notice that the left edge of the <b>C/C++ Editor</b> has a blank space called a <i>marker bar</i>.
+   </li>
+<li>Hover your pointer over the marker bar, beside the exact line of code where you want to add a breakpoint. Right-click the marker bar and select <b>Add Breakpoint</b>:<p>   <img src="./images/view_breakpoints_adding.jpg" alt="Breakpoints view; adding breakpoints"></p><p>   A dot <img src="./images/icon_breakpoint_obj.gif" alt="Icon: Breakpoint object"> appears, indicating a breakpoint. A corresponding dot <img src="./images/icon_breakpoint_obj.gif" alt="Icon: Breakpoint object"> also appears in the <b>Breakpoints</b> view, along with the name of the file in which you set the breakpoint:</p><p>   <img src="./images/view_breakpoints_added.jpg" alt="Breakpoints view; breakpoint added">
+   </p></li>
+</ol>
+
+
+<h3><a name="view_breakpoints_add_watch">Adding watchpoints</a></h3>
+
+<p>To add a watchpoint:</p>
+<ol>
+
+<li>From the main menu, select <b>Run</b>--><b>Add C/C++ Watchpoint</b>. (If this option isn't available, select <b>Window</b>--><b>Customize Perspective</b>. In the left pane, select <b>Other</b>. Enable <b>C/C++ Debug</b>. Click <b>OK</b>.)
+   The <b>Add C/C++ Watchpoint</b> dialog appears:<p>   <img src="./images/view_breakpoints_watch_add.jpg" alt="Breakpoints view; adding watchpoints">
+   </p></li>
+<li>Enter an expression in the <b>Expression to watch</b> field. The expression may be anything that can be evaluated inside an <tt>if</tt> statement. (e.g. <tt>y==1</tt>)
+   </li>
+<li>If you want the program to stop when it reads the watch expression, enable <b>Read</b>; to have the program stop when it writes the watch expression, enable <b>Write</b>. You must enable at least one.
+   </li>
+<li>Click <b>OK</b>.
+   The watchpoint appears in the <b>Breakpoints</b> view list.</li>
+</ol>
+
+
+<h3><a name="view_breakpoints_setprop">Setting properties of breakpoints and watchpoints</a></h3>
+
+<p>After you've set your breakpoint or watchpoint, the IDE unconditionally halts the program when:</p>
+<ul>
+<li>it reaches a line of code that the breakpoint is set on
+<p>Or:
+	</p></li>
+<li>the expression specified by the watchpoint becomes true.</li>
+</ul>
+<p>
+
+To set the properties for a breakpoint or watchpoint:</p>
+<ol>
+
+<li>In the <b>Breakpoints</b> view, right-click the breakpoint or watchpoint and select <b>Properties</b>. (Or for breakpoints only, in the <b>C/C++ Editor</b>, right-click the breakpoint and select <b>Breakpoint Properties</b>.)
+    The <b>C/C++ Line Breakpoint Properties</b> or <b>C/C++ Watchpoint Properties</b> dialog appears (they're very similar). You need to fill in at least one field:<p>   <img src="./images/view_breakpoints_prop.jpg" alt="Breakpoints view; setting breakpoint properties">
+   
+   </p></li>
+<li>In the <b>Condition</b> field, enter the Boolean expression to evaluate. The expression may be anything that can be evaluated inside an <tt>if</tt> statement (e.g. <tt>x &gt; y</tt> ). The default is TRUE.
+   </li>
+<li>In the <b>Ignore Count</b> field, enter the number of times the breakpoint or watchpoint may be hit before it begins to take effect (not the number of times the condition is true). The default is 0.
+   </li>
+<li>Click <b>OK</b>.
+   When in debug mode, your program stops when it meets the conditions you've set for the breakpoint or watchpoint.</li>
+</ol>
+
+
+<h3><a name="view_breakpoints_disable">Disabling and enabling breakpoints and watchpoints</a></h3>
+
+<p>You may wish to temporarily deactivate a breakpoint or watchpoint without losing the information it contains.</p>
+<p>
+
+To disable or enable a breakpoint or watchpoint:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>Breakpoints</b> view, right-click the breakpoint or watchpoint and select <b>Disable</b> or <b>Enable</b> (Or for breakpoints only, right-click the breakpoint in the editor area and select <b>Disable Breakpoint</b> or <b>Enable Breakpoint</b>):<p><img src="./images/view_breakpoints_disable.jpg" alt="Breakpoints view; disabling breakpoints"></p></td></tr>
+</table>
+
+
+<p>To disable or enable all (or many) breakpoints or watchpoints:
+
+</p>
+<ol>
+
+<li>In the <b>Breakpoints</b> view, use any of the following methods:
+   <ul>
+<li>Select breakpoints and watchpoints while holding down the <font face="Helvetica"><b>Ctrl</b></font> key.
+  		 </li>
+<li>Select a range of breakpoints and watchpoints while holding down the <font face="Helvetica"><b>Shift</b></font> key.
+  		 </li>
+<li>From the main menu, select <b>Edit</b>--><b>Select All</b>.
+  		 </li>
+<li>Right-click in the <b>Breakpoints</b> view and select <b>Select All</b>.
+	</li>
+</ul>
+   </li>
+<li>Right-click the highlighted breakpoints and watchpoints and select <b>Disable</b> or <b>Enable</b>.</li>
+</ol>
+
+
+<h3><a name="view_breakpoints_remove">Removing breakpoints and watchpoints</a></h3>
+
+<p>
+
+To remove one or more breakpoints and watchpoints:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>Follow the procedure described in <a href="#view_breakpoints_disable">"Disabling and enabling breakpoints and watchpoints"</a>, with the following exceptions:
+	<ul>
+<li>Instead of selecting <b>Disable</b> or <b>Enable</b>, select <b>Remove</b>.
+	</li>
+</ul></td></tr>
+</table>
+
+
+<p>
+
+To remove all breakpoints and watchpoints:
+
+</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>Breakpoints</b> view, right-click and select <b>Remove All</b>.</td></tr>
+</table>
+
+
+
+<h2><a name="view_expressions">Evaluating your expressions (Expressions view)</a></h2>
+
+<p>The <b>Expressions</b> view lets you evaluate and examine the value of expressions:</p>
+<p><img src="./images/view_expressions.jpg" alt="Expressions view">
+
+
+</p>
+<p>To evaluate an expression:</p>
+<ol>
+
+<li>From the menu, select <b>Run</b>--><b>Add C/C++ Expression</b>. (Or, right-click in the <b>C/C++ Editor</b> and select <b>Add C/C++ Expression</b>.)
+   The <b>Add Expression</b> dialog opens:<p>   <img src="./images/view_expressions_add.jpg" alt="Expressions view; add expressions">
+   
+   </p></li>
+<li>Enter the expression you want to evaluate (e.g. <tt>(x-5)*3</tt> ).
+   </li>
+<li>Click <b>OK</b>.
+   The expression and its value appear in the <b>Expressions</b> view. When the execution of a program is suspended, the IDE reevaluates all expressions and highlights the changed values.</li>
+</ol>
+
+
+<h2><a name="view_registers">Inspecting your registers (Registers view)</a></h2>
+
+<p>The <b>Registers</b> view displays information about the registers in the currently selected stack frame. When the execution stops, the changed values are highlighted. The functionality of the <b>Registers</b> view is very similar to that of the <b>Variables</b> view; for more information, see the <a href="#view_variables">"Inspecting your variables (Variables view)"</a> section in this chapter.</p>
+<p><img src="./images/view_registers.jpg" alt="Registers view"></p>
+<p>You can also customize the colors in the <b>Registers</b> view and change the default value of the <b>Show Type Names</b> option.
+
+</p>
+<p>To access the <b>Registers</b> view customization dialog:</p>
+<ol>
+
+<li>From the main menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>Debug</b>--><b>Registers View</b>.</li>
+</ol>
+
+
+<h2><a name="view_memory">Inspecting your process memory (Memory view)</a></h2>
+
+<p>The <b>Memory</b> view lets you inspect and change your process memory. The view consists of four tabs that let you inspect multiple sections of memory:</p>
+<p><img src="./images/view_memory.jpg" alt="Memory view">
+
+</p>
+<p></p>
+
+
+<h3><a name="id41">Inspecting memory</a></h3>
+
+<p>The <b>Memory</b> view supports the same addressing as the C language. You can address memory using expressions such as <tt>0x0847d3c</tt>, <tt>(&amp;y)+1024</tt>, and <tt>*ptr</tt>.
+
+</p>
+<p>To inspect your process memory:</p>
+<ol>
+
+<li>In the <b>Debug</b> view, select a process. Selecting a thread automatically selects the associated process.
+   </li>
+<li>In the <b>Memory</b> view, select one of the four tabs labeled <b>Memory 1</b>, <b>Memory 2</b>, and so on.
+   </li>
+<li>In the <b>Address</b> field, type the address and press <font face="Helvetica"><b>Enter</b></font>.</li>
+</ol>
+
+
+<h3><a name="id43">Changing memory</a></h3>
+
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/caution.gif" alt="Caution:"></td>
+<td>Changing your process memory can make your program crash.</td></tr>
+</table>
+<hr>
+
+
+<p>To change your process memory:</p>
+<ol>
+
+<li>Follow the procedure for inspecting your process memory.
+   </li>
+<li>In the memory pane, type the new value for the memory. The <b>Memory</b> view works in "typeover" mode; use the arrow keys to jump from byte to byte:<p>   <img src="./images/view_memory_change.jpg" alt="Memory view; changing">
+   </p></li>
+<li>Click the <b>Save Changes</b> button<img src="./images/icon_memory_update.gif" alt="Icon: Save Changes">.
+   The changed memory appears in red.</li>
+</ol>
+
+
+<h3><a name="id45">Configuring output format</a></h3>
+
+<p>You can configure your output to display hexadecimal or decimal. You can also set the number of display columns and the memory unit size. You can configure each memory tab independently.</p>
+<p>
+
+To configure the output format:</p>
+<ol>
+
+<li>In the <b>Memory</b> view, select one of the four tabs labeled <b>Memory 1</b>, <b>Memory 2</b>, and so on.
+   </li>
+<li>Right-click the pane and select any of <b>Format</b>, <b>Memory Unit Size</b>, or <b>Number of Columns</b>. Choose your desired output format:<p>   <img src="./images/view_memory_configure.jpg" alt="Memory view; configure"></p><p>      The output reflects your selection. Note that some output formats are best viewed in a nonproportional font such as Courier.
+
+</p></li>
+</ol>
+
+
+<h3><a name="id47">Customizing the Memory view</a></h3>
+
+<p>You can customize the <b>Memory</b> view to display in different colors and fonts. You can also customize some of its behavior. The customizations affect the entire <b>Memory</b> view.</p>
+<p>
+
+To access the <b>Memory</b> view customization dialog:</p>
+<ol>
+
+<li>From the menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>Debug</b>--><b>Memory View</b>.
+   </li>
+<li>You can now change the colors, font, and behavior of the <b>Memory</b> view. When you're done, click <b>Apply</b>, then <b>OK</b>.
+   </li>
+</ol>
+
+
+<h2><a name="view_console">Viewing your output (Console view)</a></h2>
+
+<p>The <b>Console</b> view shows you the output of the execution of your program and lets you supply input to your program:</p>
+<p><img src="./images/view_console.jpg" alt="Console view"></p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>See also the <a href="#view_console_gdb">"Debugging with GDB (Console view)"</a> section, below.</td></tr>
+</table>
+<hr>
+
+
+<p>
+
+The console shows three different kinds of text, each in a different default color:</p>
+<ul>
+<li>standard output (blue)
+   </li>
+<li>standard error (red)
+   </li>
+<li>standard input (green)</li>
+</ul>
+<p>You can choose different colors for these kinds of text on the preferences pages.
+
+</p>
+<p>To access the <b>Console</b> view customization dialog:</p>
+<ol>
+
+<li>From the menu, select <b>Window</b>--><b>Preferences</b>.
+   </li>
+<li>In the left pane, select <b>Debug</b>--><b>Console</b>.</li>
+</ol>
+
+
+<h2><a name="view_console_gdb">Debugging with GDB (Console view)</a></h2>
+
+<p>The IDE lets you debug using a subset of the commands that the <tt>gdb</tt> utility offers:</p>
+<p><img src="./images/view_console_gdb.jpg" alt="Console view; GDB"></p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>See also the <a href="#view_console">"Viewing your output (Console view)"</a> section, above.</td></tr>
+</table>
+<hr>
+
+</p>
+
+<h3><a name="id51">Enabling the GDB Console view</a></h3>
+
+<p>The <b>GDB Console</b> view is part of the regular <b>Console</b> view but isn't accessible until you toggle to it. Once you do, GDB output appears in place of the regular <b>Console</b> view output.
+
+</p>
+<p>To enable the <b>GDB Console</b> view:</p>
+<ol>
+
+<li>In the <b>Debug</b> view, select a debug session.
+   </li>
+<li>In the <b>Debug</b> view, click the <b>Show Debugger Console on Target Selection</b> button <img src="./images/icon_debugger_console.gif" alt="Icon: Show Debugger Console on Target Selection">.
+   The <b>Console</b> view changes to the <b>GDB Debugger Console</b> view.</li>
+</ol>
+
+
+<h3><a name="id53">Using the GDB Console view</a></h3>
+
+<p>The <b>GDB Console</b> view lets you bypass the IDE and talk directly to GDB; the IDE is unaware of anything done in the <b>GDB Console</b> view. Thus, items such as breakpoints that you set from the <b>GDB Console</b> view don't appear in the <b>C/C++ Editor</b>.</p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>You can't use the <font face="Helvetica"><b>Tab</b></font> key for line completion because the commands are sent to GDB only when you press <tt>Enter</tt>.</td></tr>
+</table>
+<hr>
+
+
+<p>To use the <b>GDB Console</b> view:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>In the <b>GDB Console</b> view, enter a command. For example, enter <tt>help</tt> to get a list of commands; <tt>nexti</tt> to step one instruction, proceeding through subroutine calls; <tt>nexti 3</tt> to step three:<p><img src="./images/view_console_gdb_using.jpg" alt="Console view; GDB; using"></p></td></tr>
+</table>
+
+
+
+
+</body>
+
+</html>
+
+<!--
+/**********************************************************************
+ * Copyright (c) 2002,2003 QNX Software Systems Ltd. and others.
+ * All rights reserved.   This program and the accompanying materials
+ * are made available under the terms of the Common Public License v0.5
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v05.html
+ * 
+ * Contributors: 
+ * QNX Software Systems - Initial API and implementation
+***********************************************************************/
+-->
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/caution.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/caution.gif
new file mode 100644
index 00000000000..f4ec4e7b194
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/caution.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/onestep.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/onestep.gif
new file mode 100644
index 00000000000..239243c1059
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/onestep.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/pointing.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/pointing.gif
new file mode 100644
index 00000000000..903f23707c9
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/image-lib/pointing.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz.jpg
new file mode 100644
index 00000000000..23d9f690a84
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c.jpg
new file mode 100644
index 00000000000..c1898523069
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_architecture.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_architecture.jpg
new file mode 100644
index 00000000000..a07df4a7457
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_architecture.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_buildsettings.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_buildsettings.jpg
new file mode 100644
index 00000000000..1a45dcad259
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_buildsettings.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_library.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_library.jpg
new file mode 100644
index 00000000000..d824c834336
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_library.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_options.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_options.jpg
new file mode 100644
index 00000000000..aaf0bdfad6c
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_options.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_projects.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_projects.jpg
new file mode 100644
index 00000000000..5c80aa3fd32
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_c_projects.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_convert_1.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_convert_1.jpg
new file mode 100644
index 00000000000..e1027e3438b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_convert_1.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_target.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_target.jpg
new file mode 100644
index 00000000000..1f4530af3e8
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/cwiz_target.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c.jpg
new file mode 100644
index 00000000000..775044e2c13
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_codetemplates_use.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_codetemplates_use.jpg
new file mode 100644
index 00000000000..0382955bdf7
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_codetemplates_use.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_contentassist.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_contentassist.jpg
new file mode 100644
index 00000000000..b7db881d3e6
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_contentassist.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_helloworld.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_helloworld.jpg
new file mode 100644
index 00000000000..9fb6c01590b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_helloworld.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_hoverhelp.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_hoverhelp.jpg
new file mode 100644
index 00000000000..0971f4ee3cf
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/editor_c_hoverhelp.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/findit b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/findit
new file mode 100644
index 00000000000..34010dbfb31
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/findit
@@ -0,0 +1,13 @@
+#!/bin/sh
+
+for i in `ls *.gif *.jpg`
+do
+
+	grep $i ../*.html > /dev/null
+	result=$?
+	if [ $result -ne 0 ]
+	then
+		echo "Removing $i ($result)"
+		/bin/rm -f $i
+	fi
+done
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/first_look.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/first_look.jpg
new file mode 100644
index 00000000000..8c73a267472
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/first_look.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_breakpoint_obj.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_breakpoint_obj.gif
new file mode 100644
index 00000000000..06d007905b2
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_breakpoint_obj.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debug_exc.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debug_exc.gif
new file mode 100644
index 00000000000..3052a80cd67
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debug_exc.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debugger_console.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debugger_console.gif
new file mode 100644
index 00000000000..e6d5b138d46
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debugger_console.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debugt_obj.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debugt_obj.gif
new file mode 100644
index 00000000000..d139cde9dd4
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_debugt_obj.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_disassembly.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_disassembly.gif
new file mode 100644
index 00000000000..a78e3024c87
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_disassembly.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_disconnect.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_disconnect.gif
new file mode 100644
index 00000000000..f1d5fb31e51
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_disconnect.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_error_obj.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_error_obj.gif
new file mode 100644
index 00000000000..b04020bc723
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_error_obj.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_filter_tsk.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_filter_tsk.gif
new file mode 100644
index 00000000000..1492b4efae2
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_filter_tsk.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_installed_ovr.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_installed_ovr.gif
new file mode 100644
index 00000000000..7f4a31ee7eb
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_installed_ovr.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_memory_update.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_memory_update.gif
new file mode 100644
index 00000000000..ca4fe2b1cff
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_memory_update.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_menu.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_menu.gif
new file mode 100644
index 00000000000..a492838d248
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_menu.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newccqnx_app.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newccqnx_app.gif
new file mode 100644
index 00000000000..b7165fa005a
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newccqnx_app.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newccqnx_lib.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newccqnx_lib.gif
new file mode 100644
index 00000000000..af20154d34b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newccqnx_lib.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newcqnx_app.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newcqnx_app.gif
new file mode 100644
index 00000000000..385a8ba0cc8
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newcqnx_app.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newcqnx_lib.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newcqnx_lib.gif
new file mode 100644
index 00000000000..a48b45c47ce
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_newcqnx_lib.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_next_error_nav.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_next_error_nav.gif
new file mode 100644
index 00000000000..775842e89d1
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_next_error_nav.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_prev_error_nav.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_prev_error_nav.gif
new file mode 100644
index 00000000000..3b1bb7ca128
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_prev_error_nav.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_relaunch.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_relaunch.gif
new file mode 100644
index 00000000000..6b0c23d8f61
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_relaunch.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_remove_all.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_remove_all.gif
new file mode 100644
index 00000000000..2c069ab3f43
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_remove_all.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_restart.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_restart.gif
new file mode 100644
index 00000000000..a063c230aca
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_restart.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_resume.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_resume.gif
new file mode 100644
index 00000000000..2088548a499
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_resume.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_run_exc.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_run_exc.gif
new file mode 100644
index 00000000000..8174dade2bb
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_run_exc.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stackframe.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stackframe.gif
new file mode 100644
index 00000000000..b9783c814a7
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stackframe.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stackframe_running.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stackframe_running.gif
new file mode 100644
index 00000000000..ef406cf24c9
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stackframe_running.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepinto.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepinto.gif
new file mode 100644
index 00000000000..cc1378e0e0d
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepinto.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepover.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepover.gif
new file mode 100644
index 00000000000..5e24fb9b8fe
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepover.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepreturn.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepreturn.gif
new file mode 100644
index 00000000000..6081cba13ba
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_stepreturn.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_suspend.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_suspend.gif
new file mode 100644
index 00000000000..457893c1ba5
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_suspend.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate.gif
new file mode 100644
index 00000000000..d47876f6857
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate_all.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate_all.gif
new file mode 100644
index 00000000000..ec56a24fabc
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate_all.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate_rem.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate_rem.gif
new file mode 100644
index 00000000000..bd53994fb7b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_terminate_rem.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread1.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread1.gif
new file mode 100644
index 00000000000..7e4a43cd78c
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread1.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread2.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread2.gif
new file mode 100644
index 00000000000..fb5175f5c68
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread2.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread3.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread3.gif
new file mode 100644
index 00000000000..f2a16394e6d
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_thread3.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_tnames.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_tnames.gif
new file mode 100644
index 00000000000..1bbbb95c8ea
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_tnames.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_warning_obj.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_warning_obj.gif
new file mode 100644
index 00000000000..cf8d571833d
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_warning_obj.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_read_obj.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_read_obj.gif
new file mode 100644
index 00000000000..793b189d849
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_read_obj.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_readwrite_obj.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_readwrite_obj.gif
new file mode 100644
index 00000000000..0b1184d72a8
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_readwrite_obj.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_write_obj.gif b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_write_obj.gif
new file mode 100644
index 00000000000..b5fa352bb51
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/icon_watchpoint_write_obj.gif
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch.jpg
new file mode 100644
index 00000000000..735c3b3e553
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_arguments.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_arguments.jpg
new file mode 100644
index 00000000000..dab157b564b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_arguments.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_common.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_common.jpg
new file mode 100644
index 00000000000..12a27679ef8
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_common.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_customize.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_customize.jpg
new file mode 100644
index 00000000000..df901271dbd
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_customize.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_debug_debug.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_debug_debug.jpg
new file mode 100644
index 00000000000..1f241c0cfb5
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_debug_debug.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_debugger.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_debugger.jpg
new file mode 100644
index 00000000000..92679ca2c29
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_debugger.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_environment.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_environment.jpg
new file mode 100644
index 00000000000..d5d29676680
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_environment.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_main.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_main.jpg
new file mode 100644
index 00000000000..9ba0a2b2cc7
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_main.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_run2_faster.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_run2_faster.jpg
new file mode 100644
index 00000000000..f575b571111
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_run2_faster.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_run_run.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_run_run.jpg
new file mode 100644
index 00000000000..6d428f53843
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/lnch_run_run.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/persp_dbug_properties_options.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/persp_dbug_properties_options.jpg
new file mode 100644
index 00000000000..2ac4b01c9d1
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/persp_dbug_properties_options.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints.jpg
new file mode 100644
index 00000000000..b90f436f57c
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_added.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_added.jpg
new file mode 100644
index 00000000000..6c46064d6d9
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_added.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_adding.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_adding.jpg
new file mode 100644
index 00000000000..b0cefdcf9c5
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_adding.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_disable.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_disable.jpg
new file mode 100644
index 00000000000..d2713acb7a0
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_disable.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_prop.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_prop.jpg
new file mode 100644
index 00000000000..33dc1b97a31
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_prop.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_watch_add.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_watch_add.jpg
new file mode 100644
index 00000000000..51d66095f5b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_breakpoints_watch_add.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cbuild.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cbuild.jpg
new file mode 100644
index 00000000000..22eb91ce741
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cbuild.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cbuild_configurations.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cbuild_configurations.jpg
new file mode 100644
index 00000000000..d51d5e9b2cf
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cbuild_configurations.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console.jpg
new file mode 100644
index 00000000000..f0e8fcba1f6
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_gdb.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_gdb.jpg
new file mode 100644
index 00000000000..201fd624130
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_gdb.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_gdb_using.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_gdb_using.jpg
new file mode 100644
index 00000000000..1450ef52ee8
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_gdb_using.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_helloworld.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_helloworld.jpg
new file mode 100644
index 00000000000..7d73ca6d547
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_console_helloworld.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects.jpg
new file mode 100644
index 00000000000..7b26f7986bd
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_building.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_building.jpg
new file mode 100644
index 00000000000..81a98ae2d48
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_building.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_filter.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_filter.jpg
new file mode 100644
index 00000000000..fe2068b3aed
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_filter.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_outline_executable.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_outline_executable.jpg
new file mode 100644
index 00000000000..48e0c86bcd7
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_outline_executable.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_outline_source.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_outline_source.jpg
new file mode 100644
index 00000000000..17469f7dea9
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_outline_source.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_target_add.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_target_add.jpg
new file mode 100644
index 00000000000..2dc8b6c61a7
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_target_add.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_target_use.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_target_use.jpg
new file mode 100644
index 00000000000..15d968fcbeb
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_cprojects_target_use.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_debug.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_debug.jpg
new file mode 100644
index 00000000000..5ffbab51a2d
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_debug.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_debug_runtoline.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_debug_runtoline.jpg
new file mode 100644
index 00000000000..43674afff51
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_debug_runtoline.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_expressions.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_expressions.jpg
new file mode 100644
index 00000000000..4d706ed99ab
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_expressions.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_expressions_add.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_expressions_add.jpg
new file mode 100644
index 00000000000..8836ec003c2
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_expressions_add.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory.jpg
new file mode 100644
index 00000000000..414cb658784
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory_change.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory_change.jpg
new file mode 100644
index 00000000000..3636d953921
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory_change.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory_configure.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory_configure.jpg
new file mode 100644
index 00000000000..9a8a809b78a
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_memory_configure.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_outline.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_outline.jpg
new file mode 100644
index 00000000000..420c4787856
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_outline.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_registers.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_registers.jpg
new file mode 100644
index 00000000000..bc2ee4ebf26
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_registers.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks.jpg
new file mode 100644
index 00000000000..5284ac82218
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks_filter_tasks.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks_filter_tasks.jpg
new file mode 100644
index 00000000000..e7ede1228cb
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks_filter_tasks.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks_new_tasks.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks_new_tasks.jpg
new file mode 100644
index 00000000000..294c6fcfb45
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_tasks_new_tasks.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_variables.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_variables.jpg
new file mode 100644
index 00000000000..9435b70d68f
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_variables.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_variables_customize.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_variables_customize.jpg
new file mode 100644
index 00000000000..bfc696b7b00
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/view_variables_customize.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/window_preferences_c_codetemplates.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/window_preferences_c_codetemplates.jpg
new file mode 100644
index 00000000000..ee85448640b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/window_preferences_c_codetemplates.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/window_preferences_workbench.jpg b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/window_preferences_workbench.jpg
new file mode 100644
index 00000000000..bc1e73b061b
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/images/window_preferences_workbench.jpg
diff --git a/doc/org.eclipse.cdt.doc.user/raw/hackedguide/lnch.html b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/lnch.html
new file mode 100644
index 00000000000..f86b9bbb092
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/raw/hackedguide/lnch.html
@@ -0,0 +1,457 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.ord/TR/html4/loose.dtd">
+<html>
+
+<head>
+
+<title>Starting Your Programs (launcher)</title>
+
+</head>
+<body bgcolor="#ffffff" text="#000000">
+<hr>
+
+
+<h1><a name="id1">Starting Your Programs (launcher)</a></h1>
+
+<p>
+
+
+</p>
+<p>Before running or debugging a program, you must configure how and where to 
+run it, and what options to pass to it. To do all this, you must use the 
+launcher. 
+
+</p>
+<p></p>
+ 
+In this chapter:
+<ul>
+<li><a href="#lnch_works">How the launcher works</a>
+   </li>
+<li><a href="#lnch_diff">Differences between launch configurations</a>
+   </li>
+<li><a href="#lnch_run1">Running and debugging the first time (Launch Configuration dialog)</a>
+   </li>
+<li><a href="#lnch_run2">Running and debugging subsequent times (Launch Configuration dialog)</a>
+   </li>
+<li><a href="#lnch_tabs">Setting execution options (Launch Configuration tabs)</a></li>
+</ul>
+
+<h1><a name="lnch_works">How the launcher works</a></h1>
+
+<p>To run or debug programs with the IDE, you must set up a <i>launch 
+configuration</i>. Launch configurations define which programs to launch, 
+the command-line options to use, and what values to use for environment 
+variables. </p>
+<p>
+
+The IDE saves your launch configurations so you can quickly reproduce the 
+execution conditions by running existing configurations, even if the setup 
+is complicated.</p>
+
+<h1><a name="lnch_diff">Types of launch configurations</a></h1>
+
+<p>The IDE supports these types of launch configurations:
+
+</p>
+<dl>
+
+<dt><b>C/C++ Local</b></dt>
+<dd>If you're developing on your target (self-hosted),  you may create a <b>C/C++ Local</b> launch configuration. You don't need to use <tt>qconn</tt>; the IDE launches your program through <a href="../../neutrino/utilities/g/gdb.html"><tt>gdb</tt></a>.
+
+</dd>
+<dt><b>C/C++ Postmortem debugger</b></dt>
+<dd>If your program produced a corefile (via the <a href="../../neutrino/utilities/d/dumper.html"><tt>dumper</tt></a> utility) when it faulted, you can examine the state of your program by loading it into the postmortem debugger. This option is available only when you select <b>Debug</b>. When you debug, you're prompted with the <b>Select the corefile</b> dialog.
+
+</dd>
+</dl>
+
+</p>
+
+<h1><a name="lnch_run1">Running and debugging the first time (Launch Configurations dialog)</a></h1>
+
+<p>You can use the same launch configuration to run or debug a program. Your choices in the <b>Launch Configurations</b> dialog may 
+cause subtle changes in the dialog but greatly affect such things as which options in the 
+dialog are enabled.
+
+<h2><a name="id6">Enabling the Run and Debug menu items</a></h2>
+
+<p>The <b>Run</b> and <b>Debug</b> menu items appear in the <b>C/C++ Development</b> perspective by default, but they might not appear in all perspectives. It's also possible to remove them. If the <b>Run</b>--><b>Run</b> menu item doesn't appear, you must enable it.
+
+</p>
+<p>To enable the <b>Run</b> and <b>Debug</b> menu items:</p>
+<ol>
+
+<li>From the main menu, select <b>Window</b>--><b>Customize Perspective</b>.
+   The <b>Customize Perspective</b> dialog appears.
+   </li>
+<li>In the left pane, select <b>Other</b>--><b>Launch</b>.
+   </li>
+<li>Enable <b>Launch</b>:
+	<p><img src="./images/lnch_customize.jpg" alt="Launch Configuration dialog; customization">
+   </p></li>
+<li>Click <b>OK</b>.
+   The <b>Run</b>--><b>Run</b> menu item is now accessible in your current perspective.</li>
+</ol>
+
+
+<h2><a name="debug_first">Debugging a program the first time</a></h2>
+
+<p>When you first debug a program, you have to create a launch configuration.</p>
+<p>
+
+To debug a program the first time:</p>
+<ol>
+
+<li>In the <b>C/C++ Projects</b> view (or the <b>Navigator</b> view), select your project.
+   </li>
+<li>From the main menu, select <b>Run</b>--><b>Debug</b> (or, click the <b>Debug</b> icon and select <b>Debug</b> from the dropdown menu):
+	<p><img src="./images/lnch_debug_debug.jpg" alt="Launch Configuration dialog; debugging">
+   </p></li>
+<li>Select a launch configuration type:
+	<p><img src="./images/lnch.jpg" alt="Launch Configuration dialog"></p><p> If you're connecting to your target via IP, select <b>C/C++ QNX QConn (IP)</b>. If not, see  the 
+<a href="#lnch_diff">"Types of Launch Configurations"</a> section in this chapter before deciding:
+
+   </p></li>
+<li>Click <b>New</b>.
+The dialog displays the appropriate tabs
+   </li>
+<li>Enter an appropriate description for your configuration in the <b>Name</b> field.
+   </li>
+<li>Fill in the details in the various tabs. See the <a href="#lnch_tabs">"Setting execution options (Launch Configurations tabs)"</a> section in this chapter for details about each tab.
+   </li>
+<li>Click <b>Debug</b>.
+   You can now debug your program.</li>
+</ol>
+
+
+<h2><a name="id9">Running a program the first time</a></h2>
+
+<p>When you configure a program to run, you should also configure it to debug as well.
+
+</p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>There are fewer options for running programs than for debugging. Some configurations aren't available.</td></tr>
+</table>
+<hr>
+
+
+<p>
+
+To run a program the first time:</p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>Repeat the procedure for debugging a program (see <a href="#debug_first">"Debugging a program the first time"</a>), with the following changes:
+<ul>
+<li>Instead of selecting <b>Run</b>--><b>Debug</b> from the main menu, select <b>Run</b>--><b>Run</b> (or, click the <b>Run</b> icon and select <b>Run</b> from the dropdown menu):
+	<p><img src="./images/lnch_run_run.jpg" alt="Launch Configuration dialog; running">
+   </p></li>
+<li>Instead of clicking <b>Debug</b> when you're done, click <b>Run</b>.
+   </li>
+<li>Instead of running under the control of a debugger, your program runs.</li>
+</ul></td></tr>
+</table>
+
+
+
+<h1><a name="lnch_run2">Running and debugging subsequent times (Launch Configurations dialog)</a></h1>
+
+<p>Once you've created your launch configuration, running or debugging a program is as easy as selecting your previous configuration. There are several ways to do it:</p>
+<ul>
+<li>fast way: see <a href="#fast">"Launching a selected program"</a>
+	</li>
+<li>faster way: see <a href="#faster">"Launching from a list of favorites"</a>
+	</li>
+<li>fastest way: see <a href="#fastest">"Launching the last-launched program"</a></li>
+</ul>
+
+<h2><a name="fast">Launching a selected program</a></h2>
+
+<p>
+
+To debug or run a program that you've created a launch configuration for:</p>
+<ol>
+
+<li>From the main menu, select <b>Run</b>--><b>Debug</b> or <b>Run</b>--><b>Run</b>.
+   The <b>Launch Configurations</b> dialog appears.
+   </li>
+<li>In the left pane, select the launch configuration you created when you first ran or debugged your program.
+   </li>
+<li>Click <b>Debug</b> or <b>Run</b>.
+   </li>
+</ol>
+
+
+<h2><a name="faster">Launching from a list of favorites</a></h2>
+
+<p>If you have a program that you launch frequently, you can add it to the <b>Debug</b> or <b>Run</b> drop-down menu so you can launch it quickly.</p>
+<p></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>To use this method, you must have selected <b>Display in favorites</b> when you first created your Launch Configuration. If you didn't, edit the <b>Display in favorites</b> option under the <b>Common</b> tab. See the <a href="#lnch_tabs">"Setting execution options (Launch Configurations tabs)"</a> section in this  chapter.</td></tr>
+</table>
+<hr>
+
+
+<p>To debug or run a program using your favorites list:</p>
+<ol>
+
+<li>Do one of the following:
+	<ul>
+<li>Run: From the main menu, select <b>Run</b>--><b>Run History</b>.
+	   </li>
+<li>Run: Click the dropdown menu <img src="./images/icon_menu.gif" alt="Icon: Menu dropdown"> part of the run menu button set <img src="./images/icon_run_exc.gif" alt="Icon: Run"><img src="./images/icon_menu.gif" alt="Icon: Menu dropdown">.
+	   </li>
+<li>Debug: From the main menu, select <b>Run</b>--><b>Debug History</b>.
+	   </li>
+<li>Debug: Click the dropdown menu <img src="./images/icon_menu.gif" alt="Icon: Menu dropdown"> part of the debug menu  button set <img src="./images/icon_debug_exc.gif" alt="Icon: Debug"><img src="./images/icon_menu.gif" alt="Icon: Menu dropdown">.
+	</li>
+</ul>
+   A list appears, showing all the launch configurations for which you enabled <b>Display in favorites</b>:
+	<p><img src="./images/lnch_run2_faster.jpg" alt="Launch Configuration dialog; running a program subsequent times (faster)">
+
+   </p></li>
+<li>Select your launch configuration.</li>
+</ol>
+
+
+<h2><a name="fastest">Launching the last-launched program</a></h2>
+
+<p>To relaunch the last program you ran or debugged:</p>
+<p></p>
+
+<table>
+<tr><td valign="top"><img src="image-lib/onestep.gif" alt="=&gt;&gt;"></td>
+<td>Press <font face="Helvetica"><b>F11</b></font> or click one of:
+<ul>
+<li> the <b>Debug Last Launched: <i>yourLaunchName</i></b> button 
+<img src="./images/icon_debug_exc.gif" alt="Icon: Debug">
+	</li>
+<li> the <b>Run Last Launched: <i>yourLaunchName</i></b> 
+<img src="./images/icon_run_exc.gif" alt="Icon:Run"></li>
+</ul></td></tr>
+</table>
+
+
+
+<h1><a name="lnch_tabs">Setting execution options (Launch Configurations tabs)</a></h1>
+
+<p>The <b>Launch Configurations</b> dialog has many tabs, including:</p>
+<p></p>
+<ul>
+<li><a href="#tab_main"><b>Main</b> tab</a>
+	</li>
+<li><a href="#tab_arguments"><b>Arguments</b> tab</a>
+	</li>
+<li><a href="#tab_environment"><b>Environment</b> tab</a>
+	</li>
+<li><a href="#tab_debugger"><b>Debugger</b> tab</a>
+	</li>
+<li><a href="#tab_common"><b>Common</b> tab</a>
+	</li>
+</ul>
+<p>Depending on what type of launch configuration you've selected, only certain tabs appear:</p>
+<p></p>
+<table border=1 width="100%">
+
+<tr>
+<th><b>Launch Configuration</b>
+	</th>
+<th><b>Main</b> tab,<br>
+	<b>Common</b> tab
+	
+	</th>
+<th><b>Arguments</b> tab,<br>
+	<b>Environment</b> tab
+	</th>
+<th><b>Debugger</b> tab
+	</th>
+</tr>
+<tr>
+<td><b>C/C++ Local</b>
+	</td>
+<td>Yes
+	</td>
+<td>Yes
+	</td>
+<td>Yes
+	</td>
+</tr>
+<tr>
+<td><b>C/C++ Postmortem debug</b>***
+	</td>
+<td>Yes
+	</td>
+<td>No
+	</td>
+<td>Yes
+	</td>
+</tr>
+</table>
+
+<p>***<b>Debug</b> only; core file required.</p>
+<p>	
+
+
+</p>
+
+<h2><a name="tab_main">Main tab</a></h2>
+
+<p>This tab lets you specify the project and program that you want to run or debug. The IDE might fill in some of the fields for you:</p>
+<p><img src="./images/lnch_main.jpg" alt="Launch Configurations dialog; Main tab"></p>
+<p>
+
+The <b>Main</b> tab varies, depending on the type of configuration you're creating. If you're creating a <b>C/C++ QNX QConn (IP)</b> launch configuration, you'll see a section for <b>Target Options</b>; for <b>C/C++ PDebug (Serial)</b>, you'll see <b>Serial Options</b>.
+
+</p>
+<dl>
+
+<dt><b>Project</b></dt>
+<dd>Enter the name of your project. You may also select from the open projects by clicking <b>Browse</b>. You can create or edit launch configurations only for open projects.
+
+</dd>
+<dt><b>C/C++ Application</b></dt>
+<dd>Enter the relative path of the executable from the project directory (e.g. <tt>x86/o/KillerApp</tt>).
+For <b>QNX</b> projects, an executable with a <tt>_g</tt> suffix indicates it was compiled for debugging.
+You may also select from the available executables by clicking <b>Search</b>.
+
+</dd>
+<dt><b>Target Options</b></dt>
+<dd>You'll see this section only for <b>C/C++ QNX QConn (IP)</b> launch configurations.
+Select a target from the available list. If you haven't created a target, right-click the empty pane and select <b>Add Target</b>. For more information about creating a target, see the <a href="cwiz.html">Common Wizards</a> chapter.
+
+</dd>
+<dt><b>Filter targets based on C/C++ Application selection</b></dt>
+<dd>Enable this option to hide platforms that don't match your chosen executable. For example, if you've chosen a program compiled for PPC, you'll see only PPC targets.
+
+</dd>
+<dt><b>Serial Options</b></dt>
+<dd>You'll see this section only for <b>C/C++ QNX PDebug (Serial)</b> launch configurations. 
+
+</dd>
+<dt><b>Serial Port</b></dt>
+<dd>Enter the communication port (e.g. <tt>COM1</tt> for Windows; <tt>/dev/ser1</tt> for QNX Neutrino).
+
+</dd>
+<dt><b>Baud Rate</b></dt>
+<dd>Select the baud rate from the dropdown list.</dd>
+</dl>
+
+
+<h2><a name="tab_arguments">Arguments tab</a></h2>
+
+<p>This tab lets you specify the arguments your program uses and the directory where it runs:</p>
+<p><img src="./images/lnch_arguments.jpg" alt="Launch Configurations dialog; Arguments tab">
+
+</p>
+<dl>
+
+<dt><b>C/C++ Program Arguments</b></dt>
+<dd>Enter the arguments that you want to pass on the command line. For example, if you want to send the equivalent of <tt><i>myProgram</i> <tt><b>-v</b></tt> <tt><b>-L 7</b></tt></tt>, type <tt><b>-v -L 7</b></tt> in this field. You can put <tt><b>-v</b></tt> and <tt><b>-L 7</b></tt> on separate lines because the IDE automatically strings the entire contents together.
+
+</dd>
+<dt><b>Working directory</b></dt>
+<dd>Enable <b>Use default working directory</b> to run the executable from the directory where the IDE is running. If you disable <b>Use default working directory</b>, you can specify a full path in the <b>Local directory</b> field or a relative path in the <b>Workspace</b> field.</dd>
+</dl>
+
+
+<h2><a name="tab_environment">Environment tab</a></h2>
+
+<p>The <b>Environment</b> tab lets you set the environment variables and values to use when the program launches:</p>
+<p><img src="./images/lnch_environment.jpg" alt="Launch Configurations dialog; Environment tab"></p>
+<p> For example, if you want to set the environment variable named <b>PHOTON</b> to the value <tt>/dev/photon_2</tt> when you run your program, use this tab. Click <b>New</b> to add an environment variable.</p>
+
+<h2><a name="tab_debugger">Debugger tab</a></h2>
+
+<p>The <b>Debugger</b> tab lets you choose which debugger to use when you debug your program:</p>
+<p><img src="./images/lnch_debugger.jpg" alt="Launch Configurations dialog; Debugger tab"></p>
+
+<hr>
+<table>
+<tr><td valign="top"><img src="image-lib/pointing.gif" alt="Note:"></td>
+<td>The settings in the <b>Debugger</b> tab affect the program only when you debug it, not when you run it.</td></tr>
+</table>
+<hr>
+
+
+<dl>
+
+<dt><b>Debugger</b></dt>
+<dd>The debugger dropdown list includes the available debuggers for the selected launch-configuration type. The list also varies depending on whether you're debugging self-hosted.
+
+</dd>
+<dt><b>Run program in debugger</b>/<b>Attach to running process</b></dt>
+<dd>Most of the time, you'll want to simply <b>Run program in debugger</b>.
+If you enable <b>Attach to running process</b>, you're prompted to select a process from a list at run time. Note the following limitations:
+
+	<ul>
+<li>You can attach only to programs that you launched for debugging.
+	   </li>
+<li>You can't use the <b>Memory Trace</b> tool.
+	</li>
+</ul></dd>
+<dt><b>Stop at main() on startup</b></dt>
+<dd>If you deselect <b>Stop at main() on startup</b>, the program runs until you interrupt it manually, or until it hits a breakpoint.
+
+</dd>
+<dt><b>Debugger Options</b></dt>
+<dd>You'll see this section only for <b>C/C++ Local</b> launch configurations; the IDE already automatically fills in the options for <b>QNX</b> launch configurations.
+
+	<dl>
+
+<dt><b>MI Debugger</b>
+		</dt>
+<dd>You can choose the MI (Machine Interface) Debugger, such as the <tt>gdb</tt> executable.
+
+		</dd>
+<dt><b>Load shared library symbols automatically</b>
+		</dt>
+<dd>If you want to watch line-by-line stepping of library functions in the <b>C Editor</b>, enable this option. You may wish to disable this option if your target doesn't have much memory; the library symbols take up RAM on the target. It's enabled by default.
+	</dd>
+</dl>
+</dd>
+</dl>
+
+
+<h2><a name="tab_common">Common tab</a></h2>
+
+<p>The <b>Common</b> tab lets you define where the launch configuration is stored, how you access it, and what perspective you change to when you launch:</p>
+<p><img src="./images/lnch_common.jpg" alt="Launch Configurations dialog; Common tab">
+
+
+</p>
+<dl>
+
+<dt><b>Type of launch configuration</b></dt>
+<dd>When you create a launch configuration, the IDE saves it as a <tt>.launch</tt> file. If you select <b>Local</b>, the IDE stores the configuration in one of its own plugin directories. If you select <b>Shared</b>, you can save it in a location you specify (such as in your project). Saving as <b>Shared</b> lets you commit the <tt>.launch</tt> file to CVS so your coworkers can run the program using the same configuration.
+
+</dd>
+<dt><b>Perspective to switch to or open when launched in</b></dt>
+<dd>You can configure which perspectives the IDE changes to when you run or debug. You can set the perspectives specifically, or simply set them to <b>Default</b>. To determine the default perspectives for both, select <b>Window</b>--><b>Preferences</b> from the main menu and select <b>Debug</b> from the left pane.
+
+</dd>
+<dt><b>Display in favorites</b></dt>
+<dd>You can have your launch configuration displayed when you click the <b>Run</b> or <b>Debug</b> dropdown menus. To do so, enable <b>Run</b> or <b>Debug</b> under the <b>Display in favorites menu:</b> heading.</dd>
+</dl>
+
+</body>
+
+</html>
+
+<!--
+/**********************************************************************
+ * Copyright (c) 2002,2003 QNX Software Systems Ltd. and others.
+ * All rights reserved.   This program and the accompanying materials
+ * are made available under the terms of the Common Public License v0.5
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/cpl-v05.html
+ * 
+ * Contributors: 
+ * QNX Software Systems - Initial API and implementation
+***********************************************************************/
+-->
author	Sebastien Marineau	2003-06-13 22:29:43 +0000
committer	Sebastien Marineau	2003-06-13 22:29:43 +0000
commit	e380c8ea03d2ea2f35fe4fee83a8a1cb75afc4de (patch)
tree	c5293e694b9cb530f968365f06e9eb2763ee8535 /doc
parent	22eb93f0e4b6acccdca274b53db680aee2be910d (diff)
download	org.eclipse.cdt-e380c8ea03d2ea2f35fe4fee83a8a1cb75afc4de.tar.gz org.eclipse.cdt-e380c8ea03d2ea2f35fe4fee83a8a1cb75afc4de.tar.xz org.eclipse.cdt-e380c8ea03d2ea2f35fe4fee83a8a1cb75afc4de.zip