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.
Difference between revisions of "Getting started with CDT development"
(→Getting started with CDT development for the latest CVS head) |
m (→Getting started with CDT development for the latest CVS head) |
||
| Line 15: | Line 15: | ||
* If you are not a committer, open the psf in a text editor and do a search-n-replace: "extssh" ==> "pserver" | * If you are not a committer, open the psf in a text editor and do a search-n-replace: "extssh" ==> "pserver" | ||
* Go to: File > Import > Team > Team Project Set and select the psf | * Go to: File > Import > Team > Team Project Set and select the psf | ||
| − | * You will be prompted for a username and password. | + | * You will be prompted for a username and password. Non-committers should enter "anonymous" for username, and an email address for the password. |
The fairly long process of checking out all the sources from CVS will begin. | The fairly long process of checking out all the sources from CVS will begin. | ||
Revision as of 13:35, 11 March 2010
Getting started with CDT development for the latest CVS head
- Preparing workspace
First you need to get the correct eclipse version, the latest CVS head of CDT works with eclipse 3.6 (Helios), so browse downloads page and grab this version. It should contain both the JDT and PDE plugins that would allow you to develop plugins for eclipse.
- For example, on http://download.eclipse.org/eclipse/downloads/, under the "Eclipse 3.6 and 3.5.x Stream Stable Builds" heading (grey bar), select Eclipse 3.6M5 (or a later one if available) - and on the next page, select Eclipse SDK - and download it.
Unzip or untar this archive, and launch eclipse.
Now let's download the CDT source code.
- Click on the following file and download it to your machine: http://www.eclipse.org/cdt/psf/cdt-main.psf
- If you are not a committer, open the psf in a text editor and do a search-n-replace: "extssh" ==> "pserver"
- Go to: File > Import > Team > Team Project Set and select the psf
- You will be prompted for a username and password. Non-committers should enter "anonymous" for username, and an email address for the password.
The fairly long process of checking out all the sources from CVS will begin.
After you checkout, JDT will build all the projects for you. If you have any error markers, you might be missing some plugins.
- Launching
Now, move back to the PDE (Plug-in Development Environment) perspective. Window->Perspective->Other->"Plug in Development". There, you'll see a project with the name org.eclipse.cdt.ui, right click the org.eclipse.cdt.ui project, select "Run As"->"eclipse application". You should see a new instance of eclipse - with the latest version of eclipse CDT plugins.
- Submitting and Applying Patches
If you wish to contribute your changes to CDT see these instructions.
In order to apply a patch, right click the relevant project, and select "Team->Apply Patch...
In case you've applied a patch, and you wish to revert back to the latest HEAD branch - right click the project, then "Replace With->Latest From HEAD", answer Yes to the warning message, and the patch is gone.
- Creating a runtime patch
Building a working cdt distribution is very difficult, but if you want just patch up your local installation you can export plugin(s) to which source patch is applied using Export->Plugins, export as archive and use your eclipse installation as destination. Make sure after this you have 2 version of the same plugin (one from installation and one new) in the plugins directory and version qualifier of your new plugin is higher.