Jump to: navigation, search

Difference between revisions of "PTP/sync-projects"

< PTP
(Presentations and Tutorials)
Line 1: Line 1:
Refer to [http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.ptp.doc.user%2Fhtml%2Fsync.html Synchronized Projects User Guide] for basic information. [http://forecaster.ncsa.uiuc.edu/whpc/ptp-synch-projects/index.htm The user-call recording] includes a live demonstration of how to setup and configure a synchronized project.  
+
= Basic Information =
 +
Refer to [http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.ptp.doc.user%2Fhtml%2Fsync.html Synchronized Projects User Guide] for basic information.  
 +
 
 +
The July 2011 PTP user meeting [http://forecaster.ncsa.uiuc.edu/whpc/ptp-synch-projects/index.htm user-call recording] includes a live demonstration of how to setup and configure a synchronized project. (Note: convert to full-screen viewing via the green square in the lower right corner of the screen to be able to read the contents of the demo screens.)
  
 
= Known Issues =
 
= Known Issues =
Line 31: Line 34:
 
* Add Fortran synchronization wizard
 
* Add Fortran synchronization wizard
 
* Do not sync if only a file's markers have changed (prevents sync'ing during file editing if code analysis is turned on).
 
* Do not sync if only a file's markers have changed (prevents sync'ing during file editing if code analysis is turned on).
 
= Presentations and Tutorials =
 
* July 2011 PTP user meeting featured a presentation and demo by John Eblen and Roland Schultz: replay is available at: http://forecaster.ncsa.uiuc.edu/whpc/ptp-synch-projects/lib/playback.html (Note: convert to full-screen viewing via the green square in the lower right corner of the screen to be able to read the contents of the demo screens.)
 

Revision as of 09:55, 9 August 2011

Basic Information

Refer to Synchronized Projects User Guide for basic information.

The July 2011 PTP user meeting user-call recording includes a live demonstration of how to setup and configure a synchronized project. (Note: convert to full-screen viewing via the green square in the lower right corner of the screen to be able to read the contents of the demo screens.)

Known Issues

  • There are no wizards to convert existing projects to synchronized projects. A fix is planned for version 5.0.2.
  • Errors occur during synchronization if the project contains files with odd characters, such as parentheses. (Files with spaces should work fine.)
  • There are some potential pitfalls when configuring projects
    • Users should avoid changing configurations inside the new project wizard, as this will cause errors. Instead, add and change configurations after project creation.
    • The Workspace configuration only appears after the project is created.
    • The tool chain selected during creation is used for both the local machine and remote machine. Users need to adjust this after project creation.
    • For remote configurations, only the "Sync Builder" works, although other options are available (Project -> Properties -> C/C++ Build -> Tool Chain Editor). The "Sync Builder" is set as the default.
    • Attempting to change multiple configurations does not work correctly.

FAQ

I want to use CVS (or another version control system) together with synchronization. How do I setup a synchronized project and download my files from CVS?

  1. Create an empty Synchronized project
  2. Right-click on the project: 'Team' -> 'Share Project'
  3. Configure the repository
  4. Do not launch the Commit wizard (last page of wizard)
  5. Right-click on the project: 'Team' -> 'Update' to download all files. The files will automatically be synchronized to the remote host.


Change Log

Version 5.0.1

  • Use separate Git directory (.ptp-sync instead of .git) for sync'ing so that it does not interfere with user's Git repository.
  • Sync empty directories
  • Prevent users from modifying the synchronization properties of the Workspace configuration
  • Fix bug 349372: Build fails if empty environment variables are present
  • Support managed project types
  • Add Fortran synchronization wizard
  • Do not sync if only a file's markers have changed (prevents sync'ing during file editing if code analysis is turned on).