Bug 124310 - Multiple execution and debugging configurations
Summary: Multiple execution and debugging configurations
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: Automake (show other bugs)
Version: 3.3.1
Platform: Mandriva RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-26 18:43 UTC by Daniel Calviño Sánchez
Modified: 2008-06-30 22:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Calviño Sánchez 2006-03-26 18:43:07 UTC
Version:           3.3.1 (using KDE KDE 3.4.2)
Installed from:    Mandriva RPMs

Right now, only one execution configuration can be set.

If your project has more than one executable, you must change manually the execution configuration when you need to execute a different one to the last executed. For example, if you have your application and also a test suite for the app in another executable.

The same goes for execution args. You may need call the executable with different args for testing purposes, for example.

It would be great if you can set multiple execution configurations (like the building ones) so you can change between executables and its args without writing them again and again.

All of the above applies also for debugging.
Comment 1 Jens Dagerbo 2006-03-26 18:50:36 UTC
This is dependent on buildsystem, and at least for automake, the above is wrong.

The automake manager lets you specify a target as the "active target", which makes it the preferred target for build/execute/debug actions. It also let you set "run arguments" per target.
Comment 2 Amilcar do Carmo Lucas 2006-03-27 13:55:50 UTC
Yeap it is invalid.
Comment 3 Daniel Calviño Sánchez 2006-04-30 23:25:21 UTC
First of all, I apologize for the time that passed since I made the report. I thought that I had already answered, but I realized that I hadn't. Sorry.

About "active target", it's true. I haven't noticed it before. However, maybe I'm wrong, but as far as I can tell, you can only have one set of "run arguments" configured per target. So, if you want to execute that argument with different arguments, you have to change them explicitly in each execution.

For example, you want to execute program foo. It accepts the options "--bar" and "-o fileName". If you set the "run arguments" to be "--bar", whenever you want to execute it with "-o fileName" arguments, you need to change it in the active target. If you want to execute it again with "--bar", you need to change it.

It'll be better if you can specify various arguments set, so you select to run foo with "set1", and it uses "--bar" as arguments. If you select "set2", it'll run with "-o fileName", and so on. But you wouldn't need to rewrite the arguments each time, only select a different arguments set from a menu (for example).

I think that it can't be made at this moment. Please correct me if I'm wrong.
Comment 4 Andreas Pakulat 2008-06-30 22:34:32 UTC
this is fixed in kdevelop4, where you can now freely define executable configurations.