blob: e8a19fcfe85ae77e6b3c9958218ec725f6d64e62 [file] [log] [blame]
Joerg Sonnenberger340a1752013-09-25 10:37:32 +00001<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2<html xmlns="http://www.w3.org/1999/xhtml">
3<head>
4<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
5<link href="style.css" rel="stylesheet" type="text/css" />
6<title>Accessing LLDB Sources</title>
7</head>
8
9<body>
10 <div class="www_title">
11 The <strong>LLDB</strong> Debugger
12 </div>
13
14<div id="container">
15 <div id="content">
16
17 <!--#include virtual="sidebar.incl"-->
18
19 <div id="middle">
20 <div class="post">
Zachary Turnerc99b5ce2015-03-10 23:22:25 +000021 <h1 class ="postheader">Checking out LLDB sources</h1>
22 <div class="postcontent">
23 <p>Refer to the <a href="http://llvm.org/docs/GettingStarted.html#getting-started-with-llvm">LLVM Getting Started Guide</a>
24 for general instructions on how to check out source. Note that LLDB depends on having a working checkout of LLVM
25 and Clang, so the first step is to download LLVM and Clang sources as described at the above URL. Then you can
26 additionally download the LLDB sources from the following repository URLs.</p>
27 <p><b>SVN Repository</b>: http://llvm.org/svn/llvm-project/lldb/trunk </p>
28 <p><b>Git Clone</b>: http://llvm.org/git/lldb.git </p>
29 <p>
30 For non-Mac platforms, and for MacOSX building with CMake (not Xcode), you should check out your sources to adhere to
31 the following directory structure:
Dimitry Andric9a3a6ab2016-01-11 18:07:47 +000032 <pre><tt>
33 llvm
34 |
35 `-- tools
36 |
37 +-- clang
38 |
39 `-- lldb
40 </tt></pre>
Zachary Turnerc99b5ce2015-03-10 23:22:25 +000041 </p>
Dimitry Andric9a3a6ab2016-01-11 18:07:47 +000042 <p>
43 For MacOSX building from Xcode, simply checkout LLDB and then build from Xcode. The Xcode project will
44 automatically detect that it is a fresh checkout, and checkout LLVM and clang automatically. Unlike other
45 platforms / build systems, it will use the following directory structure.
46 <pre><tt>
47 lldb
48 |
49 `-- llvm
50 |
51 +-- tools
52 |
53 `-- clang
54 </tt>
55 </pre>
56 So updating your checkout will consist of updating lldb, llvm, and clang in these locations.
57 </p>
58 <p>
59 Refer to the <a href="build.html">Build Instructions</a> for more detailed instructions on how to build for a particular
60 platform / build system combination.
Zachary Turnerc99b5ce2015-03-10 23:22:25 +000061 </p>
62 </div>
Joerg Sonnenberger340a1752013-09-25 10:37:32 +000063 </div>
64 <div class="post">
65 <h1 class ="postheader">Contributing to LLDB</h1>
66 <div class="postcontent">
Dimitry Andric9a3a6ab2016-01-11 18:07:47 +000067 <p>
68 Please refer to the <a href="http://llvm.org/docs/DeveloperPolicy.html">LLVM Developer Policy</a>
69 for information about authoring and uploading a patch. LLDB differs from the LLVM Developer Policy in
70 the following respects.
71 <ul>
Dimitry Andric9a3a6ab2016-01-11 18:07:47 +000072 <li>
73 Test infrastructure. It is still important to submit tests with your patches, but LLDB uses a different
74 system for tests. Refer to the lldb/test folder on disk for examples of how to write tests.
75 </li>
76 </ul>
77 For anything not explicitly listed here, assume that LLDB follows the LLVM policy.
Zachary Turnerc99b5ce2015-03-10 23:22:25 +000078 </p>
79 </div>
Joerg Sonnenberger340a1752013-09-25 10:37:32 +000080 <div class="postfooter"></div>
81 </div>
82 </div>
83 </div>
84</div>
85</body>
86</html>