From: Misha Brukman Date: Thu, 3 Feb 2005 18:28:08 +0000 (+0000) Subject: * Clearly mark LLVM_LIB_SEARCH_PATH as being optional X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=8f0cad17cab62fdfee92af58748da244c38db1ea;p=oota-llvm.git * Clearly mark LLVM_LIB_SEARCH_PATH as being optional * llvmgcc and llvmg++ aliases are no longer needed (binaries have llvm- prefix) git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@20016 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 8bf80d340ff..e5c981206ee 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -552,22 +552,16 @@ All these paths are absolute:

-In order to compile and use LLVM, you will need to set some environment -variables. There are also some shell aliases which you may find useful. -You can set these on the command line, or better yet, set them in your -.cshrc or .profile. +In order to compile and use LLVM, you may need to set some environment +variables.

LLVM_LIB_SEARCH_PATH=/path/to/your/bytecode/libs
-
This environment variable helps LLVM linking tools find the locations - of your bytecode libraries. It is optional and provided only a convenience - since you can specify the paths using the -L options of the tools.
- -
alias llvmgcc='llvm-gcc'
-
alias llvmg++='llvm-g++'
-
These aliases allow you to use the LLVM C and C++ front ends - under alternative names. It is assumed that llvm-gcc and llvm-g++ are - in your path. The LLVM makefiles will use llvm-gcc and llvm-g++ directly.
+
[Optional] This environment variable helps LLVM linking tools find the + locations of your bytecode libraries. It is provided only a + convenience since you can specify the paths using the -L options of the + tools and the C/C++ front-end will use the bytecode files installed in its + lib directory.