projects
/
oota-llvm.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
[LIR] Make the LoopIdiomRecognize pass get analyses essentially the same
[oota-llvm.git]
/
docs
/
GettingStartedVS.rst
diff --git
a/docs/GettingStartedVS.rst
b/docs/GettingStartedVS.rst
index 7d773b7900d6f375bac6d6e22b1ccaab22737fcc..63e81f5165dfe865d610e585ef46668b0fc493c8 100644
(file)
--- a/
docs/GettingStartedVS.rst
+++ b/
docs/GettingStartedVS.rst
@@
-1,5
+1,3
@@
-.. _winvs:
-
==================================================================
Getting Started with the LLVM System using Microsoft Visual Studio
==================================================================
==================================================================
Getting Started with the LLVM System using Microsoft Visual Studio
==================================================================
@@
-36,7
+34,7
@@
Most of the tools build and work. ``bugpoint`` does build, but does
not work.
Additional information about the LLVM directory structure and tool chain
not work.
Additional information about the LLVM directory structure and tool chain
-can be found on the main
`Getting Started <GettingStarted.html>`_
page.
+can be found on the main
:doc:`GettingStarted`
page.
Requirements
Requirements
@@
-47,22
+45,20
@@
and software you will need.
Hardware
--------
Hardware
--------
-Any system that can adequately run Visual Studio 20
08
is fine. The LLVM
+Any system that can adequately run Visual Studio 20
13
is fine. The LLVM
source tree and object files, libraries and executables will consume
approximately 3GB.
Software
--------
source tree and object files, libraries and executables will consume
approximately 3GB.
Software
--------
-You will need Visual Studio 2008 or higher. Earlier versions of Visual
-Studio have bugs, are not completely compatible, or do not support the C++
-standard well enough.
+You will need Visual Studio 2013 or higher.
You will also need the `CMake <http://www.cmake.org/>`_ build system since it
generates the project files you will use to build with.
If you would like to run the LLVM tests you will need `Python
You will also need the `CMake <http://www.cmake.org/>`_ build system since it
generates the project files you will use to build with.
If you would like to run the LLVM tests you will need `Python
-<http://www.python.org/>`_. Version
s 2.4-2.7 are known to work. You will need
-`GnuWin32 <http://gnuwin32.sourceforge.net/>`_ tools, too.
+<http://www.python.org/>`_. Version
2.7 and newer are known to work. You will
+
need
`GnuWin32 <http://gnuwin32.sourceforge.net/>`_ tools, too.
Do not install the LLVM directory tree into a path containing spaces (e.g.
``C:\Documents and Settings\...``) as the configure step will fail.
Do not install the LLVM directory tree into a path containing spaces (e.g.
``C:\Documents and Settings\...``) as the configure step will fail.
@@
-101,8
+97,11
@@
Here's the short story for getting up and running quickly with LLVM:
using LLVM. Another important option is ``LLVM_TARGETS_TO_BUILD``,
which controls the LLVM target architectures that are included on the
build.
using LLVM. Another important option is ``LLVM_TARGETS_TO_BUILD``,
which controls the LLVM target architectures that are included on the
build.
- * See the
`LLVM CMake guide <CMake.html>`_
for detailed information about
+ * See the
:doc:`LLVM CMake guide <CMake>`
for detailed information about
how to configure the LLVM build.
how to configure the LLVM build.
+ * CMake generates project files for all build types. To select a specific
+ build type, use the Configuration manager from the VS IDE or the
+ ``/property:Configuration`` command line option when using MSBuild.
6. Start Visual Studio
6. Start Visual Studio
@@
-123,31
+122,32
@@
Here's the short story for getting up and running quickly with LLVM:
or run it from the command line. The program will print the
corresponding fibonacci value.
or run it from the command line. The program will print the
corresponding fibonacci value.
-8. Test LLVM
o
n Visual Studio:
+8. Test LLVM
i
n Visual Studio:
* If ``%PATH%`` does not contain GnuWin32, you may specify
``LLVM_LIT_TOOLS_DIR`` on CMake for the path to GnuWin32.
* You can run LLVM tests by merely building the project "check". The test
results will be shown in the VS output window.
* If ``%PATH%`` does not contain GnuWin32, you may specify
``LLVM_LIT_TOOLS_DIR`` on CMake for the path to GnuWin32.
* You can run LLVM tests by merely building the project "check". The test
results will be shown in the VS output window.
-.. FIXME: Is it up-to-date?
-
-9. Test LLVM:
+9. Test LLVM on the command line:
* The LLVM tests can be run by changing directory to the llvm source
directory and running:
.. code-block:: bat
* The LLVM tests can be run by changing directory to the llvm source
directory and running:
.. code-block:: bat
- C:\..\llvm>
llvm-lit
test
+ 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
- Note that quite a few of these test will fail.
+ This example assumes that Python is in your PATH variable, you
+ have built a Win32 Debug version of llvm with a standard out of
+ line build. You should not see any unexpected failures, but will
+ see many unsupported tests and expected failures.
A specific test or test directory can be run with:
.. code-block:: bat
A specific test or test directory can be run with:
.. code-block:: bat
- C:\..\llvm>
llvm-lit
test/path/to/test
+ 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
An Example Using the LLVM Tool Chain
An Example Using the LLVM Tool Chain
@@
-163,14
+163,14
@@
An Example Using the LLVM Tool Chain
return 0;
}
return 0;
}
-2. Next, compile the C file into a LLVM bitcode file:
+2. Next, compile the C file into a
n
LLVM bitcode file:
.. code-block:: bat
C:\..> clang -c hello.c -emit-llvm -o hello.bc
This will create the result file ``hello.bc`` which is the LLVM bitcode
.. code-block:: bat
C:\..> clang -c hello.c -emit-llvm -o hello.bc
This will create the result file ``hello.bc`` which is the LLVM bitcode
- that corresponds the
the
compiled program and the library facilities that
+ that corresponds the compiled program and the library facilities that
it required. You can execute this file directly using ``lli`` tool,
compile it to native assembly with the ``llc``, optimize or analyze it
further with the ``opt`` tool, etc.
it required. You can execute this file directly using ``lli`` tool,
compile it to native assembly with the ``llc``, optimize or analyze it
further with the ``opt`` tool, etc.
@@
-218,8
+218,8
@@
An Example Using the LLVM Tool Chain
Common Problems
===============
If you are having problems building or using LLVM, or if you have any other
Common Problems
===============
If you are having problems building or using LLVM, or if you have any other
-general questions about LLVM, please consult the `Frequently Asked Questions
-<FAQ
.html>`_
page.
+general questions about LLVM, please consult the
:doc:
`Frequently Asked Questions
+<FAQ
>`
page.
Links
Links