what about clangd?

Daniel Mensinger daniel at mensinger-ka.de
Mon Aug 26 16:39:05 BST 2019

On Sat, 24 Aug 2019 11:38:22 +0200
René J. V.  Bertin <rjvbertin at gmail.com> wrote:

> René J.V. Bertin wrote:
> > About that: at first sight a proper implementation would take the existing
> > compile_commands.json project management code from the cmake plugin and move
> > it to a parent class where it becomes available to other project manager
> > plugins too?  
> And another JSON parser than the one from Qt, which fails on larger projects 
> like digiKam (with a compile_commands.json file that's 87Mb large).
> R.

Wait... seriously? I am using the QT JSON parser for for the meson plugin (the
introspection format is also in JSON (but different from compile_commands.json).

In that case would switching to nlohmann::json be OK? If yes, were should the
header be located in KDevelop?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20190826/47d51b6d/attachment.sig>

More information about the KDevelop-devel mailing list