v5.1.4/5.2 problems parsing its own code?

[René J.V. Bertin]

Interestingly I just realised I was still using build of the clang parser plugin that predated that commit on one of my machines. Yet the parsing issues disappeared on that machine too. The commit in question only touched clang plugin sources, so apparently the issues I was experiencing were caused by something else (like not using canonical paths).

R.

On Thursday September 21 2017 15:06:29 Milian Wolff wrote:
>> https://bugs.kde.org/show_bug.cgi?id=384775
>
>Everyone affected by this: Please try again, I think I just fixed the issue.
>
>Cheers
>
>