Migrate build completely to kotlin-toolchain#58
Open
thunderbiscuit 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.
Ok this might be a bit premature because kotlin-toolchain is still early (for example there are a few things that prevent it from working on Padawan), but for simple projects it works wonderfully, and I was able to migrate the Tatooine Faucet to it easily, and when it works it's just so much easier than Gradle... it reminds me of cargo and the Rust toolchain in general.
One of the weaknesses of this build tool at the moment is IDE integration. It doesn't really play well with my Android studio and only somewhat ok with IntelliJ, but honestly I mostly use the command line to build, test, or run the app, so the build tool integration has not really been a problem for me.
Let me know what you think @ItoroD, I'm totally ok with waiting a bit and revisiting in 6 months if you prefer, but since this project has a small user-base and is on the "simpler" side of Android, I figured it was a good testing ground, and we can then report back our experience and findings for more production libraries down the line.