| C++ programs in the console [message #77206] |
Mon, 28 July 2003 08:28  |
Eclipse User |
|
|
|
Originally posted by: sbh4.duke.edu
> If you have the right Binary parser(assuming PE) this is how CDT discover
> new binaries, since a file name *.exe is not an indication that this is
> a valid binary. But when you create a project you have the choice
> of choosing the parser not sure why you need to switch again.
The default parser when you make a new C++ project is the Elf parser,
so you do have to manually change it (you have the option of changing it
when you make the project).
My question was how would one run a C++ project in the Eclipse console
WITHOUT using the PE Windows parser or making a Run Configuration with
"Run...".
Here are the facts/problems as I've encountered them:
1) "Run As" doesn't work with the Elf parser (as far as I can tell)
2) If you double click your executable when you have the PE parser enabled,
Eclipse tries to open the file in its text browser and usually will incur an
out of memory error as a result.
3) Running via double-clicking is problematic because the DOS window closes
when the program finishes, making it impossible to see any text output that
is generated.
I just want to be able to run C++ programs as simply as possible without
risking a crash of Eclipse in the process (see #2).
I should explain that I am a CS student working in the Duke CS
department writing documentation on how to use Eclipse as well as writing
some Duke-specific plug-ins (for example, plug-ins that'll download/submit
assignments, etc). We're going to experiment with it as a possible
development platform for intro-level CS classes. An emphasis is placed on
ease-of-use because the students involved would not be computer veterans.
"Run..." is too many steps. You have to click "Run..", then "C/C++ Local",
then "New Configuration", then type in some name for your configuration,
then type in the name of the .exe file. It's rediculous.
Using the PE Windows parser, students will have to switch the parser
manually (remembering to do so everytime), will double-click and crash
Eclipse at least once, and even if they manage to get "Run As" to work, they
still have to click which executable they'd like to run (even if there is
only one) as well as specify a debugger (which as no meaning to them at
all). No good either.
And so I repeat, how would one run a C++ project in the Eclipse console
WITHOUT using the PE Windows parser or making a Run Configuration with
"Run..."?
I could probably make a hack'ish plug-in that'll auto-generate a run
configuration, but that seems silly (not too mention that it'd probably not
work with future versions of Eclipse).
Sam
|
|
|
| Re: C++ programs in the console [message #77473 is a reply to message #77206] |
Wed, 30 July 2003 14:24  |
| Eclipse User |
|
|
|
Originally posted by: alain.nowhere.ca
Sam Heald wrote:
> > If you have the right Binary parser(assuming PE) this is how CDT discover
> > new binaries, since a file name *.exe is not an indication that this is
> > a valid binary. But when you create a project you have the choice
> > of choosing the parser not sure why you need to switch again.
> The default parser when you make a new C++ project is the Elf parser,
> so you do have to manually change it (you have the option of changing it
> when you make the project).
I suppose we could have a global preference page, to set this.
> My question was how would one run a C++ project in the Eclipse console
> WITHOUT using the PE Windows parser or making a Run Configuration with
> "Run...".
> Here are the facts/problems as I've encountered them:
> 1) "Run As" doesn't work with the Elf parser (as far as I can tell)
> 2) If you double click your executable when you have the PE parser enabled,
> Eclipse tries to open the file in its text browser and usually will incur an
> out of memory error as a result.
> 3) Running via double-clicking is problematic because the DOS window closes
> when the program finishes, making it impossible to see any text output that
> is generated.
> I just want to be able to run C++ programs as simply as possible without
> risking a crash of Eclipse in the process (see #2).
> I should explain that I am a CS student working in the Duke CS
> department writing documentation on how to use Eclipse as well as writing
> some Duke-specific plug-ins (for example, plug-ins that'll download/submit
> assignments, etc). We're going to experiment with it as a possible
> development platform for intro-level CS classes. An emphasis is placed on
> ease-of-use because the students involved would not be computer veterans.
> "Run..." is too many steps. You have to click "Run..", then "C/C++ Local",
> then "New Configuration", then type in some name for your configuration,
> then type in the name of the .exe file. It's rediculous.
> Using the PE Windows parser, students will have to switch the parser
> manually (remembering to do so everytime), will double-click and crash
> Eclipse at least once, and even if they manage to get "Run As" to work, they
> still have to click which executable they'd like to run (even if there is
> only one) as well as specify a debugger (which as no meaning to them at
> all). No good either.
> And so I repeat, how would one run a C++ project in the Eclipse console
> WITHOUT using the PE Windows parser or making a Run Configuration with
> "Run..."?
> I could probably make a hack'ish plug-in that'll auto-generate a run
> configuration, but that seems silly (not too mention that it'd probably not
> work with future versions of Eclipse).
Yes, I see your point.
I suppose we could map the double-click and create a configuration
for you on the fly. This is probably to late for the 1.2
Questions:
- If you want to debug instead of running, what should the double-click
do ?
- If you have a cross-developement platform, building executable for
another target, what should the double-click do ?
- Double-click binding could be provided only by the "C/C++ view"
is this inconsistent compare to say the navigator view.
- What happen for say a "powerPC" executable ?
- If you have multiple debugger ?
etc ...
Do not forget the IDE is use for embedded cross-developement effort.
> Sam
|
|
|
Powered by
FUDForum. Page generated in 0.03311 seconds
] 
Search
Help
Register
Login
Home
