fix: resolve NDK path discovery on Windows#3
Open
AttalliAyoub wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes an issue on Windows where
locate_ndk.dartcrashes becausePlatform.environment['HOME']is null, and addresses a secondary issue where theGlobpackage fails to match Windows paths containing backslashes.How was this fixed?
Platform.environment['USERPROFILE']as the home directory fallback on Windows.\with/) before passing them to theGlobpackage so that glob pattern matching correctly finds the NDK installation directories.0.1.2and updated the CHANGELOG.Testing
Tested locally on Windows.
NDKLocator.locate()now successfully discovers the NDK installation without crashing or failing to match directories.