diff --git a/docs/GettingStartedVS.html b/docs/GettingStartedVS.html index 05803780a84..2e21b33b72a 100644 --- a/docs/GettingStartedVS.html +++ b/docs/GettingStartedVS.html @@ -86,7 +86,7 @@
  1. Read the documentation.
    2. -
  2. Read the documentation.
    3. +
  3. Seriously, read the documentation.
  4. Remember that you were warned twice about reading the documentation.
  5. Get the Source Code @@ -203,17 +203,13 @@ each of these names with the appropriate pathname on your local system. All these paths are absolute:

    -
    SRC_ROOT -
    - This is the top level directory of the LLVM source tree. -

    +

    SRC_ROOT
    +

    This is the top level directory of the LLVM source tree.

    -
    OBJ_ROOT -
    - This is the top level directory of the LLVM object tree (i.e. the - tree where object files and compiled programs will be placed. It - is fixed at SRC_ROOT/win32). -

    +

    OBJ_ROOT
    +

    This is the top level directory of the LLVM object tree (i.e. the + tree where object files and compiled programs will be placed. It is + fixed at SRC_ROOT/win32).

    @@ -227,12 +223,12 @@ All these paths are absolute:

    The object files are placed under OBJ_ROOT/Debug for debug builds and OBJ_ROOT/Release for release (optimized) builds. These include - both executables and libararies that your application can link against. + both executables and libararies that your application can link against.

    The files that configure would create when building on Unix are created by the Configure project and placed in OBJ_ROOT/llvm. You application must have OBJ_ROOT in its include - search path just before SRC_ROOT/include. + search path just before SRC_ROOT/include.

    @@ -245,57 +241,83 @@ All these paths are absolute:

      -
    1. First, create a simple C file, name it 'hello.c': - 
      -   #include <stdio.h>
-   int main() {
-     printf("hello world\n");
-     return 0;
-   }
-
      2. +

    2. First, create a simple C file, name it 'hello.c':

      + +
      +
      +#include <stdio.h>
+int main() {
+  printf("hello world\n");
+  return 0;
+}
+

    3. Next, compile the C file into a LLVM bitcode file:

      -

      % llvm-gcc -c hello.c -emit-llvm -o hello.bc

      -

      This will create the result file hello.bc which is the LLVM - bitcode that corresponds the the compiled program and the library - facilities that it required. You can execute this file directly using - lli tool, compile it to native assembly with the llc, - optimize or analyze it further with the opt tool, etc.

      +
      +
      +% llvm-gcc -c hello.c -emit-llvm -o hello.bc
+
      +
      + +

      This will create the result file hello.bc which is the LLVM + bitcode that corresponds the the compiled program and the library + facilities that it required. You can execute this file directly using + lli tool, compile it to native assembly with the llc, + optimize or analyze it further with the opt tool, etc.

      Note: while you cannot do this step on Windows, you can do it on a - Unix system and transfer hello.bc to Windows. Important: - transfer as a binary file!

      4. + Unix system and transfer hello.bc to Windows. Important: + transfer as a binary file!

    4. Run the program using the just-in-time compiler:

      -

      % lli hello.bc

      5. +
      +
      +% lli hello.bc
+
      +

      Note: this will only work for trivial C programs. Non-trivial programs - (and any C++ program) will have dependencies on the GCC runtime that - won't be satisfied by the Microsoft runtime libraries.

      + (and any C++ program) will have dependencies on the GCC runtime that + won't be satisfied by the Microsoft runtime libraries.

    5. Use the llvm-dis utility to take a look at the LLVM assembly code:

      -

      % llvm-dis < hello.bc | more

      6. +
      +
      +% llvm-dis < hello.bc | more
+
      +

    6. Compile the program to C using the LLC code generator:

      -

      % llc -march=c hello.bc

      7. +
      +
      +% llc -march=c hello.bc
+
      +

    7. Compile to binary using Microsoft C:

      -

      % cl hello.cbe.c

      8. +
      +
      +% cl hello.cbe.c
+
      +

      Note: this will only work for trivial C programs. Non-trivial programs (and any C++ program) will have dependencies on the GCC runtime that - won't be satisfied by the Microsoft runtime libraries.

      + won't be satisfied by the Microsoft runtime libraries.

    8. Execute the native code program:

      -

      % hello.cbe.exe

      9. - +
      +
      +% hello.cbe.exe
+
      +
    @@ -332,7 +354,7 @@ out:

  6. LLVM homepage
  7. LLVM doxygen tree
  8. Starting a Project - that Uses LLVM
    9. + that Uses LLVM