get-lit.ps1: Specify the current directory when starting luvi.exe/lit.exe#268
Merged
squeek502 merged 1 commit intoluvit:masterfrom Mar 9, 2020
Merged
get-lit.ps1: Specify the current directory when starting luvi.exe/lit.exe#268squeek502 merged 1 commit intoluvit:masterfrom
squeek502 merged 1 commit intoluvit:masterfrom
Conversation
….exe If there was an older lit.exe or luvi.exe on your PATH, then running get-lit.ps1 anywhere would use those older existing lit.exe/luvi.exe instead of the newly downloaded ones. This could lead to 'cannot load incompatible bytecode' errors that should no longer be possible after luvit#263.
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.
If there was an older lit.exe or luvi.exe on your PATH, then running get-lit.ps1 anywhere would use those older existing lit.exe/luvi.exe instead of the newly downloaded ones. This could lead to 'cannot load incompatible bytecode' errors that should no longer be possible after #263.