From 9c29bfbab14dcd89c022e731eb596748c3dd5c7f Mon Sep 17 00:00:00 2001
From: John Criswell
-
If you have access to our CVS repository, you can get a fresh copy of -the entire source code. All you need to do is check it out from CVS as +
If you have access to our Subversion repository, you can get a fresh copy of +the entire source code. All you need to do is check it out from Subvresion as follows:
This will create an 'llvm' directory in the current directory and fully populate it with the LLVM source code, Makefiles, test directories, and local copies of documentation files.
@@ -721,14 +720,14 @@ labels:If you would like to get the LLVM test suite (a separate package as of 1.4), -you get it from the CVS repository:
+you get it from the Subversion repository:cd llvm/projects - cvs -z3 -d :pserver:anon@llvm.org:/var/cvs/llvm co llvm-test + svn so http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
By placing it in the llvm/projects, it will be automatically configured by the LLVM configure script as well as automatically updated when -you run cvs update.
+you run svn update.If you would like to get the GCC front end source code, you can also get it and build it yourself. Please follow these @@ -783,7 +782,8 @@ much easier now than it was in the past.
Once checked out from the CVS repository, the LLVM suite source code must be +
Once checked out from the Subversion repository, the LLVM suite source + code must be configured via the configure script. This script sets variables in the various *.in files, most notably llvm/Makefile.config and llvm/include/Config/config.h. It also populates OBJ_ROOT with @@ -1172,13 +1172,6 @@ The following is a brief introduction to code layout:
Every directory checked out of CVS will contain a CVS directory; for -the most part these can just be ignored.
-This is not a directory in the normal llvm module; it is a separate CVS - module that must be checked out (usually to projects/llvm-test). This +
This is not a directory in the normal llvm module; it is a separate + Subversion + module that must be checked out (usually to projects/test-suite). + This module contains a comprehensive correctness, performance, and benchmarking test - suite for LLVM. It is a separate CVS module because not every LLVM user is + suite for LLVM. It is a separate Subversion module because not every LLVM + user is interested in downloading or building such a comprehensive test suite. For further details on this test suite, please see the Testing Guide document.
@@ -1395,7 +1391,7 @@ information is in the Command Guide. usual machine code output. It works just like any other GCC compiler, taking the typical -c, -S, -E, -o options that are typically used. Additionally, the the source code for llvm-gcc is available as a - separate CVS module. + separate Subversion module.