bazel-contrib / bazel-contrib/rules_foreign_cc
Windows tool paths require `.exe` when passed to CMake
- Dominant language
- Starlark
- Stars
- 737
- Forks
- 270
- PR merge metrics
- No merged PRs in 30d
Description
CMake does not accept paths to tools which look like `c:/msys64/mingw64/bin/gcc`, reporting "... is not a full path to an existing compiler tool."
It needs to have ".exe" appended to the tool names. Not sure how this hasn't been spotted yet but here we are :smile:. This is probably good practise for passing tools to any underlying build system on Windows.
Contributor guide
Research direction
No source file or test is named. Start by locating the CMake tool-path handling and reproduce the reported Windows case with a compiler path lacking `.exe`; done means CMake accepts the resulting tool paths without the existing-compiler error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100