blob: 50f7aa123c5587a468cb9b5cdb4c1799bfb729d6 [file] [log] [blame]
Michael J. Spencerd93399a2012-06-21 23:27:09 +00001==================================================================
2Getting Started with the LLVM System using Microsoft Visual Studio
3==================================================================
4
5.. contents::
6 :local:
7
8
9Overview
10========
11Welcome to LLVM on Windows! This document only covers LLVM on Windows using
12Visual Studio, not mingw or cygwin. In order to get started, you first need to
13know some basic information.
14
Reid Klecknerba19d182016-01-11 20:51:57 +000015There are many different projects that compose LLVM. The first piece is the
16LLVM suite. This contains all of the tools, libraries, and header files needed
17to use LLVM. It contains an assembler, disassembler, bitcode analyzer and
18bitcode optimizer. It also contains basic regression tests that can be used to
19test the LLVM tools and the Clang front end.
Michael J. Spencerd93399a2012-06-21 23:27:09 +000020
Reid Klecknerba19d182016-01-11 20:51:57 +000021The second piece is the `Clang <http://clang.llvm.org/>`_ front end. This
22component compiles C, C++, Objective C, and Objective C++ code into LLVM
23bitcode. Clang typically uses LLVM libraries to optimize the bitcode and emit
24machine code. LLVM fully supports the COFF object file format, which is
25compatible with all other existing Windows toolchains.
Michael J. Spencerd93399a2012-06-21 23:27:09 +000026
Reid Klecknerba19d182016-01-11 20:51:57 +000027The last major part of LLVM, the execution Test Suite, does not run on Windows,
28and this document does not discuss it.
Michael J. Spencerd93399a2012-06-21 23:27:09 +000029
30Additional information about the LLVM directory structure and tool chain
Sean Silva1703e702014-04-08 21:06:22 +000031can be found on the main :doc:`GettingStarted` page.
Michael J. Spencerd93399a2012-06-21 23:27:09 +000032
33
34Requirements
35============
36Before you begin to use the LLVM system, review the requirements given
37below. This may save you some trouble by knowing ahead of time what hardware
38and software you will need.
39
40Hardware
41--------
Reid Kleckner6130a2d2016-10-19 23:04:41 +000042Any system that can adequately run Visual Studio 2015 is fine. The LLVM
Michael J. Spencerd93399a2012-06-21 23:27:09 +000043source tree and object files, libraries and executables will consume
44approximately 3GB.
45
46Software
47--------
Reid Kleckner6130a2d2016-10-19 23:04:41 +000048You will need Visual Studio 2015 or higher, with the latest Update installed.
Michael J. Spencerd93399a2012-06-21 23:27:09 +000049
50You will also need the `CMake <http://www.cmake.org/>`_ build system since it
Mehdi Amini0695e5b2016-11-09 01:44:42 +000051generates the project files you will use to build with.
Michael J. Spencerd93399a2012-06-21 23:27:09 +000052
53If you would like to run the LLVM tests you will need `Python
Rafael Espindola21a400852014-12-12 15:29:31 +000054<http://www.python.org/>`_. Version 2.7 and newer are known to work. You will
55need `GnuWin32 <http://gnuwin32.sourceforge.net/>`_ tools, too.
Michael J. Spencerd93399a2012-06-21 23:27:09 +000056
57Do not install the LLVM directory tree into a path containing spaces (e.g.
58``C:\Documents and Settings\...``) as the configure step will fail.
59
60
61Getting Started
62===============
63Here's the short story for getting up and running quickly with LLVM:
64
651. Read the documentation.
662. Seriously, read the documentation.
673. Remember that you were warned twice about reading the documentation.
684. Get the Source Code
69
70 * With the distributed files:
71
72 1. ``cd <where-you-want-llvm-to-live>``
73 2. ``gunzip --stdout llvm-VERSION.tar.gz | tar -xvf -``
74 (*or use WinZip*)
75 3. ``cd llvm``
76
77 * With anonymous Subversion access:
78
79 1. ``cd <where-you-want-llvm-to-live>``
80 2. ``svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm``
81 3. ``cd llvm``
82
835. Use `CMake <http://www.cmake.org/>`_ to generate up-to-date project files:
84
85 * Once CMake is installed then the simplest way is to just start the
86 CMake GUI, select the directory where you have LLVM extracted to, and
87 the default options should all be fine. One option you may really
88 want to change, regardless of anything else, might be the
89 ``CMAKE_INSTALL_PREFIX`` setting to select a directory to INSTALL to
90 once compiling is complete, although installation is not mandatory for
91 using LLVM. Another important option is ``LLVM_TARGETS_TO_BUILD``,
92 which controls the LLVM target architectures that are included on the
93 build.
Keno Fischer3c305442016-02-07 19:36:54 +000094 * If CMake complains that it cannot find the compiler, make sure that
95 you have the Visual Studio C++ Tools installed, not just Visual Studio
96 itself (trying to create a C++ project in Visual Studio will generally
97 download the C++ tools if they haven't already been).
Sean Silva1703e702014-04-08 21:06:22 +000098 * See the :doc:`LLVM CMake guide <CMake>` for detailed information about
Michael J. Spencerd93399a2012-06-21 23:27:09 +000099 how to configure the LLVM build.
Yaron Kereneadc9b32014-06-05 16:42:26 +0000100 * CMake generates project files for all build types. To select a specific
101 build type, use the Configuration manager from the VS IDE or the
102 ``/property:Configuration`` command line option when using MSBuild.
Aaron Ballman472278a2017-05-25 21:01:30 +0000103 * By default, the Visual Studio project files generated by CMake use the
104 32-bit toolset. If you are developing on a 64-bit version of Windows and
105 want to use the 64-bit toolset, pass the ``-Thost=x64`` flag when
106 generating the Visual Studio solution. This requires CMake 3.8.0 or later.
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000107
1086. Start Visual Studio
109
110 * In the directory you created the project files will have an ``llvm.sln``
111 file, just double-click on that to open Visual Studio.
112
1137. Build the LLVM Suite:
114
115 * The projects may still be built individually, but to build them all do
116 not just select all of them in batch build (as some are meant as
117 configuration projects), but rather select and build just the
118 ``ALL_BUILD`` project to build everything, or the ``INSTALL`` project,
119 which first builds the ``ALL_BUILD`` project, then installs the LLVM
120 headers, libs, and other useful things to the directory set by the
121 ``CMAKE_INSTALL_PREFIX`` setting when you first configured CMake.
122 * The Fibonacci project is a sample program that uses the JIT. Modify the
123 project's debugging properties to provide a numeric command line argument
124 or run it from the command line. The program will print the
125 corresponding fibonacci value.
126
Aaron Ballman1e9d9b22014-01-23 20:46:44 +00001278. Test LLVM in Visual Studio:
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000128
129 * If ``%PATH%`` does not contain GnuWin32, you may specify
130 ``LLVM_LIT_TOOLS_DIR`` on CMake for the path to GnuWin32.
131 * You can run LLVM tests by merely building the project "check". The test
132 results will be shown in the VS output window.
133
Aaron Ballman1e9d9b22014-01-23 20:46:44 +00001349. Test LLVM on the command line:
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000135
136 * The LLVM tests can be run by changing directory to the llvm source
137 directory and running:
138
139 .. code-block:: bat
140
Aaron Ballmanc8aefe42013-05-01 19:13:50 +0000141 C:\..\llvm> python ..\build\bin\llvm-lit --param build_config=Win32 --param build_mode=Debug --param llvm_site_config=../build/test/lit.site.cfg test
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000142
Aaron Ballmanc8aefe42013-05-01 19:13:50 +0000143 This example assumes that Python is in your PATH variable, you
144 have built a Win32 Debug version of llvm with a standard out of
145 line build. You should not see any unexpected failures, but will
146 see many unsupported tests and expected failures.
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000147
148 A specific test or test directory can be run with:
149
150 .. code-block:: bat
151
Aaron Ballmanc8aefe42013-05-01 19:13:50 +0000152 C:\..\llvm> python ..\build\bin\llvm-lit --param build_config=Win32 --param build_mode=Debug --param llvm_site_config=../build/test/lit.site.cfg test/path/to/test
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000153
154
155An Example Using the LLVM Tool Chain
156====================================
157
1581. First, create a simple C file, name it '``hello.c``':
159
160 .. code-block:: c
161
162 #include <stdio.h>
163 int main() {
164 printf("hello world\n");
165 return 0;
166 }
167
Daniel Dunbar06b9f9e2013-08-16 23:30:19 +00001682. Next, compile the C file into an LLVM bitcode file:
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000169
170 .. code-block:: bat
171
172 C:\..> clang -c hello.c -emit-llvm -o hello.bc
173
174 This will create the result file ``hello.bc`` which is the LLVM bitcode
Sylvestre Ledru35521e22012-07-23 08:51:15 +0000175 that corresponds the compiled program and the library facilities that
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000176 it required. You can execute this file directly using ``lli`` tool,
177 compile it to native assembly with the ``llc``, optimize or analyze it
178 further with the ``opt`` tool, etc.
179
180 Alternatively you can directly output an executable with clang with:
181
182 .. code-block:: bat
183
184 C:\..> clang hello.c -o hello.exe
185
186 The ``-o hello.exe`` is required because clang currently outputs ``a.out``
187 when neither ``-o`` nor ``-c`` are given.
188
1893. Run the program using the just-in-time compiler:
190
191 .. code-block:: bat
192
193 C:\..> lli hello.bc
194
1954. Use the ``llvm-dis`` utility to take a look at the LLVM assembly code:
196
197 .. code-block:: bat
198
199 C:\..> llvm-dis < hello.bc | more
200
2015. Compile the program to object code using the LLC code generator:
202
203 .. code-block:: bat
204
205 C:\..> llc -filetype=obj hello.bc
206
2076. Link to binary using Microsoft link:
208
209 .. code-block:: bat
210
211 C:\..> link hello.obj -defaultlib:libcmt
212
2137. Execute the native code program:
214
215 .. code-block:: bat
216
217 C:\..> hello.exe
218
219
220Common Problems
221===============
222If you are having problems building or using LLVM, or if you have any other
Sean Silva1703e702014-04-08 21:06:22 +0000223general questions about LLVM, please consult the :doc:`Frequently Asked Questions
224<FAQ>` page.
Michael J. Spencerd93399a2012-06-21 23:27:09 +0000225
226
227Links
228=====
229This document is just an **introduction** to how to use LLVM to do some simple
230things... there are many more interesting and complicated things that you can
231do that aren't documented here (but we'll gladly accept a patch if you want to
232write something up!). For more information about LLVM, check out:
233
234* `LLVM homepage <http://llvm.org/>`_
235* `LLVM doxygen tree <http://llvm.org/doxygen/>`_
236