projects
/
oota-llvm.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Include llvm/Config/config.h in FileSystem.h as it depends upon HAVE_SYS_STAT_H which...
[oota-llvm.git]
/
docs
/
GettingStartedVS.rst
diff --git
a/docs/GettingStartedVS.rst
b/docs/GettingStartedVS.rst
index 628bfdc7cb5bc4be08113e8bd8cc44922c588906..63e81f5165dfe865d610e585ef46668b0fc493c8 100644
(file)
--- a/
docs/GettingStartedVS.rst
+++ b/
docs/GettingStartedVS.rst
@@
-34,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
@@
-45,20
+45,20
@@
and software you will need.
Hardware
--------
Hardware
--------
-Any system that can adequately run Visual Studio 201
2
is fine. The LLVM
+Any system that can adequately run Visual Studio 201
3
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 201
2
or higher.
+You will need Visual Studio 201
3
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.
@@
-97,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
@@
-215,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