KDevelop syntax parser is barely usable
Steve the Fiddle
stevethefiddle at gmail.com
Tue Nov 13 10:55:47 GMT 2018
On Wed, 7 Nov 2018 at 12:51, René J.V. Bertin <rjvbertin at gmail.com> wrote:
> On Wednesday November 07 2018 12:33:35 Steve the Fiddle wrote:
> >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
> It depends considerably on your local set-up, and your platform because of
> wxW . I have these defines configured:
> and the following custom include paths:
> (all copied directly from my audacity/.kdev4/audacity.kdev4 settings file).
> You can set these via the project settings dialog in KDevelop.
> I'm guessing that you could get the wx-related defines and paths from
> wx-config, so if KDevelop supported (supports?) shell expressions in its
> settings files you could (almost) write a template .kdev4 file. Almost,
> because typically you have to know which wx-config script to use...
Just a quick update,
Thanks to help from René, I've now got KDevelop working much better with
the Audacity code. It's still not perfect, but it is now much more usable.
The improvements came from modifying the "defines" and "custom includes
paths" (as René suggested). I'm still not sure that I really understand how
to use these properly, and the manual is rather sparse about this feature.
Setting this up was extremely time consuming because it takes so long to
re-parse the project before the effect of the changes can be seen.
I'll have another bash at configuring the project when I update Ubuntu, but
it's good enough for now :-)
Thanks for your support guys.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop