Can C++ support cope with changing include dirs?

David Nolden zwabel at googlemail.com
Sat Feb 13 22:07:30 UTC 2010


Am Samstag 13 Februar 2010 22:33:32 schrieb Andreas Pakulat:
> On 13.02.10 21:21:59, David Nolden wrote:
> > Am Samstag 13 Februar 2010 20:41:44 schrieb Andreas Pakulat:
> > > > A simpler solution for now is: Just let the build-manager return the
> > > > correct include-paths depending on the current configuration, and
> > > > additionally put a switch somewhere into the UI to reparse the whole
> > > > project using the already existing ProjectParseJob like after
> > > > startup.
> > >
> > > Ok, can you give me a hint where to look for the latter part?
> >
> > You mean for the parse-job? Just look at
> > ProjectController::projectLoaded() or similar, there the whole thing is
> > kicked in.
> 
> So just to clarify, kicking off a new parse-job for all project files
> does reparse everything with the new includes/defines? So far I thought
> that wouldn't happen because all files where already parsed (and didn't
> change since the first parse).

Maybe I would have to add a rule like "if the include-paths is different, re-
parse", or even better some tracking whether the changed include-path really 
needs to different found includes. That would be the next problem then.




More information about the KDevelop-devel mailing list