Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

CDT/git

< CDT
Revision as of 15:58, 11 May 2011 by Doug.schaefer.windriver.com (Talk | contribs) (New page: To make it easier for adoptors and contributors to work with the CDT source, we are moving to git right after the final build for Indigo/CDT 8.0 in June 2011. This document will ultimate...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

To make it easier for adoptors and contributors to work with the CDT source, we are moving to git right after the final build for Indigo/CDT 8.0 in June 2011.

This document will ultimately be the guide for using git and egit with CDT. It will be a work in progress until then.

James Blackburn has created a test repository on github. He 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.

Setting up your workspace with the Test Repo

Follow these instructions to get working with the CDT test repo out on github.

  • Eclipse Setup (tested with Indigo M7)
    • Eclipse SDK
    • Install Egit and Subversive for source control
    • Install Remote System Explorer Run-time for build dependencies
      • for TCF and CDT remote launch
  • Check out build dependencies
    • from /cvsroot/tools, org.eclipse.orbit, checkout the 1.1 version of net.sourceforge.lpg.lpgjavaruntime
      • required by lrparser based plug-ins
    • from /cvsroot/eclipse, checkout the following required by the test plug-ins
      • org.eclipse.ant.optional.junit
      • org.eclipse.test
      • org.eclipse.test.performance
    • from /svnroot/dsdp/org.eclipse.tm.tcf, checkout all plug-ins and features
      • required by EDC
  • Preferences setup
    • Make sure you setup up an API baseline. Current baseline should be the Helios build.
  • Clone the repo
    • From the Git perspective, clone the repo and place it some where useful
    • From the repo, select Import Projects...
      • Select all the projects
      • You can select individual ones if you need
    • Let the build run
      • I find that I sometimes need to do a rebuild to ensure the API checkers run correctly.

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