[Lldb-commits] [PATCH] D62041: [Docs] Remove SVN checkout from LLDB build steps

J. Ryan Stinnett via Phabricator via lldb-commits lldb-commits at lists.llvm.org
Thu May 16 15:38:37 PDT 2019

jryans created this revision.
jryans added a reviewer: JDevlieghere.
Herald added a project: LLDB.

This removes several older paragraphs in the LLDB build steps for Unix systems
which suggested checking out various components via SVN. Since there's a
separate page about getting the LLDB source which only mentions Git, it seems
appropriate to remove this older info from the build docs.

  rG LLVM Github Monorepo



Index: lldb/docs/resources/build.rst
--- lldb/docs/resources/build.rst
+++ lldb/docs/resources/build.rst
@@ -239,43 +239,6 @@
 **Building LLDB**
-We first need to checkout the source trees into the appropriate locations. Both
-Clang and LLDB build as subprojects of LLVM. This means we will be checking out
-the source for both Clang and LLDB into the tools subdirectory of LLVM. We will
-be setting up a directory hierarchy looking something like this:
-                  llvm
-                  |
-                  `-- tools
-                      |
-                      +-- clang
-                      |
-                      `-- lldb
-For reference, we will call the root of the LLVM project tree $llvm, and the
-roots of the Clang and LLDB source trees $clang and $lldb respectively.
-Change to the directory where you want to do development work and checkout
-  > svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
-Now switch to LLVM’s tools subdirectory and checkout both Clang and LLDB:
-  > cd $llvm/tools
-  > svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
-  > svn co http://llvm.org/svn/llvm-project/lldb/trunk lldb
-In general, building the LLDB trunk revision requires trunk revisions of both
-LLVM and Clang.
 It is highly recommended that you build the system out of tree. Create a second
 build directory and configure the LLVM project tree to your specifications as
 outlined in LLVM’s Getting Started Guide. A typical build procedure might be:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: D62041.199920.patch
Type: text/x-patch
Size: 1602 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20190516/603ed681/attachment.bin>

More information about the lldb-commits mailing list