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

Difference between revisions of "CDT/git"

< CDT
(Setting up your workspace with the CDT Repo)
Line 1: Line 1:
 
To make it easier for adoptors and contributors to work with the CDT source, we moved to GIT source control system June 24th 2011. Old CVS repo is read only now.
 
To make it easier for adoptors and contributors to work with the CDT source, we moved to GIT source control system June 24th 2011. Old CVS repo is read only now.
  
This document will ultimately be the guide for using git and egit with CDT. It will be a work in progress until then.  
+
This document will ultimately be the guide for using git and egit with CDT.  
  
James Blackburn has created a test repository on github and it has been mirrored back to our space on git.eclipse.org.
+
== Source Repositories  ==
 
+
James is working on the conversion script. Once we're ready, we'll take the repo and bring it to Eclipse and make it our central repo that will feed the official builds. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=316208 Conversion script is discussed here.]
+
 
+
== Setting up your workspace with the CDT Repo ==
+
  
 
CDT is now broken into two git repos. You can view repos at http://git.eclipse.org/c/.
 
CDT is now broken into two git repos. You can view repos at http://git.eclipse.org/c/.
 
Core cdt org.eclipse.cdt.git, EDC repo is org.eclipse.cdt.edc.git. If you want to practice there are also
 
Core cdt org.eclipse.cdt.git, EDC repo is org.eclipse.cdt.edc.git. If you want to practice there are also
 
test repos, test3/*...
 
test repos, test3/*...
 +
 +
Committers will want to access the master repository via ssh
 +
 +
  ssh://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
 +
 +
Everyone else will use either of the following URLs
 +
 +
  git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
 +
  http://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
 +
 +
[http://git.eclipse.org/c/cdt/org.eclipse.cdt Click here] for further information on the Git repos available to CDT developers
 +
 +
== Screencasts  ==
 +
 +
Doug Schaefer has posted numerous screencasts on using git with Eclipse<br>
 +
 +
*[http://www.youtube.com/watch?v=DcM1xOiaidk&feature=related Using Git GUI with Eclipse Part I - Setting up the workspace] [http://www.youtube.com/watch?v=1OrPJClD92s&feature=related]<br>
 +
*[http://www.youtube.com/watch?v=1OrPJClD92s&feature=related Using Git GUI with Eclipse Part II - Pushing changes to the server] [http://www.youtube.com/watch?v=WU9xYP_NScQ]<br>
 +
*[http://www.youtube.com/watch?v=WU9xYP_NScQ Setting up SSH authorized keys in Eclipse] [http://www.youtube.com/watch?v=Lhwi3z2DyzQ&feature=related]
 +
*[http://www.youtube.com/watch?v=Lhwi3z2DyzQ&feature=related Creating and Applying Patches to CDT git repo] [http://www.youtube.com/watch?v=I5uq6dWdi0w&feature=related]
 +
*[http://www.youtube.com/watch?v=I5uq6dWdi0w&feature=related CDT Pushing Changes to Master]
 +
 +
 +
== Setting up your workspace with the CDT Repo ==
  
 
Follow these instructions to get working with the CDT repo out on eclipse.org.
 
Follow these instructions to get working with the CDT repo out on eclipse.org.
Line 22: Line 42:
 
** Eclipse Classic 3.7
 
** Eclipse Classic 3.7
 
** Install Cdt on top on eclipse or install a separate copy of CDT 8.0 to establish an API baseline
 
** Install Cdt on top on eclipse or install a separate copy of CDT 8.0 to establish an API baseline
** In Preferences set API baseline (you can set it to its own installation if it has CDT it it)
+
** In Preferences set API baseline (you can set it to its own installation if it has CDT in it)
 
** Install Egit 1.0 (you can get it from Indigo update site). See docs http://wiki.eclipse.org/EGit/User_Guide
 
** Install Egit 1.0 (you can get it from Indigo update site). See docs http://wiki.eclipse.org/EGit/User_Guide
 
** (Optional if you using CDT remote launch) Install Remote System Explorer Run-time for build dependencies
 
** (Optional if you using CDT remote launch) Install Remote System Explorer Run-time for build dependencies
Line 34: Line 54:
 
**** URL for committers - ssh://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
 
**** URL for committers - ssh://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
 
**** URL - git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
 
**** URL - git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
*** Enter your committer credentials. Doug has video about setting up ssh keys http://www.youtube.com/watch?v=WU9xYP_NScQ&feature=related here
+
*** Enter your committer credentials. Doug has video about setting up ssh keys http://www.youtube.com/watch?v=WU9xYP_NScQ&feature=related. It does not work directly yet, you need to ask unrestricted shell from admins first.
 
*** It will ask you what branches to import. If you only care about head select master, if you want to work with other branches select a corresponding branch, for example cdt_8_0.
 
*** It will ask you what branches to import. If you only care about head select master, if you want to work with other branches select a corresponding branch, for example cdt_8_0.
 
*** Press Next. As location where files are store select a folder inside your workspaces, for example workspace/cdt-git
 
*** Press Next. As location where files are store select a folder inside your workspaces, for example workspace/cdt-git
Line 40: Line 60:
 
*** This should take about 3-5 minutes
 
*** This should take about 3-5 minutes
 
** From the repo, select Import Projects...
 
** From the repo, select Import Projects...
*** Select all the projects
+
*** Select all the projects or individual. Project filter does not seems to work. It maybe easier select all, then close projects you don't need
*** You can select individual ones if you need
+
 
** Let the build run
 
** Let the build run
 
*** I find that I sometimes need to do a rebuild to ensure the API checkers run correctly.
 
*** I find that I sometimes need to do a rebuild to ensure the API checkers run correctly.

Revision as of 14:23, 26 June 2011

To make it easier for adoptors and contributors to work with the CDT source, we moved to GIT source control system June 24th 2011. Old CVS repo is read only now.

This document will ultimately be the guide for using git and egit with CDT.

Source Repositories

CDT is now broken into two git repos. You can view repos at http://git.eclipse.org/c/. Core cdt org.eclipse.cdt.git, EDC repo is org.eclipse.cdt.edc.git. If you want to practice there are also test repos, test3/*...

Committers will want to access the master repository via ssh

  ssh://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git

Everyone else will use either of the following URLs

  git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
  http://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git

Click here for further information on the Git repos available to CDT developers

Screencasts

Doug Schaefer has posted numerous screencasts on using git with Eclipse


Setting up your workspace with the CDT Repo

Follow these instructions to get working with the CDT repo out on eclipse.org.

There is wiki for eclipse/git marriage here - http://wiki.eclipse.org/Git

Step one is for the main CDT repo.

  • Eclipse Setup (tested with Indigo)
    • Eclipse Classic 3.7
    • Install Cdt on top on eclipse or install a separate copy of CDT 8.0 to establish an API baseline
    • In Preferences set API baseline (you can set it to its own installation if it has CDT in it)
    • Install Egit 1.0 (you can get it from Indigo update site). See docs http://wiki.eclipse.org/EGit/User_Guide
    • (Optional if you using CDT remote launch) Install Remote System Explorer Run-time for build dependencies
  • Check out build dependencies
    • (Optional if you using lp-parsers) from anonymous@dev.eclipse.org:/cvsroot/tools, org.eclipse.orbit, checkout the 1.1 version of net.sourceforge.lpg.lpgjavaruntime
    • (Optional if you using test plugins) anonymous@dev.eclipse.org:/cvsroot/eclipse, checkout the following
      • org.eclipse.test.performance
  • Clone the repo. Doug's video http://www.youtube.com/watch?v=O4rDgx6-B6Q
    • From the Git perspective, select clone repo action
    • From the repo, select Import Projects...
      • Select all the projects or individual. Project filter does not seems to work. It maybe easier select all, then close projects you don't need
    • Let the build run
      • I find that I sometimes need to do a rebuild to ensure the API checkers run correctly.
  • Another video http://www.youtube.com/user/cdtdoug#p/a/u/1/I5uq6dWdi0w

More for EDC soon.

And that's it. One way to test you have everything is to try and Export the master feature. That'll give you everything our official builds do.

Back to the top