[LLVMbugs] [Bug 14051] New: Incorrect instructions for running llvm tests in Visual Studio guide

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=14051

             Bug #: 14051
           Summary: Incorrect instructions for running llvm tests in
                    Visual Studio guide
           Product: Documentation
           Version: trunk
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P
         Component: General docs
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: rb+llvm at ravenbrook.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified


http://www.llvm.org/docs/GettingStartedVS.html says:

  9. Test LLVM:

        The LLVM tests can be run by changing directory to the llvm source
directory and running:

        C:\..\llvm> llvm-lit test

        Note that quite a few of these test will fail.

        A specific test or test directory can be run with:

        C:\..\llvm> llvm-lit test/path/to/test

There are several things wrong with this.

1. If you have followed the instructions up to now, "llvm-lit" will not be
found.  There was no step that added the build directory's "bin" directory to
your path (and there probably shouldn't be).  In fact you must type something
like:

  C:\Python27\python \path\to\build\directory\bin\llvm-lit test

to even run llvm-lit.

2. llvm-lit will then fail anyway because llvm-lit.in contains CMAKE variables
that can only be expanded by Visual Studio, such as @CMAKE_CFG_INTDIR@  See
http://www.cmake.org/cmake/help/cmake2.6docs.html#variable:CMAKE_CFG_INTDIR

3. llvm-lit appears to depend on bash, which is not included in the GnuWin32
step earlier in the instructions.

These problems lead me to believe that step 9 of this guide is very out-of-date
and that the tests aren't intended to be run like this at all.

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.