Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/icon_edit_settings.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/run_mode_debug_01.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/run_mode_debug_02.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/run_mode_debug_05.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/run_mode_debug_06.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/run_mode_debug_07.png has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/run_mode_debug_example_00.htm Fri Jul 16 14:42:52 2010 -0500
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Debugging on Remote Targets (Run-mode) Tutorial</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Debugging on Remote Targets (Run-mode) Tutorial</h2>
+<p>In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:</p>
+<ol>
+ <li><a href="run_mode_debug_example_01.htm">Connect</a> target device for PC</li>
+ <li><a href="../trk/trk_installation_instr.htm">Install </a>TRK v3.2.6 remote agent or later on the target device</li>
+ <li><a href="run_mode_debug_example_04.htm">Configure</a> project for debugging</li>
+ <li><a href="run_mode_debug_example_05.htm">Debug</a> project on target device</li>
+</ol>
+<h4>Other references</h4>
+<ul>
+ <li><a href="new_proj_from_template_00.htm">Creating and Debugging New Projects Tutorial</a></li>
+ <li><a href="new_proj_dll_example_00.htm">Creating and Debugging DLL Projects Tutorial</a></li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/run_mode_debug_example_01.htm Fri Jul 16 14:42:52 2010 -0500
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Connect target device to PC Tutorial</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2><strong>Connect target device to PC</strong></h2>
+<p>In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:</p>
+<ol>
+ <li><strong>Connect target device to PC</strong></li>
+ <li><a href="../trk/trk_installation_instr.htm">Install </a>TRK remote agent (v3.2.6) or later on the target device</li>
+ <li><a href="run_mode_debug_example_04.htm">Configure</a> project for debugging</li>
+ <li><a href="run_mode_debug_example_05.htm">Debug</a> project on target device</li>
+ </ol>
+<hr>
+<p>The most reliable connection between a remote device and your PC is a cable. In this case, the USB cable that physically connects your phone to the a PC USB connection. Once connected, Carbide uses plug-and-play (PnP) to create a remote connection to the phone or remote device.</p>
+<p class="note"><strong>NOTE</strong> This tutorial assumes that Carbide is setup properly enabling you to create, build, and debug applications with an emulator.</p>
+<div class="step">
+ <h4 align="left">Connecting remote devices to PC</h4>
+ <ol>
+ <li>Connect the USB cable between the remote device and PC running Carbide.<br />
+ <p>Use the <strong>Remote Connections</strong> view to verify a successful connection or by looking at the remote connection trim display shown at the bottom of the workplace window.</p>
+ <p><img src="../images/run_mode_debug_01.png" alt="Remote Connection view"> <img src="../images/run_mode_debug_02.png" alt="Remote Connection trim indicator"></p>
+ <p>The <strong>Status</strong> column indicates whether the service you need for debugging, TRK, is <strong>Available</strong>. If it's status is <strong>Not Accessible</strong> you are probably missing the TRK remote agent on the remote device.</p>
+ </li>
+ <li>Click OK on the remote device when it asks to use PC Suite mode with USB.<br />
+ <p class="note"><strong>NOTE</strong> Debugging requires the use of PC Suite mode. If you are in another mode, like Mass storage mode, an alert appears asking you to change.</p>
+ </li>
+ </ol>
+</div>
+<p><strong>NEXT</strong>: <a href="run_mode_debug_example_02.htm">Install TRK remote agent</a></p>
+<h4>Other references</h4>
+<ul>
+ <li><a href="run_mode_debug_example_00.htm">Debugging on Remote Targets (Run-mode) Tutorial</a></li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/run_mode_debug_example_02.htm Fri Jul 16 14:42:52 2010 -0500
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Install TRK remote agent Tutorial</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/></head>
+<body bgcolor="#FFFFFF">
+<h2>Install TRK remote agent</h2>
+<p>In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:</p>
+<ol>
+ <li><a href="run_mode_debug_example_01.htm">Connect</a> target device to PC</li>
+ <li><strong>Install TRK remote agent (v3.2.6) or later on the target device</strong></li>
+ <li><a href="run_mode_debug_example_03.htm">Configure</a> project for debugging</li>
+ <li><a href="run_mode_debug_example_04.htm">Debug</a> project on target device</li>
+ </ol>
+<hr>
+<p>To debug on a remote device you need a program to communicate between the Carbide debugger and your executable running on the device. That program is the <strong>TRK</strong> (Terminal Resident Kernel) remote agent, also known as <strong>Application TRK</strong>. </p>
+<p> </p>
+<div class="step">
+ <h4>Installing or updating the TRK remote agent</h4>
+ <ol>
+ <li>Select the Connection to edit in the Remote Connections view.</li>
+ <li>Click the Edit Settings... icon (<img src="../images/icon_edit_settings.png" alt="Edit Settings icon" width="17" height="17" align="absmiddle">) in the Remote Connections toolbar.<br />
+ <p><img src="../images/run_mode_debug_05.png" alt="Click Edit Settings icon"></p>
+ </li>
+ <li>Click the Install Remote Agents tab. <br />
+ <p><img src="../images/run_mode_debug_06.png" alt="Click Install Remote Agents tab"></p>
+ </li>
+ <li>Select the latest remote agent to install.<br />
+ <p>Choose the remote agent to install. Since there are different builds for different OSes, knowing the OS installed on the device helps. </p>
+ </li>
+ <p><img src="../images/run_mode_debug_07.png" alt="Click Install Remote Agents tab"></p>
+ <p class="note"><strong>NOTE</strong> If you don't know what OS version is on the device, always choose the remote agent that supports the highest OS version available. Should that one not work, drop down to the next OS version in line and repeat.</p>
+ <li>
+ <p>Click <strong>Install</strong>.</p>
+ </li>
+ </ol>
+</div>
+<p><strong>NEXT:</strong> <a href="run_mode_debug_example_03.htm">Configure project for debugging</a></p>
+<h4>Other references</h4>
+<ul>
+ <li><a href="run_mode_debug_example_00.htm">Debugging on Remote Targets (Run-mode) Tutorial</a></li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/run_mode_debug_example_03.htm Fri Jul 16 14:42:52 2010 -0500
@@ -0,0 +1,31 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Configure project for debugging Tutorial</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Configure project for debugging</h2>
+<p>In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:</p>
+<ol>
+ <li><a href="run_mode_debug_example_01.htm">Connect</a> target device to PC</li>
+ <li><a href="../trk/trk_installation_instr.htm">Install </a>TRK remote agent (v3.2.6) or later on the target device</li>
+ <li><strong>Configure project for debugging</strong></li>
+ <li><a href="run_mode_debug_example_05.htm">Debug</a> project on target device</li>
+ </ol>
+<hr>
+<p> </p>
+<p><strong>Configure project for debugging</strong></p>
+<p> </p>
+<p><strong>NEXT:</strong> <a href="run_mode_debug_example_04.htm">Debug project on target device</a></p>
+<h4>Other references</h4>
+<ul>
+ <li><a href="run_mode_debug_example_00.htm">Debugging on Remote Targets (Run-mode) Tutorial</a></li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/run_mode_debug_example_04.htm Fri Jul 16 14:42:52 2010 -0500
@@ -0,0 +1,29 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Debug project on target device Tutorial</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Debug project on target device</h2>
+<p>In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:</p>
+<ol>
+ <li><a href="run_mode_debug_example_01.htm">Connect</a> target device to PC</li>
+ <li><a href="../trk/trk_installation_instr.htm">Install</a> TRK remote agent (v3.2.6) or later on the target device</li>
+ <li><a href="run_mode_debug_example_04.htm">Configure</a> project for debugging</li>
+ <li><a href="run_mode_debug_example_05.htm">Debug</a> project on target device</li>
+ </ol>
+<hr>
+<p> </p>
+<p> </p>
+<h4>Other references</h4>
+<ul>
+ <li><a href="run_mode_debug_example_00.htm">Debugging on Remote Targets (Run-mode) Tutorial</a></li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm Fri Jul 16 14:41:18 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm Fri Jul 16 14:42:52 2010 -0500
@@ -1,30 +1,30 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Installing PERL</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Installing PERL</h2>
-<p>PERL is required for many Symbian OS utilities and commands.</p>
-<div class="step">
-<h4><a name="runPerl" id="runPerl"> </a>Installing PERL</h4>
-<ul>
- <li>Install ActivePERL version 5.6.1 b638</li>
-</ul>
-<blockquote>
- <p>Software can be downloaded from: <a href="http://www.activestate.com/Products/ActivePerl/">http://www.activestate.com/Products/ActivePerl/</a>.</p>
- <p class="note"><b>NOTE</b> Later releases of Perl are not yet supported by the Symbian utilities and can cause unknown compiling errors. </p>
- </blockquote>
-</div>
-<h5>Other references</h5>
-<ul>
- <li><a href="run_mode_debug.htm">Run Mode On-Device Debugging</a></li>
-</ul>
-<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Installing Perl</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Installing Perl</h2>
+<p><a href="http://en.wikipedia.org/wiki/Perl">Perl</a> is a high-level, general-purpose, interpreted, dynamic programming language which many Symbian OS build utilities and commands require.</p>
+<div class="step">
+<h4><a name="runPerl" id="runPerl"> </a>Installing Perl</h4>
+<ul>
+ <li>Download and install ActivePerl version 5.6.1 b638</li>
+</ul>
+<blockquote>
+ <p>Software can be downloaded from: <a href="http://www.activestate.com/Products/ActivePerl/">http://www.activestate.com/Products/ActivePerl/</a>.</p>
+ <p class="note"><b>NOTE</b> Later releases of Perl are not yet supported by the Symbian utilities and can cause unknown compiling errors. </p>
+ </blockquote>
+</div>
+<h5>Other references</h5>
+<ul>
+ <li><a href="../../projects/tutorials/run_mode_debug_example_01.htm">Verify System Setup (Run-mode) Tutorial</a></li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Fri Jul 16 14:41:18 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Fri Jul 16 14:42:52 2010 -0500
@@ -1,61 +1,59 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Installing an SDK</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Installing an SDK</h2>
-<p>To create projects an SDK must be installed. If more than one SDK is installed one must be specified as the default.</p>
-<div class="step">
-<h4><a name="runSDK" id="runSDK"> </a>Installing an SDK</h4>
-<p>The following SDKs can be downloaded from Nokia at: <a href="http://www.forum.nokia.com/Tools_Docs_and_Code/">http://www.forum.nokia.com/</a>.</p>
-<ol>
- <li>Install at least one of the following SDKs using the install directions that accompany the SDK:
- <ul>
- <li>Series 60 5.0</li>
- <li>Qt for S60</li>
- <li>Series80</li>
- <li>Series 60 cust kits</li>
- <li>Techview Development kits</li>
- </ul>
- </li>
- <li>Set the default SDK to use for projects
- <ol type="A">
- <li>In Carbide.c++
- <ol type="i">
- <li>Click Window > Preferences > Carbide.c++ > SDK Preferences to open the SDK Preferences panel</li>
- <li>Select the SDK and click SDK Properties to open the SDK Properties dialog</li>
- <li>Set the Default SDK value to Yes</li>
- <li>Close all the dialogs</li>
- </ol>
- </li>
- <li>In a command-line prompt:
- <ol type="i">
- <li>Set the default device devkit by typing on the command line:<br>
- <br />
- > <span class="code">devices –setdefault @device id: name</span></li>
- <p>The device id and name can be found in the devices.xml file. For example, for a Techview 9.2 kit you might type<br>
- <br />
- <span class="code">> devices –setdefault @ SymbianOS_92_2006_wk40:com.symbian.techview</span></p>
- <li>Now ensure the default device is set by entering:<br>
- <br />
- > <span class="code">devices</span></li>
- </ol>
- </li>
- <li>Make sure the correct SDK default is set.</li>
- </ol>
- </li>
- </ol>
- </div>
-
-<h5>Other references</h5>
-<ul>
- <li><a href="run_mode_debug.htm">Run Mode On-Device Debugging</a> </li>
-</ul>
-<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Installing an SDK</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Installing an SDK</h2>
+<p>To create projects an SDK must be installed. If more than one SDK is installed one must be specified as the default.</p>
+<div class="step">
+<h4><a name="runSDK" id="runSDK"> </a>Installing an SDK</h4>
+<p>The following SDKs can be downloaded from Nokia at: <a href="http://www.forum.nokia.com/Tools_Docs_and_Code/">http://www.forum.nokia.com/</a>.</p>
+<ol>
+ <li>Install at least one of the following SDKs using the install directions that accompany the SDK:
+ <ul>
+ <li>Nokia Symbian^3</li>
+ <li>Nokia Qt for SDK 1.0</li>
+ <li>S60 5th Edition v1.0</li>
+ </ul>
+ </li>
+ <li>Set the default SDK to use for projects
+ <ol type="A">
+ <li>In Carbide.c++
+ <ol type="i">
+ <li>Click Window > Preferences > Carbide.c++ > SDK Preferences to open the SDK Preferences panel</li>
+ <li>Select the SDK and click SDK Properties to open the SDK Properties dialog</li>
+ <li>Set the Default SDK value to Yes</li>
+ <li>Close all the dialogs</li>
+ </ol>
+ </li>
+ <li>In a command-line prompt:
+ <ol type="i">
+ <li>Set the default device devkit by typing on the command line:<br>
+ <br />
+ > <span class="code">devices –setdefault @device id: name</span></li>
+ <p>The device id and name can be found in the devices.xml file. For example, for a Techview 9.2 kit you might type<br>
+ <br />
+ <span class="code">> devices –setdefault @ SymbianOS_92_2006_wk40:com.symbian.techview</span></p>
+ <li>Now ensure the default device is set by entering:<br>
+ <br />
+ > <span class="code">devices</span></li>
+ </ol>
+ </li>
+ <li>Make sure the correct SDK default is set.</li>
+ </ol>
+ </li>
+ </ol>
+</div>
+
+<h5>Other references</h5>
+<ul>
+ <li><a href="../../projects/tutorials/run_mode_debug_example_01.htm">Verify System Setup (Run-mode) Tutorial</a><a href="run_mode_debug.htm"></a> </li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_03.htm Fri Jul 16 14:41:18 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_03.htm Fri Jul 16 14:42:52 2010 -0500
@@ -1,49 +1,49 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Configuring Environment Variables</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Configuring Environment Variables</h2>
-<p>To implement run mode on-device debugging the following tasks need to be completed.</p>
-<div class="step">
-<h4><a name="runEnvVars" id="runEnvVars"> </a>Configuring Environment Variables</h4>
-<ol>
- <li>Set EPOCROOT variable
- <ol type="a">
- <li>Right click on My Computer and select Properties</li>
- <li>Select the Advanced tab</li>
- <li>Select the Environmental Variables button</li>
- <li>Setup a new System variable called EPOCROOT. The value will depend on the path of the epoc32 folder in the kit, for example: </li>
- <p>Variable name: <span class="code">EPOCROOT</span><br />
- Variable value: <span class="code">\bin\techview\</span></p>
- </ol>
- </li>
- <p class="note"><b>NOTE</b> Take note of the location of the epoc32 folder when using multiple kits. Some kits place the epoc32 folder at \bin\techview\ and some kits will place it at the root. If you have multiple installations and switch to a new kit, you will need to change the EPOCROOT path; otherwise build problems may occur. When building the ROM image, scripts may complain about the EPOCROOT path or that it can’t find bldmake.bat if an incorrect EPOCROOT path is set.</p>
- <li>Set Path to Tools Directory
- <ol type="a">
- <li>If using an installer the tools path is set up automatically and points to:</li>
- Variable: <span class="code">PATH</span><br>
- Value: <span class="code">C:\Program Files\Common Files\Symbian\Tools</span>
- <li>If installing from zip files you will need to setup the tools path manually. Add the path to the beginning of the PATH variable:</li>
- Variable: <span class="code">PATH</span><br />
- Variable Value: <span class="code">\epoc32\tools;\epoc32\gcc\bin;</span>
- <li>If using multiple kits that use a mix of installer and zip files then you can set up your PATH variable like this:</li>
- Variable: <span class="code">PATH</span><br />
- Value: <span class="code">\epoc32\tools;\epoc32\gcc\bin;C:\Program Files\Common Files\Symbian\Tools</span>
- </ol>
- </li>
- </ol>
-</div>
-<h5>Other references</h5>
-<ul>
- <li><a href="run_mode_debug.htm">Run Mode On-Device Debugging</a> </li>
-</ul>
-<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Configuring Environment Variables</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Configuring Environment Variables</h2>
+<p>To implement run mode on-device debugging the following tasks need to be completed.</p>
+<div class="step">
+<h4><a name="runEnvVars" id="runEnvVars"> </a>Configuring Environment Variables</h4>
+<ol>
+ <li>Set EPOCROOT variable
+ <ol type="a">
+ <li>Right click on My Computer and select Properties</li>
+ <li>Select the Advanced tab</li>
+ <li>Select the Environmental Variables button</li>
+ <li>Setup a new System variable called EPOCROOT. The value will depend on the path of the epoc32 folder in the kit, for example: </li>
+ <p>Variable name: <span class="code">EPOCROOT</span><br />
+ Variable value: <span class="code">\bin\techview\</span></p>
+ </ol>
+ </li>
+ <p class="note"><b>NOTE</b> Take note of the location of the epoc32 folder when using multiple kits. Some kits place the epoc32 folder at \bin\techview\ and some kits will place it at the root. If you have multiple installations and switch to a new kit, you will need to change the EPOCROOT path; otherwise build problems may occur. When building the ROM image, scripts may complain about the EPOCROOT path or that it can’t find bldmake.bat if an incorrect EPOCROOT path is set.</p>
+ <li>Set Path to Tools Directory
+ <ol type="a">
+ <li>If using an installer the tools path is set up automatically and points to:</li>
+ Variable: <span class="code">PATH</span><br>
+ Value: <span class="code">C:\Program Files\Common Files\Symbian\Tools</span>
+ <li>If installing from zip files you will need to setup the tools path manually. Add the path to the beginning of the PATH variable:</li>
+ Variable: <span class="code">PATH</span><br />
+ Variable Value: <span class="code">\epoc32\tools;\epoc32\gcc\bin;</span>
+ <li>If using multiple kits that use a mix of installer and zip files then you can set up your PATH variable like this:</li>
+ Variable: <span class="code">PATH</span><br />
+ Value: <span class="code">\epoc32\tools;\epoc32\gcc\bin;C:\Program Files\Common Files\Symbian\Tools</span>
+ </ol>
+ </li>
+ </ol>
+</div>
+<h5>Other references</h5>
+<ul>
+ <li><a href="../../projects/tutorials/run_mode_debug_example_01.htm">Verify System Setup (Run-mode) Tutorial</a><a href="run_mode_debug.htm"></a> </li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_04.htm Fri Jul 16 14:41:18 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_04.htm Fri Jul 16 14:42:52 2010 -0500
@@ -1,35 +1,35 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Setup a Virtual Drive for Techview and Cust Kits</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Setup a Virtual Drive for Techview and Cust Kits (optional)</h2>
-<p>Techview Kits and cust kits have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.</p>
-<div class="step">
- <h4><a name="runVirDrive" id="runVirDrive"> </a>Setup a Virtual Drive for Techview and Cust Kits</h4>
- <ol>
- <li>To subst a drive, type on a command line:<br />
- > subst <span class="question">drive_letter:</span> <span class="question">path_to_kit<br />
- </span>For example:<br />
-><span class="code"> subst M: C:\Symbian\S60_3_0_200626</span></li>
- <li>On the command line type:<br />
-><span class="code">subst</span><br />
- <p>You should see the new virtual drive pointing to your kit. If the debugger tries to load a file it can’t find, it will look for it on the virtual drive. You can see this in the stack crawl. The stack crawl should give the full path of the file on the virtual drive the file was built on. The debugger will not be able to load the file until the correct virtual drive is specified.</p>
- <p>If this happens you can redo the virtual drive to use the drive specified in the stack crawl or navigate to the file using the existing virtual drive. From that point the IDE will add that path and recursively check folders for files it needs.</p>
- </li>
- <li>Make sure when you set up your default SDK in the Carbide IDE that you use the virtual drive.</li>
- </ol>
-</div>
-<h5>Other references</h5>
-<ul>
- <li><a href="run_mode_debug.htm">Run Mode On-Device Debugging</a> </li>
-</ul>
-<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Setup a Virtual Drive</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Setup a Virtual Drive (optional)</h2>
+<p>SDKs have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.</p>
+<div class="step">
+ <h4><a name="runVirDrive" id="runVirDrive"> </a>Setup a Virtual Drive for SDKs</h4>
+ <ol>
+ <li>To subst a drive, type on a command line:<br />
+ > subst <span class="question">drive_letter:</span> <span class="question">path_to_kit<br />
+ </span>For example:<br />
+><span class="code"> subst M: C:\Symbian\S60_5_0_201012</span></li>
+ <li>On the command line type:<br />
+><span class="code">subst</span><br />
+ <p>You should see the new virtual drive pointing to your kit. If the debugger tries to load a file it can’t find, it will look for it on the virtual drive. You can see this in the stack crawl. The stack crawl should give the full path of the file on the virtual drive the file was built on. The debugger will not be able to load the file until the correct virtual drive is specified.</p>
+ <p>If this happens you can redo the virtual drive to use the drive specified in the stack crawl or navigate to the file using the existing virtual drive. From that point the IDE will add that path and recursively check folders for files it needs.</p>
+ </li>
+ <li>Make sure when you set up your default SDK in the Carbide IDE that you use the virtual drive.</li>
+ </ol>
+</div>
+<h5>Other references</h5>
+<ul>
+ <li><a href="../../projects/tutorials/run_mode_debug_example_01.htm">Verify System Setup (Run-mode) Tutorial</a><a href="run_mode_debug.htm"></a> </li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
Binary file core/com.nokia.carbide.cpp/themes/carbide/graphics/icons/obj48/c3_new.png has changed
Binary file core/com.nokia.carbide.cpp/themes/carbide/graphics/icons/obj48/c3_new_hover.png has changed
