[llvm-commits] CVS: llvm/docs/GettingStarted.html
Misha Brukman
brukman at cs.uiuc.edu
Sat Aug 21 16:41:00 PDT 2004
Changes in directory llvm/docs:
GettingStarted.html updated: 1.66 -> 1.67
---
Log message:
Bytecode libraries are installed with `make install-bytecode'
---
Diffs of the changes: (+9 -10)
Index: llvm/docs/GettingStarted.html
diff -u llvm/docs/GettingStarted.html:1.66 llvm/docs/GettingStarted.html:1.67
--- llvm/docs/GettingStarted.html:1.66 Mon Aug 16 09:51:33 2004
+++ llvm/docs/GettingStarted.html Sat Aug 21 18:40:49 2004
@@ -738,18 +738,17 @@
<dt><tt>gmake distclean</tt>
<dd>
- Removes everything that <tt>gmake clean</tt> does, but also removes
- files generated by <tt>configure</tt>. It attempts to return the
- source tree to the original state in which it was shipped.
+ Removes everything that <tt>gmake clean</tt> does, but also removes files
+ generated by <tt>configure</tt>. It attempts to return the source tree to the
+ original state in which it was shipped.
<p>
- <dt><tt>gmake install</tt>
+ <dt><tt>gmake install-bytecode</tt>
<dd>
- Installs LLVM files into the proper location. For the most part,
- this does nothing, but it does install bytecode libraries into the
- GCC front end's bytecode library directory. If you need to update
- your bytecode libraries, this is the target to use once you've built
- them.
+ Assuming you built LLVM into $OBJDIR, when this command is run in
+ $OBJDIR/runtime, it will install bytecode libraries into the GCC front end's
+ bytecode library directory. If you need to update your bytecode libraries,
+ this is the target to use once you've built them.
<p>
</dl>
@@ -1280,7 +1279,7 @@
<a href="mailto:sabre at nondot.org">Chris Lattner</a><br>
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2004/08/16 14:51:33 $
+ Last modified: $Date: 2004/08/21 23:40:49 $
</address>
</body>
More information about the llvm-commits
mailing list