KDevelop syntax parser is barely usable

Steve the Fiddle stevethefiddle at gmail.com
Wed Nov 7 12:33:35 GMT 2018

On Wed, 7 Nov 2018 at 11:57, Sven Brauch <mail at svenbrauch.de> wrote:

> Hi,
> On Wednesday, 7 November 2018 12:11:12 CET Steve the Fiddle wrote:
> > The problem may be in part, due to
> > Audacity now making more use of C++11, and a little C++14, with more
> > templates and broader use of "modern" C++ idioms.
> FWIW, this is almost always a setup problem, usually include paths and/or
> preprocessor defines not being set up correctly. For CMake, KDevelop is
> very
> good at setting this up automatically, for automake much less so.

It would be really really nice if there were better documentation for
setting up. I've been struggling with this ever since KDevelop 5 was first
released, and I've managed to improve parsing from "totally useless" to
"barely usable". Despite all of my efforts I have been unable to improve

I did find some documentation re. setting up KDevelop for WxWidgets
applications, but it was many years out of date, so not really helpful.

If this is just a setup problem, and anyone can help me get KDevelop to to
parse the Audacity code reasonably well (
https://github.com/audacity/audacity), then I'd be happy to write up some
documentation for KDevelop (I write some of the documentation for Audacity).


> If include paths, compiler flags and definitions are set correctly,
> KDevelop's
> parser will be very close to perfect, since it uses clang behind the
> scenes.
> It doesn't matter how complex your template code is.
> Performance is a different topic, but correctness is very good these days.
> Best,
> Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20181107/f9d133a0/attachment.html>

More information about the KDevelop mailing list