options to run

[Andreas Pakulat]

On 13.10.08 13:29:39, Aleix wrote:
> On Sun, Oct 12, 2008 at 11:47 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> > On 12.10.08 22:43:20, Aleix wrote:
> > > On Sun, Oct 12, 2008 at 9:24 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> > > > On 12.10.08 21:04:31, Aleix wrote:
> > - choose a runnable target from the project tree as target to run
> 
> > - define a list of dependent targets/dirs/files from the project tree that
> >  should be built before running this target - no matter wether we used a
> >  project-item target or just a plain executable
> 
> So your idea is to have  a buildset for every run-target?
> It would be interesting to have these project-wise targets in the project
> configuratiion as volodya suggested in another thread too.

Well, kind of yes. Not necessarily with the current implementation of
buildset. But I guess some code-sharing would be needed.

> > Yeah I think thats what we should have. That way I can work on my
> > kdevplatform plugin and have KDevelop build it before running kdevelop.
> > Plus I don't need kdevelop open as project necessarily, because I can just
> > use the installed app. This is something developers of "external" plugins
> > are going to like, think about plasma devs writing their plugin and just
> > executing a script which re-starts plasma so it finds the new plugin and
> > loads it.
> 
> Agree, but it might not be a good idea to have too complicated targets to
> setup i think.

Yes, setting up a target should be easy. Like right-clicking on it and
choosing "run". But of course we also want to support more complicated
setups...
 
> I'll try to come up with smth today, ok?

Sure, thanks.

Andreas

-- 
Good night to spend with family, but avoid arguments with your mate's
new lover.