Replies: 3 comments
-
If I understand correctly, the idea is that your build system exports the Perhaps some of you are interested in this? (cc @certik, @gnikit, @everythingfunctional, @rouson) |
Beta Was this translation helpful? Give feedback.
-
I have had a few conversations with the Codee developers. This is a functionality that would be useful for them. I was unaware of the bear tool, or that they had devised a workaround using it. |
Beta Was this translation helpful? Give feedback.
-
We have added additional public documentation in the following links: https://docs.codee.com/faqs#what-tools-are-available-for-generating-the-compile_commandsjson-file https://docs.codee.com/faqs#what-information-is-store-in-the-compile_commandsjson-file Just in case you find it useful for FPM development roadmap. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I was scrolling through the product sheet of Codee, a software product for automated code inspection.
Their Datasheet (PDF, 540 KB) mentions they support integration with fpm:
The documentation for the CMake and Ninja options is here:
compdb
)It looks like the compilation database originated from the Clang/LLVM community: https://clang.llvm.org/docs/JSONCompilationDatabase.html
The tool bear mentioned for FPM is this one: https://github.com/rizsotto/Bear. It intercepts your compile commands somehow, and generates the JSON database.
I wonder if this means, there are commercial users of Codee (and fpm), that asked for it.
Beta Was this translation helpful? Give feedback.
All reactions