summaryrefslogtreecommitdiffstats
path: root/www/get_started.html
diff options
context:
space:
mode:
Diffstat (limited to 'www/get_started.html')
-rw-r--r--www/get_started.html33
1 files changed, 19 insertions, 14 deletions
diff --git a/www/get_started.html b/www/get_started.html
index d819532..7756f9e 100644
--- a/www/get_started.html
+++ b/www/get_started.html
@@ -53,21 +53,29 @@ follows:</p>
</li>
<li>Checkout Clang:
<ul>
- <li><tt>cd llvm/tools</tt>
+ <li><tt>cd llvm/tools</tt></li>
<li><tt>svn co http://llvm.org/svn/llvm-project/cfe/trunk clang</tt></li>
+ <li><tt>cd ../..</tt></li>
+ </ul>
+ </li>
+ <li>Checkout extra Clang Tools: (optional)
+ <ul>
+ <li><tt>cd llvm/tools/clang/tools</tt></li>
+ <li><tt>svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk
+ extra</tt></li>
+ <li><tt>cd ../../../..</tt></li>
</ul>
</li>
<li>Checkout Compiler-RT:
<ul>
- <li><tt>cd ../..</tt> (back to where you started)</li>
- <li><tt>cd llvm/projects</tt>
+ <li><tt>cd llvm/projects</tt></li>
<li><tt>svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk
compiler-rt</tt></li>
+ <li><tt>cd ../..</tt></li>
</ul>
</li>
<li>Build LLVM and Clang:
<ul>
- <li><tt>cd ../..</tt> (back to where you started)</li>
<li><tt>mkdir build</tt> (for building without polluting the source dir)
</li>
<li><tt>cd build</tt></li>
@@ -83,15 +91,12 @@ follows:</p>
</li>
<li>If you intend to work on Clang C++ support, you may need to tell it how
- to find your C++ standard library headers. If Clang cannot find your
- system libstdc++ headers, please follow these instructions:
- <ul>
- <li>'<tt>gcc -v -x c++ /dev/null -fsyntax-only</tt>' to get the
- path.</li>
- <li>Look for the comment "FIXME: temporary hack:
- hard-coded paths" in <tt>clang/lib/Frontend/InitHeaderSearch.cpp</tt> and
- change the lines below to include that path.</li>
- </ul>
+ to find your C++ standard library headers. In general, Clang will detect
+ the best version of libstdc++ headers available and use them - it will
+ look both for system installations of libstdc++ as well as installations
+ adjacent to Clang itself. If your configuration fits neither of these
+ scenarios, you can use the <tt>--with-gcc-toolchain</tt> configure option
+ to tell Clang where the gcc containing the desired libstdc++ is installed.
</li>
<li>Try it out (assuming you add llvm/Debug+Asserts/bin to your path):
<ul>
@@ -267,7 +272,7 @@ $ <b>clang -fsyntax-only ~/t.c -pedantic</b>
<h3>Pretty printing from the AST:</h3>
-<p>Note, the <tt>-cc1</tt> argument indicates the the compiler front-end, and
+<p>Note, the <tt>-cc1</tt> argument indicates the compiler front-end, and
not the driver, should be run. The compiler front-end has several additional
Clang specific features which are not exposed through the GCC compatible driver
interface.</p>
OpenPOWER on IntegriCloud