Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoreutarass2008-02-21 18:25:18 -0500
committereutarass2008-02-21 18:25:18 -0500
commit521178c66ba2989ab837a9d7bb1c4a75216cfde2 (patch)
tree712d92bd8ef1fd4860d8f56f8a9b905bb2f216c8 /docs/TCF Getting Started.html
parent39964814a5c76b9c259bb2f670cb84e4d299abef (diff)
downloadorg.eclipse.tcf-521178c66ba2989ab837a9d7bb1c4a75216cfde2.tar.gz
org.eclipse.tcf-521178c66ba2989ab837a9d7bb1c4a75216cfde2.tar.xz
org.eclipse.tcf-521178c66ba2989ab837a9d7bb1c4a75216cfde2.zip
In order to comply with naming conventions at Eclipse, plugins, packages, etc. are renamed from com.windriver.* to org.eclipse.tm.*
Copyright notices are updated to include year 2008.
Diffstat (limited to 'docs/TCF Getting Started.html')
-rwxr-xr-xdocs/TCF Getting Started.html23
1 files changed, 13 insertions, 10 deletions
diff --git a/docs/TCF Getting Started.html b/docs/TCF Getting Started.html
index 05d2ed32a..07dd570d0 100755
--- a/docs/TCF Getting Started.html
+++ b/docs/TCF Getting Started.html
@@ -51,8 +51,8 @@ below are steps to create and populate Eclipse workspace with TCF projects:</p>
<li>Select root directory: &lt;TCF Root&gt;\plugins, and click "Next".<ul>
<li>If DD-DSF and/or CDT are not installed, don't import the following two plugins
into your workspace:<ul>
- <li>com.windriver.tcf.dsf.core
- <li>com.windriver.tcf.dsf.ui
+ <li>org.eclipse.tm.tcf.dsf
+ <li>org.eclipse.tm.tcf.dsf.ui
</ul></li>
</ul></li>
<!--
@@ -90,22 +90,22 @@ below are steps to create and populate Eclipse workspace with TCF projects:</p>
<p>TCF plugins source code is stored in <code>&lt;TCF Root&gt;\plugins</code> directory.
<dl>
- <dt><b>com.windriver.tcf.api</b>
+ <dt><b>org.eclipse.tm.tcf</b>
<dd>This is the main TCF plugin. It contains the framework itself and interfaces for standard services.
It is the only TCF plugin, which should be required by a TCF client. The rest of TCF plugins are
clients developed as a reference implementation or for demonstration purposes.
<p>
- <dt><b>com.windriver.debug.tcf.core,com.windriver.debug.tcf.ui</b>
+ <dt><b>org.eclipse.tm.tcf.debug, org.eclipse.tm.tcf.debug.ui</b>
<dd>This is a prototype code that connects Eclipse Debug Framework and Target Communication Framework.
It allows to launch Eclipse debug session by connecting to a target running TCF agent,
and then perform basic debugging tasks, like resuming, suspending, single-stepping, setting/removing breakpoints, etc.
The code can be used as a reference for developing new TCF clients.
<p>
- <dt><b>com.windriver.tcf.dsf.core,com.windriver.tcf.dsf.ui</b>
+ <dt><b>org.eclipse.tm.tcf.dsf, org.eclipse.tm.tcf.dsf.ui</b>
<dd>This code allows Debugger Services Framework (DSF) clients to access targets using TCF as comminucation protocol.
It includes implementation of DSF services as TCF clients.
<p>
- <dt><b>com.windriver.tcf.rse.ui</b>
+ <dt><b>org.eclipse.tm.tcf.rse</b>
<dd>This plugin allows Remote System Explorer (RSE) to connect to remote machines using TCF as communication protocol.
It includes implementation of RSE services as TCF clients.
</dl>
@@ -154,8 +154,11 @@ following changes in settings may be necessary:<ul>
<p>On <b>VxWorks</b>, the file service as well as most debug services are currently
working. Line number mapping and the SysMonitor service (required for RSE Processes
Demo) are not yet implemented.<br/>
-To build the agent: Use Wind River Workbench to create a Kernel Module project out of source code in
-<code>&lt;TCF Root&gt;/agent</code> directory. Use Workbench commands to build and run the agent.</p>
+To build the agent: Use Wind River Workbench 3.0 and VxWorks 6.6 to create a Kernel Module
+project out of source code in <code>&lt;TCF Root&gt;/agent</code> directory. Use Workbench
+commands to build and run the agent. To run the agent on VxWorks Simulator
+you will need to setup a simulated network - see Networking with the VxWorks Simulator chapter
+in Wind River VxWorks Simulator user's guide for details.</p>
<h2><a name='Browsing'>Browsing Agent Source Code in CDT</a></h2>
On Linux, the default configuration from the CDT .project file included in TCF
@@ -176,7 +179,7 @@ explore their file systems, see list of processes and access some other resource
Remote System Explorer has been designed as a flexible, extensible framework to which Eclipse plug-in developers can
contribute their own system definitions, actions, etc.</p>
-<p>Plugin <b>com.windriver.tcf.rse.ui</b> enables use of Processes and Files subsystems of Remote System Explorer over TCF.
+<p>Plugin <b>org.eclipse.tm.tcf.rse</b> enables use of Processes and Files subsystems of Remote System Explorer over TCF.
It also extends Processes subsystem to include CPU utilization data and some other process attributes in RSE views.</p>
<p>To connect a remote machine over TCF:</p>
@@ -199,7 +202,7 @@ It also extends Processes subsystem to include CPU utilization data and some oth
<h2><a name='Debugger'>Using TCF With Eclipse Debugger</a></h2>
-<p>Plugins <b>com.windriver.debug.tcf.core</b> and <b>com.windriver.debug.tcf.ui</b> allow to start a debug session
+<p>Plugins <b>org.eclipse.tm.tcf.debug</b> and <b>org.eclipse.tm.tcf.debug.ui</b> allow to start a debug session
by connecting to a machine runnning TCF agent. This is not a complete debugger implementation, it is intended for
demo and reference purposes.

Back to the top