[all-commits] [llvm/llvm-project] f875a7: [llvm-lit] Add Windows .cmd wrapper to make llvm-l...

[Omair Javaid via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: f875a73af958bd1ed6c39849c7ae90371cd25ccb
      https://github.com/llvm/llvm-project/commit/f875a73af958bd1ed6c39849c7ae90371cd25ccb
  Author: Omair Javaid <omair.javaid at linaro.org>
  Date:   2025-08-29 (Fri, 29 Aug 2025)

  Changed paths:
    M clang/test/utils/update_cc_test_checks/lit.local.cfg
    M llvm/utils/llvm-lit/CMakeLists.txt
    A llvm/utils/llvm-lit/llvm-lit.cmd.in

  Log Message:
  -----------
  [llvm-lit] Add Windows .cmd wrapper to make llvm-lit directly runnable (#155226)

On Linux/Mac, `llvm-lit` is configured with a shebang and made
executable so tools like LNT and the test-suite can invoke it directly.
On Windows the build only produces `llvm-lit.py` which cannot be used as
a standalone executable. This caused problems when running the LLVM
test-suite via LNT or buildbots.

This change introduces a new template file `llvm-lit.cmd.in` and updates
`llvm/utils/llvm-lit/CMakeLists.txt` so that a corresponding
`llvm-lit.cmd` is generated in the `build/bin` directory (for both
single-config and multi-config generators). The wrapper simply invokes
the configured Python interpreter on the adjacent `llvm-lit.py` and
propagates the exit code.

This ensures that `llvm-lit` can be used as a direct executable on
Windows just like on Linux without requiring external wrappers or
modifications in buildbot scripts or LNT.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications