From 357f7ce199fdeb20634595dbfba5484d1f908ed2 Mon Sep 17 00:00:00 2001
From: Chris Lattner
Date: Thu, 20 Aug 2009 06:17:11 +0000
Subject: Improve the Getting Started and Hacking web pages, patch by John
Thompson!
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@79518 91177308-0d34-0410-b5e6-96231b3b80d8
---
www/get_started.html | 41 +++++++++++++++++++++--------------------
www/hacking.html | 7 +++++++
2 files changed, 28 insertions(+), 20 deletions(-)
(limited to 'www')
diff --git a/www/get_started.html b/www/get_started.html
index 690a91120d..a2706231b6 100644
--- a/www/get_started.html
+++ b/www/get_started.html
@@ -59,26 +59,28 @@ follows:
http://www.python.org/download
- Checkout
- and build LLVM from SVN head:
-
+ Checkout LLVM:
+ - Change directory to where you want the llvm directory placed.
- svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
- - cd llvm
- - ./configure; make
Checkout Clang:
- - From within the llvm directory (where you
- built llvm):
- - cd tools
-
- svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
-
+ - cd llvm/tools
+
- svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
+
+ Build LLVM and Clang:
+
+ - cd .. (back to llvm)
+ - ./configure
+ - make
+ - This builds both LLVM and Clang for debug mode.
+ - Note: For subsequent Clang development, you can just do make at the
+ clang directory level.
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:
-
- 'touch empty.cpp; gcc -v empty.cpp -fsyntax-only' to get the
path.
@@ -86,13 +88,6 @@ follows:
hard-coded paths" in clang/lib/Frontend/InitHeaderSearch.cpp and
change the lines below to include that path.
-
- Build Clang:
-
- - cd clang (assuming that you are in llvm/tools)
- - make (this will give you a debug build)
-
-
Try it out (assuming you add llvm/Debug/bin to your path):
- clang-cc --help
@@ -107,7 +102,6 @@ follows:
- clang-cc file.c -emit-llvm -o - | llvm-as | opt -std-compile-opts | llc
> file.s (output native machine code)
-
Note: Here clang-cc is the "low-level" frontend
executable that is similar in purpose to cc1. Clang also has a high-level compiler driver that acts as a drop-in
@@ -149,11 +143,18 @@ Visual Studio:
http://www.cmake.org/cmake/resources/software.html
Visual Studio 2005
(VS 2008 may work also - cmake outputs VS2005 project files)
- Python. This is need only if you will be running the tests
+ Python. This is needed only if you will be running the tests
(which is essential, if you will be developing for clang).
Get it from:
http://www.python.org/download
+ GnuWin32 tools
+ These are also necessary for running the tests.
+ (Note that the grep from MSYS or Cygwin doesn't work with the tests
+ because of embedded double-quotes in the search strings. The GNU
+ grep does work in this case.)
+ Get them from
+ http://getgnuwin32.sourceforge.net.
Checkout LLVM:
diff --git a/www/hacking.html b/www/hacking.html
index 4555322279..a1833a2326 100644
--- a/www/hacking.html
+++ b/www/hacking.html
@@ -136,6 +136,13 @@
Python, which must be installed. Find Python at:
http://www.python.org/download.
Download the latest stable version (2.6.2 at the time of this writing).
+
+ The GnuWin32 tools are also necessary for running the tests.
+ (Note that the grep from MSYS or Cygwin doesn't work with the tests
+ because of embedded double-quotes in the search strings. The GNU
+ grep does work in this case.)
+ Get them from
+ http://getgnuwin32.sourceforge.net.
Creating Patch Files
--
cgit v1.2.1