search for: llvm_lit_tools_dir

...4)] on win32 - Distinguish "test-suite" and "{llvm|clang} tests". (Installing GnuWin32) - Don't recommend to delete MSYS sh.exe in "Installing CMake". Use MSYS Makefiles instead with msys. - gnuwin32 is not needed on %PATH% if gnuwin32 is dedicated to tests. Use LLVM_LIT_TOOLS_DIR instead then. (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) - cmake and python are needed on %PATH%, as long as they are not invoked explicitly. cmake-generated Makefiles know where they are. eg. "make edit_cache", "make check" - If the target o...

..."test-suite" and "{llvm|clang} tests". (Installing GnuWin32) > > - Don't recommend to delete MSYS sh.exe in "Installing CMake". Use > MSYS Makefiles instead with msys. > > - gnuwin32 is not needed on %PATH% if gnuwin32 is dedicated to tests. > Use LLVM_LIT_TOOLS_DIR instead then. > (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) > > - cmake and python are needed on %PATH%, as long as they are not > invoked explicitly. > cmake-generated Makefiles know where they are. > eg. "make edit_cache", "make chec...

...sr/bin/env missing? - MKS utils (eg. grep) might not accept our-expected quotes. Yeah, usually I could tweak proposed patches, but I cannot obtain MKS. (and I won't!). At least, you should consider not to break cmake - {mingw|msvc} - gnuwin32. You may try tests w/o MKS, by CMake's "LLVM_LIT_TOOLS_DIR" with X:/gnuwin32/bin. (You may try also msbuild.exe! ) FYI, as you oughta know, Lit detects bash.exe in $PATH on Win32 hosts. Lit assumes bash.exe might be with a few GNU utils (grep.exe &c.) You would be welcome if you would maintain MKS on, or we shall say "We don't support M...

..."test-suite" and "{llvm|clang} tests". (Installing GnuWin32) > > - Don't recommend to delete MSYS sh.exe in "Installing CMake". Use > MSYS Makefiles instead with msys. > > - gnuwin32 is not needed on %PATH% if gnuwin32 is dedicated to tests. > Use LLVM_LIT_TOOLS_DIR instead then. > (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) > > - cmake and python are needed on %PATH%, as long as they are not > invoked explicitly. > cmake-generated Makefiles know where they are. > eg. "make edit_cache", "make chec...

..."test-suite" and "{llvm|clang} tests". (Installing GnuWin32) > > - Don't recommend to delete MSYS sh.exe in "Installing CMake". Use > MSYS Makefiles instead with msys. > > - gnuwin32 is not needed on %PATH% if gnuwin32 is dedicated to tests. > Use LLVM_LIT_TOOLS_DIR instead then. > (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) > > - cmake and python are needed on %PATH%, as long as they are not > invoked explicitly. > cmake-generated Makefiles know where they are. > eg. "make edit_cache", "make chec...

...nd "{llvm|clang} tests". (Installing GnuWin32) >> >> - Don't recommend to delete MSYS sh.exe in "Installing CMake". Use >> MSYS Makefiles instead with msys. >> >> - gnuwin32 is not needed on %PATH% if gnuwin32 is dedicated to tests. >> Use LLVM_LIT_TOOLS_DIR instead then. >> (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) >> >> - cmake and python are needed on %PATH%, as long as they are not >> invoked explicitly. >> cmake-generated Makefiles know where they are. >> eg. "make edit_cach...

I have filed a number of problem reports about getting the LLVM test infrastructure working for an environment with: Windows + MSVC9 + Cmake + NMake makefiles + MKS. (MKS provides unix-like tools for Windows, but based on very old versions, so they have quirky or minimal compatibility with GNU tools.) http://llvm.org/bugs/show_bug.cgi?id=9689 - Fix Cmake generation of compile_cxx for MSVC -

...nd "{llvm|clang} tests". (Installing GnuWin32) >> >> - Don't recommend to delete MSYS sh.exe in "Installing CMake". Use >> MSYS Makefiles instead with msys. >> >> - gnuwin32 is not needed on %PATH% if gnuwin32 is dedicated to tests. >> Use LLVM_LIT_TOOLS_DIR instead then. >> (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) >> >> - cmake and python are needed on %PATH%, as long as they are not >> invoked explicitly. >> cmake-generated Makefiles know where they are. >> eg. "make edit_cach...

...ms.  I do have many Windows ports of Unix tools in my standard path, > though, and perhaps that is the reason that the build succeds without > GnuWin32. Gnuwin32 is required, for now, when you run tests (check, check-all, clang-test). Then, you would not need to update your %PATH% to specify LLVM_LIT_TOOLS_DIR to CMake. Let me know if you know other (llvm|clang)-tests-compatible tools other than gnuwin32 (and msys). FYI, some clang/llvm tests are marked as "REQUIRES: shell". They rely on sh behavior and they are skipped if bash.exe is not found in your %PATH%.

For those interested in the actual file, it is now attached. ---------- Forwarded message ---------- From: Mikael Lyngvig <mikael at lyngvig.org> Date: 2012/6/16 Subject: RFC: "Building with MinGW on Windows" (DOC, NEW) To: LLVMdev Mailing List <llvmdev at cs.uiuc.edu> Here's the first part of my Windows set up documentation. This one only covers the process of

Here's the first part of my Windows set up documentation. This one only covers the process of setting up a normal box for building LLVM and Clang. A later document, which will follow in a few days, will cover how to set up a buildbot slave. As usual: I'm not a psychic, so if you have opinions regarding or suggestions on this document, please feel free to share them with me (on this

..."test-suite" and "{llvm|clang} tests". (Installing GnuWin32) > > - Don't recommend to delete MSYS sh.exe in "Installing CMake". Use > MSYS Makefiles instead with msys. > > - gnuwin32 is not needed on %PATH% if gnuwin32 is dedicated to tests. > Use LLVM_LIT_TOOLS_DIR instead then. > (gnuwin32 is not needed when person is working on MSYS bash shell, FYI) > > - cmake and python are needed on %PATH%, as long as they are not > invoked explicitly. > cmake-generated Makefiles know where they are. > eg. "make edit_cache", "make chec...

Hi again, The Visual Studio getting started guide ( http://llvm.org/docs/GettingStartedVS.html) mentions the "llvm-lit" tool, but fails to mention these things: 1. Either you need to run it from bash or a similar Unix shell, as Windows does not recognize the extensionless Python script that it is. 2. Alternatively, you can invoke it using Python like this: python bin/llvm-lit