Skip to content

Conversation

@euclid-skyline
Copy link

The CMake module path was not being handled correctly on Windows because backslashes were not escaped. This change explicitly replaces backslashes with forward slashes for the CMAKE_MODULE_PATH argument when building on Windows.

The CMake module path was not being handled correctly on Windows because
backslashes were not escaped. This change explicitly replaces backslashes
with forward slashes for the `CMAKE_MODULE_PATH` argument when building on
Windows.
@google-cla
Copy link

google-cla bot commented Dec 17, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@euclid-skyline
Copy link
Author

euclid-skyline commented Dec 18, 2025

I found this CMake problem on Windows System independent of PR # 1161 after consulting Gemini of Android Studio. I suggest this PR over the one suggested in PR#1161 to distinguish the issue happened with Windows and no need to do unnecessary action if CMake running on different OS such as Linux/MAC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant