Jump to: navigation, search

PTP/environment setup 20

< PTP
Revision as of 16:03, 8 December 2008 by Tibbitts.us.ibm.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Prerequisites

The following are the minimum requirements for developing PTP:

  • Java 1.5 or later (Note: for Linux, must be Sun or IBM's)
  • Eclipse 3.3.x
  • CDT 4.0.x
  • Open MPI 1.2
  • gdb 6.3 or later (earlier versions may also work)

The best environments for developing PTP are MacOS X 10.4 or later, or any recent version of Linux. Windows can be used to develop the Java components, but is not recommended. (Windows is fine for PLDT-only development. That is, for building and analysis of C code but not running MPI apps)

Setup

Install Eclipse

Download and Install Eclipse 3.3

Install Features

PTP 2.0 development requires Eclipse 3.3 (also known as Europa), CDT 4.0 and optionally RSE 2.0. RSE is is only required if you wish to use it for remote access. The preferred method for remote access is now to use the Remote Tools plugins that are part of PTP. It doesn't hurt to install RSE though.

There are two update sites from which you can install CDT:

  1. The Europa update site, whose address is already available in the Eclipse (3.3, Europa) update manager. This is only the basic CDT.
  2. The CDT update site, which also includes some additional optional features, including the SDK (source code and developer docs), C99 Parser, UPC features, testing code, XL C/C++ compiler support, GDB hardware debugging, etc.

Install basic CDT features from Europa Discovery Site:

  1. Launch Eclipse (as root if you installed Eclipse in a system directory)
  2. From the menu select: Help->Software Updates->Find and Install
  3. Select Search for new features to install, click Next
  4. Select Europa Discovery Site, click Finish
  5. Select a valid mirror, click Ok
  6. Expand Europa Discovery Site
  7. Select C and C++ Development
    Note: This should be version 4.0.3 at least (PLDT requires 4.0.2 or later)
  8. Select Remote Access and Device Development->Remote System Explorer... if you wish to install RSE
  9. Click Next
  10. Read and check I accept click Next and Finish.
  11. Click Install All

If you want to install some optional CDT features that the Europa Discovery site does not include, you can get it from the CDT Update site directly via the following:

  1. From the menu select: Help->Software Updates->Find and Install
  2. Select Search for new features to install, click Next
  3. Select the New Remote Site button on the right.
  4. In the New Update Site dialog, enter
    Name: CDT update site
    URL: http://download.eclipse.org/tools/cdt/releases/europa, click OK
  5. Make sure it is checked, and click Finish.
  6. Select a valid mirror, click Ok
  7. Expand CDT update Site and at a minimum, check, under CDT Main Features, the first item Eclipse C/C++ Development Tools... (there are also several useful optional features)
  8. Click Next
  9. Read and check I accept click Next and Finish.
  10. Click Install All

You will be prompted to restart your Eclipse workbench.

Access Eclipse CVS repository

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

After creating the repository location, expand it and expand HEAD. All the PTP content is under org.eclipse.ptp.

Note: 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.

For example, to make the PTP 2.0 tags appear, do the following:

  1. Open the CVS Repositories view for dev.eclipse.org as described above.
  2. Expand HEAD and select the project (org.eclipse.ptp) for which you want to configure tags.
  3. Context Menu->Configure Branches and Versions...
  4. In the "Browse files for tags" table, select one or more files that contain tags you would like to see.
    • For example, in the left pane under 'Browse files for tags:' expand 'core' and select the '.project' file
    • Check the tag 'ptp_2_0' branch tag shown in the right pane (or the 'PTP_2_0_1' version tag)
  5. Click "Add Checked Tags"
  6. Click "OK". The CVS Repositories view will now display the chosen tags under the Branches and Versions categories.

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.

Build Open MPI Proxy

  1. Follow Open MPI build directions as listed in PTP 1.1.1 Release Notes
  2. Follow the same directions to build your proxy plugin (sh BUILD for your platform); make sure it is the one in your workspace directory. The instructions are interpreted here:
    • Be sure to export this environment variable before compiling: LD_LIBRARY_PATH=/usr/local/lib
    • Locate the plug-in project org.eclipse.ptp.os.arch in your workspace, where os and arch correspond to your operating system and architecture respectively. Open a command shell and change to this directory.
    • Run the command: sh BUILD
    • You should at least have executables ptp_orte_proxy and sdm in your org.eclipse.ptp.os.arch project. You may need to Refresh (F5) the project to see it from the workbench.

Create an eclipse application launch configuration

Create a launch configuration to launch and run PTP as usual.

This might include : Click on org.eclipse.ptp.core, Right click on Run As ... and choose Eclipse Application .... [TBD]

References

  • Eclipse Downloads [1]
  • CDT Downloads Page [2]
  • CVS Howto [3]
  • PTP Release Notes [4]