[PATCH] Header dependencies support for modularize

Kim Gräsman kim.grasman at gmail.com
Wed Aug 21 13:20:31 PDT 2013


Hi Manuel,

On Wed, Aug 21, 2013 at 3:15 PM, Manuel Klimek <klimek at google.com> wrote:
> On Wed, Aug 21, 2013 at 3:06 PM, Kim Gräsman <kim.grasman at gmail.com> wrote:
>>
>> I've wanted to add compilation database support, but the way tooling
>> is wired it seems I need to extract compilation db and source paths
>> from the command-line and pass them to ClangTool::ClangTool. The
>> compilation db is (sort of) handled by FixedCompilationDatabase, but
>> it seems the source paths are assumed to be tool arguments, not Clang
>> arguments.
>
>
> Use a clang plugin if you want to run as part of a build. The code that has
> your main logic is basically the same, and you can use ASTMatchers and other
> stuff from tooling in your clang plugin just fine.

Thanks, but this tool already exists:
http://code.google.com/p/include-what-you-use

and we'd like to have it act either as part of a build or stand-alone
with a compilation database. It seems hard to combine the two,
currently.

I'm interested in the Tooling approach because it would cut lots of
boilerplate from our setup and make us less exposed to driver changes.

- Kim




More information about the cfe-commits mailing list