From 0c4b8b6db4ebe1259c7d3e8a27781d71b6356d40 Mon Sep 17 00:00:00 2001 From: Misha Brukman Date: Wed, 9 Feb 2005 22:38:47 +0000 Subject: [PATCH] * Use an HTML list
    instead of custom superscripts in the platform notes * Reorder software requirements list to show relative importance * Use superscripts for footnotes in software list rather than "Note 1" * Use new doc_notes class to separate footnotes from main doc text llvm-svn: 20098 --- llvm/docs/GettingStarted.html | 105 +++++++++++++++++----------------- 1 file changed, 52 insertions(+), 53 deletions(-) diff --git a/llvm/docs/GettingStarted.html b/llvm/docs/GettingStarted.html index 7a5fdf5408d0..e49608a624d5 100644 --- a/llvm/docs/GettingStarted.html +++ b/llvm/docs/GettingStarted.html @@ -274,28 +274,25 @@ software you will need.

    Notes:

    -
    -1 - Code generation supported for Pentium processors and up
    -2 - Code generation supported for 32-bit ABI only
    -3 - No native code generation
    -4 - Build is not complete: one or more tools don't link
    -5 - The GCC-based C/C++ frontend does not build
    -6 - The port is done using the MSYS shell. +
    +
      +
    1. Code generation supported for Pentium processors and +up
      2. +
    2. Code generation supported for 32-bit ABI only
      3. +
    3. No native code generation
      4. +
    4. Build is not complete: one or more tools don't link
      5. +
    5. The GCC-based C/C++ frontend does not build
      6. +
    6. The port is done using the MSYS shell. Download and install bison (excl. M4.exe) and flex in that order. Build binutils-2.15 from source, if necessary. If you need to create a library for an MS DLL, do the following: -
        +
        • pexports /C/WINNT/SYSTEM32/file.dll | sed "s/^_//" > /C/MinGW/lib/file.def
        • Edit file and append @<ordinal> to the missing function name
        • dlltool.exe -k -d /C/MinGW/lib/file.def -l /C/MinGW/lib/libfile.a.
          • +
    @@ -338,7 +335,7 @@ href="CFEBuildInstrs.html">try to compile it on your platform.

    GCC 3.4.2 - C/C++ compiler (Note 3) + C/C++ compiler1 @@ -353,40 +350,28 @@ href="CFEBuildInstrs.html">try to compile it on your platform.

    YACC compiler + + CVS + ≥1.11 + CVS access to LLVM2 + + DejaGnu 1.4.2 - Automated test suite (Note 2) + Automated test suite3 tcl 8.3, 8.4 - Automated test suite (Note 2) + Automated test suite3 expect 5.38.0 - Automated test suite (Note 2) - - - - GNU M4 - 1.4 - Macro processor for configuration (Note 1) - - - - GNU Autoconf - 2.59 - Configuration script builder (Note 1) - - - - GNU Automake - 1.9.2 - aclocal macro generator (Note 1) + Automated test suite3 @@ -396,35 +381,49 @@ href="CFEBuildInstrs.html">try to compile it on your platform.

    - libtool - 1.5.10 - Shared library manager (Note 1) + GNU M4 + 1.4 + Macro processor for configuration4 - CVS - ≥1.11 - CVS access to LLVM (Note 4) + GNU Autoconf + 2.59 + Configuration script builder4 + + + + GNU Automake + 1.9.2 + aclocal macro generator4 + + + + libtool + 1.5.10 + Shared library manager4 -

    Notes:

    +

    Notes:

    +
      -
    1. If you want to make changes to the configure scripts, +
    2. Only the C and C++ languages are needed so there's no + need to build the other languages for LLVM's purposes. See + below for specific version info.
      3. +
    3. You only need CVS if you intend to build from the + latest LLVM sources. If you're working from a release distribution, you + don't need CVS.
      4. +
    4. Only needed if you want to run the automated test + suite in the llvm/test directory.
      5. +
    5. If you want to make changes to the configure scripts, you will need GNU autoconf (2.59), and consequently, GNU M4 (version 1.4 or higher). You will also need automake (1.9.2). We only use aclocal from that package.
      6. -
    6. Only needed if you want to run the automated test - suite in the test directory.
      7. -
    7. Only the C and C++ languages are needed so there's no - need to build the other languages for LLVM's purposes. See - below for specific version info. -
      8. -
    8. You only need CVS if you intend to build from the - latest LLVM sources. If you're working from a release distribution, you - don't need CVS.
    +
    +

    Additionally, your compilation host is expected to have the usual plethora of Unix utilities. Specifically: