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

[Manuel Klimek]

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:
> > On 06/12/2012 10:13 AM, David Röthlisberger wrote:
> >> what is the meaning of having multiple compilation commands for a
> single file?
> >
> > Multiple compilation commands can happen in some cases : for example
> > varying some defines to enable different part of the file (think
> > tablegen'erated files),
>
> Do you have any insights as to what user-level tools (such as
> clang_complete) can do in the presence of multiple such commands?
> Perhaps process (gather completions from) *all* of the file's different
> compilation commands?
>

For example, yep. I think for code_complete that's probably not what you
want, but for other tools (rename) that's a completely different story.


> > 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...

Cheers,
/Manuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20120614/93fae329/attachment.html>