diff options
author | Daniel Malea <daniel.malea@intel.com> | 2012-12-17 21:32:49 +0000 |
---|---|---|
committer | Daniel Malea <daniel.malea@intel.com> | 2012-12-17 21:32:49 +0000 |
commit | 66d5714ae6a0fb433d8c67d4e22473353ed327c2 (patch) | |
tree | c8ab2745bcfe3262840c4accf21b344d4adabdf7 | |
parent | 10700aad85d716e79fd913511c0beb8f67c91bc6 (diff) | |
download | bcm5719-llvm-66d5714ae6a0fb433d8c67d4e22473353ed327c2.tar.gz bcm5719-llvm-66d5714ae6a0fb433d8c67d4e22473353ed327c2.zip |
Mention how to do a (Linux) release build on the build instructions page.
Also, a few minor fixes:
- paragraph formatting
- capitalize "Python" where appropriate
llvm-svn: 170372
-rwxr-xr-x | lldb/www/build.html | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/lldb/www/build.html b/lldb/www/build.html index 0bddbb3d7ce..e50092cf536 100755 --- a/lldb/www/build.html +++ b/lldb/www/build.html @@ -118,19 +118,21 @@ <br>> make CXXFLAGS=-std=c++0x</code>
<p>Note that once both LLVM and Clang have been configured and built it is not
necessary to perform a top-level <tt>make</tt> to rebuild changes made only to LLDB.
- You can run <tt>make</tt> from the <tt>build/tools/lldb</tt> subdirectory as well. If you
- wish to build with libc++, you should run configure with the <tt>--enable-libcpp</tt> flag.</p>
+ You can run <tt>make</tt> from the <tt>build/tools/lldb</tt> subdirectory as well.</p>
+ <p> If you wish to build with libc++ instead of libstdc++ (the default), you should run configure with the
+ <tt>--enable-libcpp</tt> flag.</p>
+ <p> If you wish to build a release version of LLDB, run configure with the <tt>--enable-optimized</tt> flag.</p>
<h2>Additional Notes</h2>
<p>LLDB has a Python scripting capability and supplies its own Python module,
<tt>lldb</tt>, built alongside the <tt>lldb</tt> binary. Python needs to know where to
- look for this module when LLDB starts up. To tell python the location of LLDB, set
+ look for this module when LLDB starts up. To tell Python the location of LLDB, set
<tt>PYTHONPATH</tt> environment variable.
<p>In bash with a <tt>Debug+Asserts</tt> build (the default if configure is invoked
like in the example on this page) one might run:</p>
<code>> export PYTHONPATH=$llvm/build/Debug+Asserts/lib/python2.7/site-packages</code>
- <p>If you used different configure flags, or have a different version of python,
- you may need to adjust the above to suit your needs. To test that the lldb python module
+ <p>If you used a different build directory, made a release build, or have a different version of
+ Python, you may need to adjust the above to suit your needs. To test that the lldb Python module
is built correctly and is available to Python, run:</p>
<code>> python -c 'import lldb'</code></p>
</div>
|