CDTFaq

How do I install CDT?
Instructions for getting up and running with developing the CDT
[What does add a Target mean]
How do I set up remote debuggin on a MIPs platform?

Does a makefile notion exists in CDT?

The CDT invokes a builder. The default builder simply calls make. Makefiles are NOT autogenerated. You must supply a makefile in the root directory of your project. (CDT 1.x).

This has changed. In Eclipse 2.x there is a notion of "managed make" which actually provides makefiles that are built for you. But you are still free to use your own makefiles if you wish

What will be the contribution of QNX in CDT?

Hi all,
as John Duimovitch announced a few weeks ago, QNX will be contributing
some of its C/C++ plugin code, as well as development resources, to the
CDT project. We are also taking over as project lead. I'm sure people
have a lot of questions as to exactly what is going to happen, so let
me give some general background on the direction and vision that we see
the CDT taking, as well as some specifics on how we will move the CDT
forward.

First, I want again to thank the IBM team for their work on the CDT.
They have done a great job in providing a rich C/C++ toolset for Linux
development, which forms a great foundation for us to build on.

As was mentioned, QNX is donating some of its C/C++ code to the CDT
project.

QNX's Momentics toolset (the brand-name of our IDE) is focused on C/C++
development for QNX targets, and runs on Windows, Solaris and QNX
Neutrino hosts. It is heavily inspired by the Eclipse Java tools (we try to
follow the same look and feel for consistency) and we've also tried to
follow a similar architecture. I believe the QNX code is a nice complement
to the existing CDT code.

With the addition of QNX on the CDT project, and participation
by some of the other Eclipse members (Rational, Redhat and others),
the goals of the CDT are going to change quite a bit.
We are going to put more emphasis on broad host platform support, on
expanding the development scenarios, and in having the right
hooks to support a wide range of external compilers and tools. This will
be achieved by developing a highly extensible CDT, where base functionality
can be easily extended or overridden by plugins that target specific
environments.

The ultimate goal is to have core CDT plugins that not only provide base
C/C++ development, but also form the integration points for a variety of free
and commercial C/C++ tools, having these tools interoperate without having to
do specific tool-to-tool integration. When we discuss the architecture of the
CDT, we'll highlight some of these scenarios.

Our approach will also be to maximize the amount of code and
functionality that can be shared with the Java tools. As languages, Java and
C/C++ are very similar, and working on common pieces such as editors or class
browsers makes a lot of sense. The CDT project will also try to maintain
a "look and feel" for C/C++ tools that is very close to the JDT.

Some of QNX's code has already been moved into Eclipse's CVS repository
under the org.eclipse.cdt.core and org.eclipse.cdt.ui components. This
code represents our core C/C++ tooling, including the core model, builder,
editor, C view and so on, and compiles and runs on Eclipse 2.0. Please
see the cdt-core mailing list for discussions and more details. We will also
be contributing to the debugger, although the debugger components
will require significant re-architecting to meet the new goals of the
CDT.

As hinted above when I mentioned the debugger, a lot of re-planning,
architecture and API definition is going to happen over the next month,
as we assess how to move forward given the broadened goals of the CDT. If you
wish to participate in this, feel free to join the discussion on the CDT
mailing lists. Note that there will be some disruptions as we update the web
pages, builds, move source around and so on. Please bear with us, or better
yet, give us a hand... it will be greatly appreciated.

To sum it up, I'm personally very excited at being part of this project,
and truly believe that we can develop a strong C/C++ foundation for Eclipse
that will eventually rival the Java tools. I also hope that you will all be
able to participate in building this!
Regards,
Sebastien Marineau
QNX Software Systems
sebastien@qnx.com

When will we see something to play with?(QNX extension)

Two packages have been added to "/home/tools" in the dev.eclipse.org cvs
repository.

org.eclipse.cdt.core
   org.eclipse.cdt.ui

These are preliminary and we are still working on making them generic and
extensible.
Together they will give you a basic C/C++ editor and something to play with
;)
We are in the process of creating updates to the website with information on
how to use the new code, designs and plans for the future and much much
more.
Enjoy ...
Judy

Update September 2002:
We have added more functionality.
The CDT packages now consist of:

org.eclipse.cdt
   org.eclipse.cdt.core
   org.eclipse.cdt.core.linux
   org.eclipse.cdt.core.qnx
   org.eclipse.cdt.core.solaris
   org.eclipse.cdt.core.win32
   org.eclipse.cdt.debug.core
   org.eclipse.cdt.debug.mi.core
   org.eclipse.cdt.debug.mi.ui
   org.eclipse.cdt.debug.ui
   org.eclipse.cdt.debug.ui.tests
   org.eclipse.cdt.launch
   org.eclipse.cdt.ui
   org.eclipse.cdt.ui.tests
   org.eclipse.cdt-feature

Have fun with them ...

Judy

Last Modified 10/2/06 11:34 AM

Hide Tools

Site
Changes
Index
Search

User
Log In
Register