[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Importing Existing Code
|
The CDT debugger's Import Executable wizard creates a project. With PDE,
you also end up creating a project in the workspace via the Plug-ins and
Fragments import wizard.
I think from the user's perspective, he's
importing something into
the workspace that currently lives outside of it; thus the wizard being
in the import menu is more intuitive. No doubt, one can spin it a
different way, but that's my 2 cents.
John
At 01:42 PM 3/10/2010, Doug Schaefer wrote:
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 Martinez Figueroa.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
