[cfe-dev] Clang static analysis under VisualStudio2012
Anton Yartsev
anton.yartsev at gmail.com
Tue Sep 2 16:58:22 PDT 2014
Hi,
I only managed to compile/analyze the source that includes 'windows.h'
when invoked the frontend (-cc1 option) and explicitly provided include
paths :
clang -cc1 -I "C:/Win-builds/x86_64-w64-mingw32/include" -I
"C:/Win-builds/include/c++/4.8.2" -I
"C:/Win-builds/include/c++/4.8.2/x86_64-w64-mingw32" -I
"F:/llvm_COMMON/-VS_build-/Debug/lib/clang/3.6.0/include" -analyze main.c
Currently failed to get rid of compilation errors reported from system
headers when tried to compile without the frontend invocation.
> -Xclang is for internal options. I don't have a Windows machine, but I would actually assume that "clang-cl.exe --analyze main.c" still works.
>
> Also CCing Anton, who's done some of the work making sure the analyzer runs on Windows. I'm not sure if he's tried any VS integration, though.
>
> Jordan
>
>
> On Aug 29, 2014, at 6:37 , bataliero1234 <a1463431 at trbvm.com> wrote:
>
>> Visual runs clang-cl.exe. Is it possible to force clang-cl to invoke
>> --analyze argument in clang.exe. ?
>>
>>> clang.exe --analyze main.c
>> Works correctly. But when I modify main.c and include "windows.h" I get
>>> "main.c:2:10: fatal error: 'windows.h' file not found"
>>
>> I have tried "-Xclang <arg> Pass <arg> to the clang compiler"
>>> CL.exe -Xclang --analyze main.c
>>> error: unknown argument: '--analyze'
>> but it doesn't help.
>>
>>
>>
>> --
>> View this message in context: http://clang-developers.42468.n3.nabble.com/Clang-static-analysis-under-VisualStudio2012-tp4041403p4041456.html
>> Sent from the Clang Developers mailing list archive at Nabble.com.
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
--
Anton
More information about the cfe-dev
mailing list