Keep scope when calling haxe cli from haxelib run #30
Conversation
This file contains 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
|
Maybe there could be a flag in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Basically the issue is with some
haxelib runcommand that call other haxe command (for example:lime rebuild mac), since the cwd would be inside the repo directory the scope then become the global one if no.haxercfile is present in the repo, so you get errors like "no haxelib named lime installed" fromhaxelib path.This keeps the scope intact from the first
haxelib runusing an environment variable.Perhaps not the best way of handling this particular issue, so feel free to close it but it did fix all of my issues from calling OpenFL's CLI using Lix (only way to fix it otherwise is to install it globally which kind of defeats the purpose).