[cfe-dev] CompilationDatabase support added to libclang and python binding

David Röthlisberger david at rothlis.net
Sat Jun 16 03:03:58 PDT 2012

On 14 Jun 2012, at 12:21, Manuel Klimek wrote:
> On Thu, Jun 14, 2012 at 12:19 PM, David Röthlisberger <david at rothlis.net> wrote:
>> On 12 Jun 2012, at 10:44, Arnaud de Grandmaison wrote:
>>> or different other compile options in case
>>> multiple builds are done at the same time (debug, release, ...).
>> I don't think the tools need to worry about this, as different builds
>> will be done in different build directories, each with its own
>> compilation database.
> This is a use case we have, so I'll just go ahead and respectfully disagree...

Thanks for the reply -- I want to understand these use cases, so the
sooner I learn I'm wrong, the better. :-)

Do you expect to find compilation commands for both release and debug
builds (and release-with-debug, and cross compilations, and any other
kind of build you may have) in the same compile_commands.json?

If so, how do you generate that compile_commands.json? (As far as I can
tell, cmake only supports one build "mode" per build directory.)

If not, presumably your refactoring/renaming tool reads from multiple
compile_commands.json files?


More information about the cfe-dev mailing list