- 1 Introduction
- 2 General
- 2.1 What is the CDT?
- 2.2 How is the CDT licensed?
- 2.3 How is the CDT Project organized?
- 2.4 How do I find out about future releases of the CDT?
- 2.5 What is the default configuration supported by the CDT?
- 2.6 Which operating systems does the CDT support?
- 2.7 Which platforms are fully supported will ultimately depend on the needs of the community, as expressed by the participation in developing, and testing for each platform?
- 2.8 Why isn't the XXX operating system supported by CDT?
- 3 Compilers and other 3rd party tools
- 4 Working on the CDT
How do I contribute to this FAQ?
Simply edit this page and add content. You can now use your bugzilla username and password to gain access.
Is it really that easy?
What is the CDT?
The CDT (C/C++ Development Tools) Project is working towards providing a fully functional C and C++ Integrated Development Environment (IDE) for the Eclipse platform.
There are a number of groups contributing to the CDT; We strongly encourage interested parties to extend our work, thereby making the Eclipse CDT project a richer set of freely available resources. We are looking for contributions from the open source community in the areas of test, development, documentation, and general users who can help us ensure that the C/C++ tools work well on all the Eclipse platforms.
Our current release function includes:
- * C/C++ Editor (basic functionality, syntax highlighting, code completion etc.)
- * C/C++ Debugger (APIs & Default implementation, using GDB)
- * C/C++ Launcher (APIs & Default implementation, launches and external application)
- * Parser
- * Search Engine
- * Content Assist Provider
- * Makefile generator
Default implementations of all interfaces and extension points will be supplied for various platforms.
How is the CDT licensed?
The CDT consists of software produced by the CDT team combined with third party software developed from other Open Source Projects. The software produced by the CDT team is licensed under the Common Public License. The software designed by third parties is made available under their respective licenses. Refer to the about.html file in the root directory of every CDT plugin for specific licensing information.
How is the CDT Project organized?
Visit CDT Project Structure to find out more about the organization of CDT (History, participants, and project structure).
How do I find out about future releases of the CDT?
See the CDT/planning section.
If you wish to contribute to the development of the CDT, we welcome the opportunity to work with you. The plans will be updated to reflect the commitments made by contributors to this projects. See Working on the CDT for information on how to get started.
Release Milestones (which represent planned availability dates for Stable CDT builds) are noted in the CDT Plan Documents which can be found on the CDT Overview Page. To see the currently available CDT builds, choose from either the current official release or from the nightly builds.
What is the default configuration supported by the CDT?
This is a bit of a moving target, but currently the compiler supported (from an error parsing point of view) is gcc, the debugger interface will work with gdb 5.2.1 (or higher) and the default build command is GNU "make".
Which operating systems does the CDT support?
The CDT Framework is platform independent. It will run where Eclipse will run. However, the default implementations may depend on external applications. To follow in the Eclipse spirit of open source, the default implementations rely upon freely available open source tools, such as the GNU Tools: GDB and Make. Therefore, the dependencies on GDB for debugging, or Make for building, will require that these applications are available for the platform that the user wishes to use. References to some of the known implementations for each platform will be indicated in the sections of this FAQ that include instructions for installation, project creation and building the CDT on the various platforms.
Which platforms are fully supported will ultimately depend on the needs of the community, as expressed by the participation in developing, and testing for each platform?
The core plugins are written in Java with no native code and thus may be ported to any platform supported by Eclipse. However, some default implementations may require that other software or tools, licensed under GNU, may be required.
In general there is some version of Linux and some version of windows used by the developers on the CDT. For an exact list of supported platforms see the Downloads page.
Why isn't the XXX operating system supported by CDT?
"Supported" has a particular meaning to us. It means that on that platform we have a good level of confidence that CDT works correctly and that its function is appropriate and complete. That means
- * someone has ensured that the function addresses the important use cases
- * the function is exercised by regular execution of a test plan
- * identified problems are tracked to resolution
- * there is a recipient for user feedback
- * code patches are developed as necessary to correct or extend CDT on that platform
To make this all happen a platform has an Owner - someone who accepts the responsibility to make sure those things all happen.
The Framework supports all the platforms that Eclipse does. The CDT team is responsible for ensuring that this remains true for the framework. Specific default implementations will work only on platforms where the required applications are available. The following list is derived from the initial CDT meeting in July 2002. The following companies have agreed to provide support for the associated platforms:
|QNX Neutrino||QNX Software Systems Ltd.|
|Linux||IBM, Red Hat|
|Windows||IBM, MontaVista with initial support from QNX|
If you have a favorite platform we highly encourage you to get involved and volunteer to own a feature that does not currently have an implementation that works on your platform of choice. See Working on the CDT for more information.
Compilers and other 3rd party tools
Does CDT include a compiler?
CDT does not come with a compiler, so if you do not have one you will need to install one. Follows are options available to you:
- * MacOS X: Install the developer tools DVD that came with your computer or with you MacOS X DVD.
- * Linux: If not already installed, it should be available on your installation CDs.
- * Windows: You have a choice of compilers available:
Working on the CDT
How do I build CDT from CVS if I want a more recent build than is on the downloads page?
- Switch to the CVS Perspective: Window > Open Perspective > Others ... and select "CVS Repository Exploring"
- Context menu in "CVS Repositories" View, New > Repository Location
- Location - Host: dev.eclipse.org Repository Path: /cvsroot/tools
- Authentication - User: anonymous (no password required)
- Connection - type: pserver
- Click 'Finish'
- Open up the resulting /cvsroot/tools tree.. find org.eclipse.cdt-releng/all
- On each of the projects under 'all', click context menu > Check Out
How do I export it so that it can be used with an external Eclipse installation?
- You can either:
- a) Export the CDT feature via File->Export->Plugin Development->Deployable Features. This will automatically export all the required plugins.
- b) Export all the plugins etc. individually or all at once via File->Export->Plugin Development->Deployable Plugins and Fragments. However, this is more error prone and you're better off doing a).
- c) Use the ANT stuff in org.eclipse.cdt.releng to build CDT the way the nightly build does.
- I want to differntiate between the "Debug" and "Release" modes in my project. Is there any preprocessors in use already (some #define like "#define DEBUG" for Debug mode) or should I have to define them manually in my project. I find verbose in project options, but I am not sure how to use it ?
Back to CDT wiki page.