RFC: [Bug 201337] Create launch configurations for executables

Aleix Pol aleixpol at kde.org
Fri Jul 24 14:10:55 UTC 2009


Maybe, since we have all this vertitas stuff, the correct thing to do would
be to add the test targets found to veritas and just the non-tests to the
launch configurations. Then we just should find some way to run the tests
inside the debugger in case there is something to debug.

On Fri, Jul 24, 2009 at 7:00 AM, Andreas Pakulat <apaku at gmx.de> wrote:

> Hi,
>
> On 24.07.09 11:58:32, Pau Garcia i Quiles wrote:
> > For CMake projects, KDevelop should automatically create a "launch
> > configuration" for each ADD_EXECUTABLE, KDE4_ADD_EXECUTABLE, etc found.
> > Currently, you need to create the launch configurations manually.
> QtCreator
> > creates them automatically, and it's very convenient.
>
> I've tried this and ended up with about 4 pages of menu item under the
> Launch Configurations submenu (due to all the unit-tests, probably would
> be even more for kdelibs or similar). Apart from that, its basically
> impossible to do this once we have more than 1 launch config type as
> then the runcontroller doesn't know which launch config type to use for
> the configs.
>
> One option would be to do this in the plugin that actually supplies the
> launch config type, i.e. the execute plugin. However that would mean
> making more of the shell implementation of launch configs public and
> accessible by plugins. Also the plugin also has no idea about which
> of the targets it should really create launch configs for.
>
> I don't think it makes sense to auto-add all executable targets when
> loading a project. David already had suggestions how to make it easier
> to execute targets from the project, I also thought about having a
> simple option "Execute this target" and "Debug this target" in the
> context menu's for targets.
>
> Opinions?
>
> Andreas
>
> --
> Your aim is high and to the right.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090724/08696e21/attachment.html>


More information about the KDevelop-devel mailing list