From b9a47d1e3f4e1134231ee1d44e2bbae5adaf2ef9 Mon Sep 17 00:00:00 2001
From: Jeff Cohen
To emphasize, there is no C/C++ front end currently available. llvm-gcc - is based on GCC, which cannot be bootstrapped using VC++. Eventually there - should be a llvm-gcc based on Cygwin or Mingw that is usable. There is also - the option of generating bytecode files on Unix and copying them over to - Windows. But be aware the odds of linking C++ code compiled with llvm-gcc - with code compiled with VC++ is essentially zero.
+To emphasize, there is no C/C++ front end currently available. + llvm-gcc is based on GCC, which cannot be bootstrapped using VC++. + Eventually there should be a llvm-gcc based on Cygwin or MinGW that + is usable. There is also the option of generating bytecode files on Unix and + copying them over to Windows. But be aware the odds of linking C++ code + compiled with llvm-gcc with code compiled with VC++ is essentially + zero.
The LLVM test suite cannot be run on the Visual Studio port at this time.
@@ -95,7 +94,7 @@It is strongly encouraged that you get the latest version from CVS. Much +progress has been made since the 1.4 release.
+ @@ -222,84 +224,6 @@ All these paths are absolute: - --If you have the LLVM distribution, you will need to unpack it before you -can begin to compile it. LLVM is distributed as a set of two files: the LLVM -suite and the LLVM GCC front end compiled for your platform. There is an -additional test suite that is optional. Each file is a TAR archive that is -compressed with the gzip program. The WinZip program can also unpack this -archive. Only the LLVM suite is usable with Visual Studio. -
- -The files are as follows: -
If you have access to our CVS repository, you can get a fresh copy of -the entire source code. Note that significant progress has been made on the -Visual Studio port since 1.4 was released. All you need to do is check it out -from CVS 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.
- -If you want to get a specific release (as opposed to the most recent -revision), you can specify a label. The following releases have the following -label:
- -If the main CVS server is overloaded or inaccessible, you can try one of -these user-hosted mirrors:
- - -