Re: KDevelop syntax parser is barely usable
René J.V. Bertin <[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <5133731.ODoNl7qlcr@bola> |
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 Audacity). It depends considerably on your local set-up, and your platform because of wxW . I have these defines configured: WXUSINGDLL=1 _FILE_OFFSET_BITS=64 __WXGTK__=1 and the following custom include paths: 1=/opt/local/libexec/wxWidgets/3.0/include/wx-3.0 2=/opt/local/libexec/wxWidgets/3.0/lib/wx/include/gtk2-unicode-3.0 (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... R.