From: John Thompson Date: Fri, 6 Nov 2009 00:06:29 +0000 (+0000) Subject: Update clang web pages with respect to Windows X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=99ff8da8c5173b4037ac03c53244256a757b0ab8;p=clang Update clang web pages with respect to Windows git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@86200 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/www/get_started.html b/www/get_started.html index 86f6cef35c..a1e9b0bc16 100644 --- a/www/get_started.html +++ b/www/get_started.html @@ -168,7 +168,8 @@ Visual Studio:

  • Run cmake to generate the Visual Studio solution and project files:
    • diff --git a/www/hacking.html b/www/hacking.html index a1833a2326..372d9a62ec 100644 --- a/www/hacking.html +++ b/www/hacking.html @@ -127,12 +127,10 @@

    Testing using Visual Studio on Windows

    -

    The cmake build tool is set up to create Visual Studio project files - for running the tests, "clang-test" being the root. - Unfortunately, the test runner scripts presently don't work on Windows. - This will be fixed during the test runner revision in progress.

    +

    The Clang test suite can be run from either Visual Studio or + the command line.

    -

    Note that the current and coming revised test runner is based on +

    Note that the test runner is based on Python, which must be installed. Find Python at: http://www.python.org/download. Download the latest stable version (2.6.2 at the time of this writing).

    @@ -143,6 +141,62 @@ grep does work in this case.) Get them from http://getgnuwin32.sourceforge.net.

    + +

    The cmake build tool is set up to create Visual Studio project files + for running the tests, "clang-test" being the root. Therefore, to + run the test from Visual Studio, right-click the clang-test project + and select "Build".

    + +

    To run all the tests from the command line, execute a command like + the following:

    + + + python (path to llvm)/llvm/utils/lit/lit.py -sv --no-progress-bar + (path to llvm)/llvm/tools/clang/test + + +

    To run a single test:

    + + + python (path to llvm)/llvm/utils/lit/lit.py -sv --no-progress-bar + (path to llvm)/llvm/tools/clang/test/(dir)/(test) + + +

    For example:

    + + + python C:/Tools/llvm/utils/lit/lit.py -sv --no-progress-bar + C:/Tools/llvm/tools/clang/test/Sema/wchar.c + + +

    The -sv option above tells the runner to show the test output if + any tests failed, to help you determine the cause of failure.

    + +

    Note that a few tests currently fail on Windows. We are working to + correct this. Therefore your output might look something like this:

    + +
    lit.py: lit.cfg:152: note: using clang: 'C:/Tools/llvm/bin/Debug\\clang.EXE'
+lit.py: lit.cfg:157: note: using clang-cc: 'C:/Tools/llvm/bin/Debug/clang-cc.exe'
+-- Testing: 1723 tests, 2 threads --
+FAIL: Clang::(test path) (659 of 1723)
+******************** TEST 'Clang::(test path)' FAILED ********************
+Script:
+  (commands run)
+Command Output (stdout):
+  (output here)
+Command Output (stderr):
+  (output here)
+********************
+Testing Time: 83.66s
+********************
+Failing Tests (1):
+    Clang::(test path)
+  Expected Passes    : 1704
+  Expected Failures  : 18
+  Unexpected Failures: 1
+
     + +

    The last statistic, "Unexpected Failures", is the important one.

    Creating Patch Files