Allow using different flutter binaries for the sdk and flutter itself #260
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.
On NixOS using a different
flutterbinary is needed or else commands like:FlutterRunwon't work as theflutterbinary that's withdart-sdkis different from the "wrapped"flutterin$PATHthis "wrapped" flutter simply runsflutterwith a lot of required dependencies. I know this similar to #259 which solves the same problem in a different way. But if this implementation isn't to your liking, I've been also been thinking of an alternative solution wheredart_bin,dart_sdk,flutter_sdk, andflutter_binare all possible with the existing system replaced (usingflutter_binto find the others if they aren't supplied, similar to how it is now). If I'm correct those options on their own should be enough to account for every possible scenario and close all further requests for custom paths.