CDT/Developer/FAQ

From Eclipsepedia

< CDT
Revision as of 11:07, 24 December 2009 by Angvoz.dev.gmail.com (Talk | contribs)

Jump to: navigation, search

Contents

General

  • Is it fun writing code for the CDT?

You betcha! And the Eclipse SDK is such a great environment to work in. We've pumped out quality code by the boat load without a lot of effort.

Getting the source

CVS

Instructions for getting the source through CVS are 'Getting started with CDT development' and 'CDT/contributing'

Git

Git for Committers details using git in the Eclipse development process. This document describes how to use git to maintain your own development lines and use the tools to generate patches for upstream submission.

Some of the plugins are available in public git repositories. These repos track CVS mainline and recent maintenance branches.

If you want a plugin that's not here, contact the dev-list

CDT Plugins:

Scripts for creating git repos cloned from CVS:


Release Engineering

  • Where can I get the latest builds?

We have a build machine, cdt.eclipse.org, that we use for our builds. You can access them from the builds section on its home page. You can also generate your own builds by checking out the CDT out of CVS and using the Export -> Deployable Feature menu item provided by the PDE.

Extending CDT

How can I programmatically create a new CDT project?

Check out methods ResourceHelper.createCDTProject(...) in plugin org.eclipse.cdt.core.tests. The class sports a few flavors of creating CDT project.

How do I contribute Include & Library paths to a project configuration?

  • externalSettingsProvider extension point

The external Settings Provider extension point can be used to register a build settings provider and have it dynamically called back at your own control. You can use this to contribute paths to your build configuration, making decisions at runtime on what should be added.

  1. Use the org.eclipse.cdt.core.externalSettingsProvider extension point, give it an "ID"
  2. Create a 'provider' element pointing at a class that extends CExternalSettingProvider
  3. Register the class on your CDT projects by adding your settingsProvider ID to the configuration descriptions list of settings providers:
    1. externalSettingsProviders = new LinkedHashSet<String>(Arrays.asList(ICConfigurationDescription.getExternalSettingsProviderIds()));
    2. extSettings.add(ID)
    3. ICConfigurationDescription.setExternalSettingsProviderIds(externalSettingsProviders.toArray(new String[0]));
  4. You will get a call-back on:
    1. public CExternalSetting[] getSettings(IProject project, ICConfigurationDescription cfgd) {
  5. which allows you to return appropriate macros and includes for the given configuration desc.
  6. CDT will cache this response, when there is a configuration change which may require a change to your settings, you should call:
    1. cfgd.updateExternalSettingsProviders(new String[] {ID});

Bug 222738 has an attachment with a sample plugin employing this technique. You can download it to get started.

How to add new make targets in the "Make Target" view?

Something like that could do the trick:

  IMakeTargetManager manager = MakeCorePlugin.getDefault().getTargetManager();
  String[] ids = manager.getTargetBuilders(project);
  IMakeTarget target = manager.createTarget(project, "name", ids[0]);
  target.setStopOnError(false);
  target.setRunAllBuilders(false);
  target.setUseDefaultBuildCmd(true);
  target.setBuildAttribute(IMakeCommonBuildInfo.BUILD_COMMAND, "make");
  target.setBuildAttribute(IMakeTarget.BUILD_LOCATION, "/build/location");
  target.setBuildAttribute(IMakeTarget.BUILD_ARGUMENTS, "args");
  target.setBuildAttribute(IMakeTarget.BUILD_TARGET, "target");
  manager.addTarget(container, target);

container here is a subfolder in the project where you wish to place the target.

Writing to a Console in Eclipse

see solution based on MessageConsole

Am I headless?

See solution based on Platform & PlatformUI

Hints

  • Can I find a method declare when my mouse point to a method for the CDT?

If you have a method selected in the Editor, pressing F3 will take you to the declaration (i.e. the prototype) and Ctrl-F3 with take you to the definition (i.e. the body). Both options are also available from the Context menu.

  • Converting between Reader and Streams
BufferedInputStream bis=new BufferedInputStream(url1.openStream());
BufferedReader br=new BufferedReader(new InputStreamReader(url1.openStream()));

More?

Many more questions are answered in the "Working on the CDT" section of the general CDT FAQ.

See also the unofficial CDT Developers FAQ.