Break Custom Buildsystem Plugin apart into 2 pieces.

[Aleix Pol]

On Mon, Feb 10, 2014 at 7:04 PM, Sergey Kalinichev <
kalinichev.so.0 at gmail.com> wrote:

> On Monday 10 February 2014 09:38:55 Sven Brauch wrote:
> > On Monday 10 February 2014 21:15:52 Sergey Kalinichev wrote:
> > > Well, I was talking more about session without opened projects at all.
> In
> > > your  case there is a project opened, so the *kdev4 file is accessible,
> > > and
> > > you could write in it: pathToOpenedInclude=...,
> > > includeDirectoriesForThatFile=...
> >
> > Yeah but then I would store the information about kdelibs' include paths
> in
> > my dolphin kdev4 file. That's not very nice for several obvious reasons.
>
> Yes, but only if kdelibs project isn't opened.
> Anyhow, I don't think we should resolve include dependencies for external
> includes manually, it should be done automatically imo.
>
> To the point, where to store information on the file system or in kdev4
> file?
>
>
> Regards
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop-devel
>

At the moment it's done automatically, by loading the project.

Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20140210/d3d11479/attachment.html>