what about clangd?
tcanabrava at kde.org
Mon Aug 26 16:50:35 BST 2019
On Mon, Aug 26, 2019 at 5:39 PM Daniel Mensinger <daniel at mensinger-ka.de>
> 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
> > > compile_commands.json project management code from the cmake plugin
> and move
> > > it to a parent class where it becomes available to other project
> > > plugins too?
> > And another JSON parser than the one from Qt, which fails on larger
> > 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
> introspection format is also in JSON (but different from
> In that case would switching to nlohmann::json be OK? If yes, were should
> header be located in KDevelop?
It's not as easy to integrate Qt code to the Nlohmann::json as it has no
knowledge of Qt (and uses the std::string instead), but it's so much easier
to handle things, and it can handle gigantic json files.
it also does not know about QVariants. so there's a little of boilerplate
to write if you use it.
but it's a really serious project and tried to be as fast and efficient as
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel