Kdevelop parser

[Milian Wolff]

On Montag, 29. Februar 2016 19:05:50 CET Erik Rull wrote:
> Hi all,
> 
> thanks for your help.
> 
> The better question would be: why is it actually parsed?
> I have some files in the intel-subdirectory that is linked into my project
> via link (ln -snf) but only the files from a certain subdirectory are
> actually required. The rest are binary packages that are not in use by my
> project.
> 
> Is it possible to define something like:
> Parse not the whole sub-directory a/b but parse the subsub-directory a/b/c?
> The "c" directory would be my toolchain tree and this would be sufficient
> for code completion.

Try to define project filters like such:

exclude a/b/*
include a/b/c

if I wrote the code correctly, this should work. If not, please file a bug.

> Is there a way to see why Kdevelop tries to parse a certain file, that
> means to track how this file was found and selected for parsing?

Not really, besides whatever is shown in the project tree view.

> Best regards,


-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20160229/18195c29/attachment.sig>