Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PTP/environment setup 21"

< PTP
(= Install Eclipse)
(Configure CVS Access)
Line 22: Line 22:
 
=== Configure CVS Access ===
 
=== Configure CVS Access ===
  
Switch to the CVS perspective and create a new repository location:
+
# Switch to the CVS perspective and create a new repository location:
* Host: dev.eclipse.org
+
#* Host: dev.eclipse.org
* Repository path:  /cvsroot/tools
+
#* Repository path:  /cvsroot/tools
* User: <yourCommitterID>  or anonymous
+
#* User: <yourCommitterID>  or anonymous
* Password: <yourPW> or empty for anonymous access
+
#* Password: <yourPW> or empty for anonymous access
* Connection type: extssh for committer access, or pserver for anonymous access
+
#* Connection type: extssh for committer access, or pserver for anonymous access
 
+
# After creating the repository location, expand it and expand HEAD.  All the PTP content is under '''org.eclipse.ptp'''.
After creating the repository location, expand it and expand HEAD.  All the PTP content is under '''org.eclipse.ptp'''.
+
 
+
<b>Note:</b> PTP 2.0 code is now under the PTP_2_0 branch, since PTP 2.1 is now under development.  See http://wiki.eclipse.org/index.php/CVS_FAQ#Browsing_the_Repository
+
for info on using branches (or see example below). You should be able to download the project set files from these links and use them from the branch, rather than from HEAD.
+
<p>For example, to make the PTP 2.0 tags appear, do the following:</p>
+
<ol>
+
      <li>Open the CVS Repositories view for dev.eclipse.org as described above.</li>
+
      <li>Expand HEAD and select the project (org.eclipse.ptp) for which you want to configure tags.</li>
+
      <li>Context Menu-&gt;Configure Branches and Versions...</li>
+
      <li>In the "Browse files for tags" table, select one or more files that contain tags you would like to see.
+
<ul><li>For example, in the left pane under 'Browse files for tags:' expand 'core' and select  the '.project' file</li>
+
        <li>Check the tag 'ptp_2_0' branch tag shown in the right pane (or the 'PTP_2_0_1' version tag)</li>
+
</ul>
+
</li>
+
      <li>Click "Add Checked Tags"</li>
+
      <li>Click "OK". The CVS Repositories view will now display the chosen tags under the Branches and Versions categories. </li>
+
</ol>
+
  
 
=== Checkout PTP Plugins ===
 
=== Checkout PTP Plugins ===

Revision as of 12:45, 18 March 2009

Prerequisites

  1. Eclipse 3.4 (Ganymede)
  2. CDT 5.0
  3. To run full PTP parallel application monitoring/debugging: Linux or Mac OS X, and OpenMPI
  4. To run/debug remote applications, and/or run only PLDT analysis, OpenMPI isn't required, and all should work on Windows

Install steps

Install Eclipse

  1. Install Ganymede - download directly from http://download.eclipse.org/eclipse/downloads/ - choose 3.4, latest version, full SDK
  2. Download CDT 5.0 - get the latest e.g. from http://download.eclipse.org/tools/cdt/builds - save the cdt-master file, to use in software update steps below
  3. Launch Eclipse (Ganymede)
  4. Install CDT from the update manager:
    1. Help > Software Updates ...
    2. Make sure 'Available Software' is selected at the top
    3. Click Add site, archive, and locate the cdt-master-whatever-zip you downloaded above; hit OK
    4. Select at least the 3 items under CDT Main features (make sure they are checked)
    5. Click Install ... Next, Accept, Finish
  5. Install RSE from the update manager:

Configure CVS Access

  1. Switch to the CVS perspective and create a new repository location:
    • Host: dev.eclipse.org
    • Repository path: /cvsroot/tools
    • User: <yourCommitterID> or anonymous
    • Password: <yourPW> or empty for anonymous access
    • Connection type: extssh for committer access, or pserver for anonymous access
  2. After creating the repository location, expand it and expand HEAD. All the PTP content is under org.eclipse.ptp.

Checkout PTP Plugins

The easiest way to do this is to import using team project sets. The following table summarizes the available sets in the releng/ptp_project_sets project:

Project Set Contents Committer Access Anonymous Access
Core PTP Plugins (required) ptp-2.0-committer.psf ptp-2.0-anonymous.psf
Resource Manager Plugins (required) ptp-rms-2.0-committer.psf ptp-rms-2.0-anonymous.psf
Remote Tools Plugins (optional) ptp-remotetools-2.0-committer.psf ptp-remotetools-2.0-anonymous.psf
RSE Support Plugins (optional) ptp-rse-2.0-committer.psf ptp-rse-2.0-anonymous.psf
Parallel Language Development Tools (optional) ptp-pldt-2.0-committer.psf ptp-pldt-2.0-anonymous.psf

Use the files in the Committer Access column if you are a committer. Otherwise, use the files in the Anonymous Access column. At a minimum you will need the Core PTP Plugins and the Resource Manager Plugins. You will also need either (or both of) the Remote Tools Plugins or the RSE Support Plugins (assuming you installed RSE). If you are working on the PLDT (or want to run it from your runtime workbench) then download this project set file also.

You can download the files directly from the above links. They aren't checked into the branch itself.

  • NOTE: there is a problem, the following instructions should work, but this gets the projects from HEAD. need to figure out how to modify the project sets files... Or... just look in the files to see which projects to check out manually from the PTP_2_0 branch.
  1. Download each psf file, save it somewhere within an eclipse project (e.g. make a new "ptp_project_sets" project),
  2. right click on the file and select Import Project Set ..., enter anonymous as userid.
  3. The projects will be checked out and created in your workspace.


You should now have all the plug-in projects in your workspace.

Launching a runtime workbench running the code you checked out into your workspace

  1. Run > Debug Configurations ...
  2. Double-click on 'Eclipse Application' - or click and click on the 'new' icon
  3. Defaults are probably ok to run with all the plugin projects in your workspace; hit 'Debug' in lower right corner
  4. Eclipse comes up. Switch to C/C++ perspective if needed
  5. For details on creating an MPI or OpenMP project, see Help > Help Contents ...

Back to the top