[kdevplatform] a5caf03: Make it possible to add pre-configured launch conf
Andreas Pakulat
apaku at gmx.de
Fri Oct 22 07:03:05 UTC 2010
On 21.10.10 21:51:02, Aleix Pol wrote:
> diff --git a/plugins/execute/nativeappconfig.cpp b/plugins/execute/nativeappconfig.cpp
> index 5edb957..7aadbfc 100644
> --- a/plugins/execute/nativeappconfig.cpp
> +++ b/plugins/execute/nativeappconfig.cpp
> @@ -395,5 +395,64 @@ void NativeAppConfigType::configureLaunchFromCmdLineArguments ( KConfigGroup cfg
> cfg.sync();
> }
>
> +QList<KDevelop::ProjectTargetItem*> targetsInFolder(KDevelop::ProjectFolderItem* folder)
> +{
> + QList<KDevelop::ProjectTargetItem*> ret;
> + foreach(KDevelop::ProjectFolderItem* f, folder->folderList())
> + ret += targetsInFolder(f);
> +
> + ret += folder->targetList();
> + return ret;
> +}
> +
> +QList<QAction*> NativeAppConfigType::launcherSuggestions()
> +{
> + static QList<QAction*> ret;
> + if(!ret.isEmpty())
> + return ret;
> +
This means this is only filled once during the execution of kdevelop,
what happens if I open a second/third/.. project?
Andreas
--
All the troubles you have will pass away very quickly.
More information about the KDevelop-devel
mailing list