Re: Support of Compilation Databases
Milian Wolff <[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <5409892.Ta0yPN1N1F@agathebauer> |
On Montag, 22. Oktober 2018 21:33:28 CEST Toni Dietze wrote: > Hello, > > I have a project with an involved build system and was quite happy to > read that kdevelop supports compilation databases [1]. However, I was > not able to find out how to convince kdevelop to use my compilation > database. I have two questions: > > 1. If I have a cmake project with enabled > CMAKE_EXPORT_COMPILE_COMMANDS, how do I notice that kdevelop actually > uses the generated compilation database? Since some time, we prefer the cmake server mode over the compilation database. Generally, you shouldn't need to enable CMAKE_EXPORT_COMPILE_COMMANDS yourself - just open a cmake project in KDevelop and everything should be handled automatically for you. > 2. Is it possible to load an arbitrary compilation database as > a project? This would be a great feature. It would already be helpful > if the code is only opened read-only just for browsing. Yes, that's indeed a good idea. But so far, it's not implemented from what I can remember. Adding such a feature to the custom buildsystem project manager would be a welcome addition! Cheers > [1] http://kfunk.org/2016/08/23/whats-new-in-kdevelop-5-0/#cmakesupport -- Milian Wolff [email protected] http://milianw.de
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEezawi1aUvUGg3A1+8zYW/HGdOX8FAlvO2JsACgkQ8zYW/HGd OX+PWhAAqrMc6ZRbLiQjElomdcUAN0hZluOaDDt8ncQkTZPPt+RVyNnJsTPk0P/9 Cr/h789ZfmjmzzvsjtsQde30vaI0fZbBrDgL9hgE8ZshECj0diZ2z7CgLRbd3lkM OQpM+DEdZ469Obob8pC2t0KBjYJ5883rSSAD/cGmL3SjrWNwDa40BnGjgThKZ8uc 0oWBfKWSY+r/MIQSplFXjRR1cKvYBfSAlaXvVOfj0kH5Xxksf8mhkR2gluRff8lL UZKXVGOCLSRDozNnUGCYsTdqt0TgMBKTf3rXPjlxzwptwQu8oqYjhzoBTv4Lowwu 9glIv87SbARLfsUCPtQkAGTIHHZM6VKZNsTuJGH/6ev6fqNSAvyBXeps0gO+NI+D XHvA5cV2LeQu9ZqgDl1fZ9kSNL1+4pIzTR1KQ7qZTmvE8mL9qd2U1MaJIn6SUigw yil2uVO5Slcsyg+vi7jULQlWWAvxnOAZ93E/Fa/iCzbpUYVQ/6zDxyotMQTjdwo6 nt3ZU5GEw42JQUyqoPP38uf5gjsduXMa0NIMQ7bkOXkZFMbeeP3pF9y4pk03N4Em fNp3dPzMcc/IkqgdcUHDHtL5UtJzqBp+fV3MKMonRcgHyPUQVQure4PIG6p+SDpN XlIWgPIAZJH0LmQRMpGxw4SS5BtK0NIJj1IUOReE3jTkc/Z3uuw= =WRcJ -----END PGP SIGNATURE-----