1 / 35

Subversion/Eclipse/Debugger

Subversion/Eclipse/Debugger. Subversion source control Eclipse Integrated Development Environment Debugger graphical user interface for GDB inside of Eclipse. Subversion. What is source code version control? http://svnbook.red-bean.com/

stan
Télécharger la présentation

Subversion/Eclipse/Debugger

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Subversion/Eclipse/Debugger • Subversion • source control • Eclipse • Integrated Development Environment • Debugger • graphical user interface for GDB inside of Eclipse

  2. Subversion • What is source code version control? • http://svnbook.red-bean.com/ • allow multiple people to modify the same source code • allow one person to manage multiple versions of their source code • move from computer to computer to develop • track all changes

  3. Repository zeus.cs.pacificu.edu /home/chadd/SVNROOT/cs360_PA1 Store your source code on zeus check it out and edit it on any other machine and upload your changes back to zeus. Client Client Client moe.cs.pacificu.edu /home/chadd/cs360_PA1 chadd.home /homes/chaddcw/cs360_PA1 lisa.cs.pacificu.edu /home/chadd/cs360_PA1

  4. Version Control • Each change you make to the source code is a revision stored in the repository • can annotate you change with a note • why did I do that? • you can browse back through the repository to find old revisions of file • changed a data structure and it did not work • rewrote an algorithm and it got slower! • check out the old (working) revision from the repository

  5. zeus.cs.pacificu.edu /home/chadd/SVNROOT/cs360_PA1 revision 1 tree.c revision 2 revision 3 revision 4 tree.c revision 4 revision 5 moe$ svn checkout cs360_PA1 moe$ svn checkout cs360_PA1 moe$ pico tree.c moe$ svn checkout cs360_PA1 moe$ pico tree.c moe$ svn update tree.c moe$ svn commit tree.c tree.c moe.cs.pacificu.edu /home/chadd/cs360_PA1

  6. Hmmm…. • How often should I update and commit? • every major change • once every 15 minutes • right before you do something you think may be a bad idea • be sure to update and commit before you log off of a lab machine!

  7. How to get this to work • Create a repository on zeus • do this exactly once • use this one repository for all your projects • login to zeus zeus$ svnadmin /home/chadd/SVNROOT • We will check out source code later…

  8. File | New Project | C | Standard Make C Project

  9. /usr/bin/enscript --pretty-print=c ${container_loc}/${resource_name} –P XEROXPh8500N laser

  10. V

  11. Using Subversion by hand • login to ada ada$ svn checkout svn+ssh://zeus/home/chadd/SVNROOT/testFoo testFoo • This checks out the project we just created ada$ cd testFoo ada$ ls -al

  12. submit Script • Must run on zeus! • If anything goes wrong, the receipt file is your proof that you submitted the assignment! • don’t try to forge the receipt ;-) zeus$ submitcs360s07test.c SUCCESS: Receipt file: test.c.cs360s07.receipt DO NOT REMOVE OR ALTER THIS FILE IN ANY WAY! File transferred successfully!

More Related