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.
Difference between revisions of "PTP/rdt-setup"
< PTP
(→How to build and run RDT (Remote Development Tools)) |
(→How to build and run RDT (Remote Development Tools)) |
||
| Line 18: | Line 18: | ||
#* Click 'Finish' and it will generate the jar file. It will also prompt you to save/overwrite the .jardesc file. | #* Click 'Finish' and it will generate the jar file. It will also prompt you to save/overwrite the .jardesc file. | ||
#* After setting this up, later you can rightmouse on the .jardesc file and just select "Create JAR" if you don't need to change anything. | #* After setting this up, later you can rightmouse on the .jardesc file and just select "Create JAR" if you don't need to change anything. | ||
| − | # | + | #* It should build these jars: |
| + | #** cdtminer.jar | ||
| + | #** cdtmodel.jar | ||
| + | #** cdtparser.jar | ||
| + | #** stubs.jar | ||
| + | # Copy those jars to remote machine, e.g. in the 'rseserver' directory as in the example above | ||
# Copy the eclipse jars for org.eclipse.equinox.common, org.eclipse.core.runtime, and org.eclipse.core.filesystem to remote machine, again into the 'rseserver' directory | # Copy the eclipse jars for org.eclipse.equinox.common, org.eclipse.core.runtime, and org.eclipse.core.filesystem to remote machine, again into the 'rseserver' directory | ||
| − | #* They should be in your <eclipse-install>/plugins directory (on either local machine, or if eclipse SDK is on remote machine, can copy them from there. They are not platform-specific.) | + | #* They should be in your <eclipse-install>/eclipse/plugins directory (on either local machine, or if eclipse SDK is on remote machine, can copy them from there. They are not platform-specific.) |
#* for example | #* for example | ||
#** cp eclipse/plugins/org.eclipse.equinox.common_*.jar ~/rseserver | #** cp eclipse/plugins/org.eclipse.equinox.common_*.jar ~/rseserver | ||
#** cp eclipse/plugins/org.eclipse.core.runtime_*.jar ~/rseserver | #** cp eclipse/plugins/org.eclipse.core.runtime_*.jar ~/rseserver | ||
#** cp eclipse/plugins/org.eclipse.core.filesystem_*.jar ~/rseserver | #** cp eclipse/plugins/org.eclipse.core.filesystem_*.jar ~/rseserver | ||
| − | # Add a line to minerFile.dat that has org.eclipse.ptp.internal.rdt.core.miners.CDTMiner in it | + | # In the rseserver directory: |
| − | # Edit server.sh | + | #* Add a line to minerFile.dat that has org.eclipse.ptp.internal.rdt.core.miners.CDTMiner in it |
| − | #*CLASSPATH=.:dstore_extra_server.jar:dstore_core.jar:dstore_miners.jar:clientserver.jar:cdtminer.jar:cdtmodel.jar:cdtparser.jar:org.eclipse.core.runtime_3.4.0.v20080421-1805.jar:org.eclipse.equinox.common_3.4.0.v20080421-2006.jar:org.eclipse.core.filesystem_1.2.0.v20080421-1805.jar:stubs.jar:$CLASSPATH; | + | #* Edit the server script file (e.g. server.sh or server.pl) to add all the jars you copied over to the CLASSPATH. So the CLASSPATH line looks something like: |
| − | #*where the qualifier in the names of the eclipse jars matches what you copied in step | + | #**CLASSPATH=.:dstore_extra_server.jar:dstore_core.jar:dstore_miners.jar:clientserver.jar:cdtminer.jar:cdtmodel.jar:cdtparser.jar:org.eclipse.core.runtime_3.4.0.v20080421-1805.jar:org.eclipse.equinox.common_3.4.0.v20080421-2006.jar:org.eclipse.core.filesystem_1.2.0.v20080421-1805.jar:stubs.jar:$CLASSPATH; |
| + | #** where the qualifier in the names of the eclipse jars matches what you copied in the previous step (the version/date/timestamp info in the filename) | ||
Revision as of 15:08, 5 September 2008
How to build and run RDT (Remote Development Tools)
RDT allows the use of CDT on remote projects and files. In this discussion, the local machine is the one running eclipse, the remote machine is the one to connect to for running, debugging, file locations, etc.
Here is how to set it up and run.
- Get Eclipse 3.4 (Ganymede) and CDT 5.0.1
- Get RSE Server
- From RSE download page at http://download.eclipse.org/dsdp/tm/downloads/ - click on version 3.0
- on the "TM Release Build:3.0" page, scroll down to "DStore Server Runtime" section and get rseserver-3.0-<platform> file, zip or tar, for your remote machine's platform.
- Untar it on the remote machine, for example in a directory named 'rseserver'
- Go to org.eclipse.ptp.rdt.core.remotejars project and use the .jardesc files to build all the jars
- In CVS Repository exploring perspective, connect to dev.eclipse.org:/cvsroot/tools
- Under HEAD, expand org.eclipse.ptp project, and expand 'rdt' folder
- Check out all the rdt projects if you like - for this step you need the remotejars project - you don't need projects ending in 'test' or 'tests' however.
- Expand the or.eclipse.ptp.rdt.core.remotejars project
- Rightmouse on one of the *.jardesc files, and select "Open JAR Packager" - in here, select the export destination - where it will write the jar file.
- Click 'Finish' and it will generate the jar file. It will also prompt you to save/overwrite the .jardesc file.
- After setting this up, later you can rightmouse on the .jardesc file and just select "Create JAR" if you don't need to change anything.
- It should build these jars:
- cdtminer.jar
- cdtmodel.jar
- cdtparser.jar
- stubs.jar
- Copy those jars to remote machine, e.g. in the 'rseserver' directory as in the example above
- Copy the eclipse jars for org.eclipse.equinox.common, org.eclipse.core.runtime, and org.eclipse.core.filesystem to remote machine, again into the 'rseserver' directory
- They should be in your <eclipse-install>/eclipse/plugins directory (on either local machine, or if eclipse SDK is on remote machine, can copy them from there. They are not platform-specific.)
- for example
- cp eclipse/plugins/org.eclipse.equinox.common_*.jar ~/rseserver
- cp eclipse/plugins/org.eclipse.core.runtime_*.jar ~/rseserver
- cp eclipse/plugins/org.eclipse.core.filesystem_*.jar ~/rseserver
- In the rseserver directory:
- Add a line to minerFile.dat that has org.eclipse.ptp.internal.rdt.core.miners.CDTMiner in it
- Edit the server script file (e.g. server.sh or server.pl) to add all the jars you copied over to the CLASSPATH. So the CLASSPATH line looks something like:
- CLASSPATH=.:dstore_extra_server.jar:dstore_core.jar:dstore_miners.jar:clientserver.jar:cdtminer.jar:cdtmodel.jar:cdtparser.jar:org.eclipse.core.runtime_3.4.0.v20080421-1805.jar:org.eclipse.equinox.common_3.4.0.v20080421-2006.jar:org.eclipse.core.filesystem_1.2.0.v20080421-1805.jar:stubs.jar:$CLASSPATH;
- where the qualifier in the names of the eclipse jars matches what you copied in the previous step (the version/date/timestamp info in the filename)