-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix(cli): run project path validation checks #2985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This update introduces a function to warn users about long project paths on Windows, which can lead to failures in Android CMake/Ninja builds due to MAX_PATH limitations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it! Couple of thoughts/suggestions I can think of now that we went down this rabbit hole:
- Move
checkWindowsPathLengthintosrc/tools/validation.tssince it seems to fit there - Consider renaming
checkWindowsPathLengthtovalidateProjectPathand we could have platform specific checks in there?- For example, Windows needs the length check
- Honestly, macOS needs a check for spaces in the path because Xcode will die on build if spaces are in the directory I'm pretty sure
frankcalise
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Frank Calise <fcalise@gmail.com>
## [11.1.1](v11.1.0...v11.1.1) (2025-08-18) ### Bug Fixes * **cli:** run project path validation checks ([#2985](#2985)) ([c54aeec](c54aeec))
|
🎉 This PR is included in version 11.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
This update introduces a function to warn users about long project paths on Windows, which can lead to failures in Android CMake/Ninja builds due to MAX_PATH limitations.
Checklist