target url from the project manager

[Matt Rogers]

On Tuesday 14 October 2008 21:50:55 Aleix wrote:
> On Wed, Oct 15, 2008 at 4:42 AM, Matt Rogers <mattr at kde.org> wrote:
> > On Tuesday 14 October 2008 21:36:02 Aleix wrote:
> > > hi list,
> > > this was discussed some time ago but we didn't find anything good but
> > > we didn't come up with a good interface for that. Now it is needed for
> > > the
> >
> > new
> >
> > > runcontroller, we want to be able to run any target.
> > >
> > > This is being solved in cmake adding the url to the UserData+1 (it is
> > > already possible to run a target from the projectmodelview if it is
> >
> > cmake),
> >
> > > we need a way to specify it in the platform interface.
> > >
> > > Last time we spoke about many things, returning: KUrl, KUrl::List,
> > > QMap<QString, KUrl> iirc. What do you think?
> > > Maybe we can add it only to test and executable target items so that
> > > the use case is simpler, I think that KUrl::List would be quite
> > > scalable for now. What do you think?
> > >
> > > bye!
> > > aleix
> >
> > What would the KUrl::List be used for? A list of all the executable URLs?
>
> Well, the problem is that 1 target might generate more than 1 file -> more
> than 1 url. The example that apaku used was that a library in windows is
> composed by many files.

Yeah, but you can't run a library, can you? I think we should limit this 
particular piece of information only to the executable targets. KUrl::List 
then becomes a good candidate for storing that information. 

But then again, perhaps I miss something and this is about more than just 
being able to have a list of executable targets per project.
-- 
Matt