Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

PTP/designs/remote

< PTP‎ | designs
Revision as of 14:01, 10 October 2007 by Unnamed Poltroon (Talk)

Remote Development Tools Designs

List of Authors:

   Chris Recoskie (recoskie@ca.ibm.com)
   Greg Watson (grw@us.ibm.com)

Background

This page is for low level technical details, notes, and discussions of the Remote Development Tools effort. For overall planning, see the Remote Development Tools Planning Page

Presentations

  • Remote Development Presented at the CDT Summit 2007 detailing the motivation behind the need for remote development tools and the status of current efforts.

Architecture Requirements

  • No new dependencies for other projects (e.g. CDT should not have to depend on RSE)
  • User experience for local scenarios should not change in any appreciable way.
  • Try to hide the remote functionality from the user wherever possible. Once the user has chosen a remote project and setup their connections it should "just work"
  • APIs should not be tied to any specific protocol or service provider. We wish to allow for different protocols to be used, potentially at the same time.
    • E.g., we should not be assuming everything is SSH
    • E.g., we should not be assuming everything is done via RSE.
  • APIs and reference implementations should be vendor neutral.

General

Replacement for IPath that abstracts around the remote/local nature of paths

EFS Support

We are currently looking at refactoring CDT for the 5.0/Ganymede release to add support for EFS.

The main areas of CDT that need to be tackled are:

Build

There are currently two builders planned:

  • Remote Standard Make A remote-enabled version of CDT's Standard Make. Essentially, a make-based builder that uses a remote shell protocol (e.g. SSH) to invoke a builder (e.g. GNU make) on a user-crafted buildfile (makefile). We are planning on tackling this after EFS support, hopefully in time for CDT 5.0, a.k.a. Ganymede.
  • Remote Managed Build A remote-enabled version of CDT's Managed Build. In this case the Managed Build System would know about your compile settings, and execute the required build commands directly via the shell protocol (e.g. SSH). Implementation date is currently TBD.


Launch/Debug

  • Coming soon...

Back to the top