| RE: [cdt-dev] Importing Existing Code |
|
> BTW, xterms and make are an IDE too ;). I think there is a difference between a “build specification”
and a “project file” and a variety of things that a project file
can support that a build specification typically doesn’t. Here are
some examples: o A build specification tends to identify how to build types of files
whereas a project file knows exactly what set of source files are in the
project o A project file contains named build configurations. This is
usually in build specifications as well but not necessarily as obvious or as
abstracted o A project file contains metadata describing the project itself (e.g. what
“kind” of thing is the output of the project – a DLL?) o A project file contains metadata describing how the project interacts
with other parts of the IDE besides the build system: debuggers, error
parsers, binary parsers, the exact language variant being used…) o A project file contains metadata describing how the project interacts
with external tools: (e.g. source code control systems) Leo From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer I will look at doing both. I started it as a new project wizard, then
changed it. BTW, xterms and make are an IDE too ;). :D On Wed, Mar 10, 2010 at 4:20 PM, I agree with Felipe. I think import should be used when
starting with a project file from a different IDE (e.g. Visual Studio, QT
Creator, etc.). I think of this case as Filipe does. New Project ->
with Existing sources Leo From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Figuer, Felipe A
Subject: RE: [cdt-dev]
Importing Existing Code It makes sense to
me as follows: New Project ->
with Existing sources Import to me means
like taking resources or something from a different environment into Eclipse
CDT but in this case
it is just to not start from scratch and as you need a Eclipse project to work
with Eclipse a new project is a
have to. From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer Excellent! Thanks. One question I'm
still struggling with is whether this is really an Import operation, since it
imports code, or a New Project operation since it creates a new project, or
maybe both. Anyone have thoughts on that? On Wed, Mar 10,
2010 at 2:37 PM, Figuer, Felipe A <Felipe.A.Figuer@xxxxxxxxxx>
wrote: That sounds great. When we started using with Eclipse CDT we
had difficulties understanding how to create a CDT project for existing
sources. The warning scared us but we tried and the project creation ended
up working. At that time we were trying Netbeans for C and the project creation
for existing sources through the project wizard was almost straight forward. Nevertheless we realized Eclipse CDT is much more powerful and
reliable that Netbeans for C but so far harder to configure and less intuitive
for starters. I am willing to try this out. Regards, Felipe Antonio
|