projects
/
oota-llvm.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Add call sequence start and end for __tls_get_addr
[oota-llvm.git]
/
docs
/
GettingStarted.rst
diff --git
a/docs/GettingStarted.rst
b/docs/GettingStarted.rst
index 8fb4daa5e26e0a46a492ecfde66b2a0779689a17..6aba500367939e24953ec8eff08ef26574d50f37 100644
(file)
--- a/
docs/GettingStarted.rst
+++ b/
docs/GettingStarted.rst
@@
-55,6
+55,12
@@
Here's the short story for getting up and running quickly with LLVM:
* ``cd llvm/projects``
* ``svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt``
* ``cd llvm/projects``
* ``svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt``
+#. Checkout Libomp (required for OpenMP support):
+
+ * ``cd where-you-want-llvm-to-live``
+ * ``cd llvm/projects``
+ * ``svn co http://llvm.org/svn/llvm-project/openmp/trunk openmp``
+
#. Checkout libcxx and libcxxabi **[Optional]**:
* ``cd where-you-want-llvm-to-live``
#. Checkout libcxx and libcxxabi **[Optional]**:
* ``cd where-you-want-llvm-to-live``
@@
-72,6
+78,8
@@
Here's the short story for getting up and running quickly with LLVM:
The usual build uses `CMake <CMake.html>`_. If you would rather use
autotools, see `Building LLVM with autotools <BuildingLLVMWithAutotools.html>`_.
The usual build uses `CMake <CMake.html>`_. If you would rather use
autotools, see `Building LLVM with autotools <BuildingLLVMWithAutotools.html>`_.
+ Although the build is known to work with CMake >= 2.8.8, we recommend CMake
+ >= v3.2, especially if you're generating Ninja build files.
* ``cd where you want to build llvm``
* ``mkdir build``
* ``cd where you want to build llvm``
* ``mkdir build``
@@
-82,7
+90,7
@@
Here's the short story for getting up and running quickly with LLVM:
* ``Unix Makefiles`` --- for generating make-compatible parallel makefiles.
* ``Ninja`` --- for generating `Ninja <http://martine.github.io/ninja/>`
* ``Unix Makefiles`` --- for generating make-compatible parallel makefiles.
* ``Ninja`` --- for generating `Ninja <http://martine.github.io/ninja/>`
- build files.
+ build files.
Most llvm developers use Ninja.
* ``Visual Studio`` --- for generating Visual Studio projects and
solutions.
* ``Xcode`` --- for generating Xcode projects.
* ``Visual Studio`` --- for generating Visual Studio projects and
solutions.
* ``Xcode`` --- for generating Xcode projects.
@@
-535,6
+543,13
@@
If you want to check out compiler-rt (required to build the sanitizers), run:
% cd llvm/projects
% git clone http://llvm.org/git/compiler-rt.git
% cd llvm/projects
% git clone http://llvm.org/git/compiler-rt.git
+If you want to check out libomp (required for OpenMP support), run:
+
+.. code-block:: console
+
+ % cd llvm/projects
+ % git clone http://llvm.org/git/openmp.git
+
If you want to check out libcxx and libcxxabi (optional), run:
.. code-block:: console
If you want to check out libcxx and libcxxabi (optional), run:
.. code-block:: console
@@
-634,7
+649,7
@@
To set up clone from which you can submit code using ``git-svn``, run:
% git config svn-remote.svn.fetch :refs/remotes/origin/master
% git svn rebase -l
% git config svn-remote.svn.fetch :refs/remotes/origin/master
% git svn rebase -l
-Likewise for compiler-rt and test-suite.
+Likewise for compiler-rt
, libomp
and test-suite.
To update this clone without generating git-svn tags that conflict with the
upstream Git repo, run:
To update this clone without generating git-svn tags that conflict with the
upstream Git repo, run:
@@
-648,7
+663,7
@@
upstream Git repo, run:
git checkout master &&
git svn rebase -l)
git checkout master &&
git svn rebase -l)
-Likewise for compiler-rt and test-suite.
+Likewise for compiler-rt
, libomp
and test-suite.
This leaves your working directories on their master branches, so you'll need to
``checkout`` each working branch individually and ``rebase`` it on top of its
This leaves your working directories on their master branches, so you'll need to
``checkout`` each working branch individually and ``rebase`` it on top of its