However, well, let's just say that the LLVM documentation isn't that intuitive for newcomers, especially if you were expecting to be able to download a nice Windows binary package and roll. This quick recipe on setting up a complete Clang static-analyzer environment for MinGW attempts to remedy that. As usual, what is presented below worked on my environment at the time of the post - I make no guarantee that it will work elsewhere, especially if you choose to deviate from the guide.
Also, before you start, please be aware that this whole process will send you back about 11 GB in terms of disk space, so make sure you have adequate room.
- Install MinGW (32 bit!) using the latest msys-get-inst (just run the GUI installer) picking up the very latest packages.
For the installation directory, I used
D:\Clang, which I will assume to also be yours for for the rest of the guide - please modify accordingly. With regards to the installation packages, select
MinGW Compiler Suite→
C compiler(which should be selected by default),
MinGW Compiler Suite→
C++ compiler, and
MinGW Developer Toolkitto ensure that binutils and all the necessary tools to build clang, except Python, are available. You should also select
MSYS Basic System, so that a shell is available. You probably also want to play it safe by picking up the pre-packaged repository catalog for MinGW. The retrieval and installation of the packages will take a few minutes.
- Download Python v2.x (32 bit installer) from http://www.python.org/download/.
D:\Clang\binas the installation directory and unselect everything but
Python Interpreter and Libraries, as this is all you really need from Python.
IMPORTANT: Using python 3.2.2 produced an error on my machine during the build, so make sure you pick v2.x.
- [OBSOLETE: You can skip to the next step as per comments below]
Download the latest
(Experimental) Clang Binaries for Mingw32/x86from http://llvm.org/releases/download.html. Extract its content (
D:\Clang, overwriting any existing files. We do not care about headers being overwritten as this setup will be used for Clang and Clang only. Always make sure
llvm-gccis installed in the
/bindirectory of MinGW, unless you want to see a
CreateProcess()error when running it (or want to have to duplicate the binutils files which we already got installed from picking up the
MinGW Developer Toolkit).
- After installing an Subversion client such as Tortoise-SVN if needed:
llvmfrom http://llvm.org/svn/llvm-project/llvm/trunk (this is a Subversion URI), into
clangfrom http://llvm.org/svn/llvm-project/cfe/trunk, into
NB: you may have to checkout
llvmfirst, then move it to the right location if your Subversion client doesn't let you checkout a repository inside an existing repository.
- Open an msys shell by launching
D:\Clang\msys\1.0\msys.batand issue the following commands:
cd /src mkdir build cd build export CC=gcc export CXX=g++ ../llvm/configure --disable-docs --enable-optimized --enable-targets=x86,x86_64 --prefix=/mingw make -j2The
--prefixensures that our files will be installed in the
bindirectory of MinGW and the two export lines avoid the need to install the Clang binaries to be able to recompile (As per now obsolete Step 3). Note that, in the msys shell,
/mingwalways point to the root directory where you installed MinGW (here
D:\clang) regardless of the name you used. I would strongly advise against using a different directory, or not specifying the
--prefixoption (in which case
/usr/localwill be used as default), as I ran into issues when I tried (the static-analyzer failed to locate
<stdio.h>when parsing sources). As usual, the
-j2, which specifies the number of jobs to run in parallel, is there to make use of as many cores as we have (here two). Adjust according to your platform.
Oh, and if you want to know why we use
--enable-optimized, see the very end of this post...
- Go for a walk or something. Some of the libraries and executables are huge (hundreds of MB in size) so this whole process will take a while. During the various compilation runs I conducted, I chanced in one that froze (one
makeprocess using 100% of the CPU and never completing) and another where Windows reported
"llvm-tblgen has stopped working", so don't be surprised if the compilation doesn't work quite right first time 'round -- it's fairly heavy on resources.
- If the compilation completed, then you can run:
make install -j2Note that this operation will take some time too!
- Copy all the content of
Copy all the content of
- Issue the command:
ln -s /mingw/bin/ccc-analyzer /mingw/bin/c++-analyzerThe reason we're re-creating this symbolic link (which on Windows ends up being a duplicate rather than a link anyway) is that the one from the file provided by LLVM only works on UNIX systems.
D:\clang\bin\scan-build, line 100, and remove the
/binthere to have:
my $ClangSB = Cwd::realpath("$RealBin/clang");
If you don't do that,
scan-buildwill look for clang in
/mingw/bin/binand obviously fail to locate it.
- Finally, since we had to override them, you shouldn't forget to undefine the
export CC= export CXX=
Success looks like what?
$ cd /d/libusb-pbatard $ scan-build ./autogen.sh (...) $ scan-build make make all-recursive make: Entering directory `/d/libusb-pbatard' Making all in libusb make: Entering directory `/d/libusb-pbatard/libusb' CC libusb_1_0_la-core.lo core.c:1626:3: warning: Value stored to 'r' is never read r = 0; ^ ~ 1 warning generated. CC libusb_1_0_la-descriptor.lo CC libusb_1_0_la-io.lo io.c:1819:8: warning: Call to 'malloc' has an allocation size of 0 bytes fds = malloc(sizeof(*fds) * nfds); ^ ~~~~~~~~~~~~~~~~~~~ 1 warning generated. CC libusb_1_0_la-sync.lo CC libusb_1_0_la-poll_windows.lo CC libusb_1_0_la-windows_usb.lo os/windows_usb.c:1218:26: warning: Value stored to 'discdevs' during its initialization is never read struct discovered_devs *discdevs = *_discdevs; ^ ~~~~~~~~~~ os/windows_usb.c:1297:4: warning: Value stored to 'session_id' is never read session_id = 0; ^ ~ 2 warnings generated. RC libusb-1.0.lo CC libusb_1_0_la-threads_windows.lo os/threads_windows.c:115:2: warning: Value stored to 'prev_pos' is never read prev_pos = pos = NULL; ^ ~~~~~~~~~~ 1 warning generated. CCLD libusb-1.0.la Creating library file: .libs/libusb-1.0.dll.a make: Leaving directory `/d/libusb-pbatard/libusb' Making all in doc make: Entering directory `/d/libusb-pbatard/doc' make: Nothing to be done for `all'. make: Leaving directory `/d/libusb-pbatard/doc' Making all in examples make: Entering directory `/d/libusb-pbatard/examples' CC xusb.o xusb.c: In function 'test_mass_storage': xusb.c:443:9: warning: variable 'junk' set but not used [-Wunused-but-set-variable] xusb.c:520:4: warning: Value stored to 'junk' is never read junk = fwrite(data, 1, size, fd); ^ ~~~~~~~~~~~~~~~~~~~~~~~~~ 1 warning generated. CCLD xusb.exe ./.libs/lt-xusb.c:692:11: warning: Value stored to 'len' during its initialization is never read int len = strlen (new_value); ^ ~~~~~~~~~~~~~~~~~~ 1 warning generated. CC lsusb.o CCLD lsusb.exe ./.libs/lt-lsusb.c:692:11: warning: Value stored to 'len' during its initialization is never read int len = strlen (new_value); ^ ~~~~~~~~~~~~~~~~~~ 1 warning generated. make: Leaving directory `/d/libusb-pbatard/examples' make: Entering directory `/d/libusb-pbatard' make: Leaving directory `/d/libusb-pbatard' make: Leaving directory `/d/libusb-pbatard' scan-build: 8 bugs found. scan-build: Run 'scan-view /tmp/scan-build-2011-10-24-1' to examine bug reports.This is a typical result that Clang will (eventually - the analysis takes some time!) churn through. One false positive (that 'junk' variable is meant to be ignored, and only serves to eliminate a warning about not reading the return value from fwrite) and apart from that malloc code, everything looks fairly minor. Even on its very first report from clang, which of course we will act upon, libusb-1.0 on Windows doesn't appear to fare too bad!
If you followed the guide above, chances are you'll be using separate installations for the standard MinGW/MinGW-w64 and the Clangified ones. As such, you may want a title on the msys shell window that reflects that you are in a Clang environment, to identify which is which more easily.
To change the msys commandline window title, just edit your
D:\clang\msys\1.0\etc\profile, locate the line:
export PS1='\[\033]0;$MSYSTEM:\w\007and replace
$MSYSTEMwith the title you want.
Displayed after spending more than one hour of compilation, using gcc:
llvm: ***** Completed Debug+Asserts Build llvm: ***** Note: Debug build can be 10 times slower than an llvm: ***** optimized build. Use make ENABLE_OPTIMIZED=1 to llvm: ***** make an optimized build. Alternatively you can llvm: ***** configure with --enable-optimized.Now you tell me!?! Shouldn't that be the kind of info you want to display after someone issues