[cfe-dev] How do clang tools handle input like '/path/to/files/*.c'?

[Pradnya Laxman Khalate]

Hi,


I am studying Clang for an academic project. I am using Clang from Windows. I was able to build it with MSVS 2013. I am using MinGW and msys shell to run the Clang tools from the command line.


As a trial, I gave a path input to clang-tidy tool -

 clang-tidy ../<path>/*.cpp -checks="readability-braces-around-statements" --


It is interesting that the tool was able to handle this without compilation database (Note --).

To see how this input is handled by 'CommonOptionsParser', I gave the same input through Visual Studio debugger in my clang build. However, the tool throws an error for the argument '/path/*.cpp'.

In general, how do clang tools handle such 'SourcePath' input?


Is it possible to run a clang tool on all files in a directory by using FixedCompilationDatabase? (It returns nullptr for getAllFiles())

In Windows, I have to manually write the compile_commands.json file, which is an additional task for huge source code.


Any suggestions / guidance is appreciated.


Thanks,

Pradnya


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150331/21df8a9b/attachment.html>