Kotlin source generation about magnet HOT 4 CLOSED

Fine for me, I'll have a closer look at build times w/ Magnet enabled and report back here if I stumble upon any issues.

from magnet.

Correct me if I am mistaken, but as of now Android Gradle Plugin generates BuildConfig.java file anyway. Thus javac gets executed independent on whether magnet generates additional java sources or not.

Nevertheless I agree with you in general. I was thinking about this kind of optimization before and I am rather inclined to implementing a Kotlin compiler plugin. They speak about Kotlin IR (Intermediate representation), which can be used to represent source code independent of any particular source or target languages. It can be used to enhance/generate byte code directly bypassing java or kotlin sources. The idea was to "inject" static factories right in the implementation classes or so. But that's future if there is time for it...

from magnet.

Well, for my Kotlin-only modules I disabled BuildConfig.java generation altogether and got a nice speedup (partially from the generation itself, partially from the javac invocation), so it would definitely help I guess, but I have no exact numbers at hand.

If interested, this is how it is done:

 project.plugins.withId("com.android.library") {
        // TODO replace with https://issuetracker.google.com/issues/72050365 once released.
        project.android.libraryVariants.all {
            it.generateBuildConfig.enabled = false
        }
    }

Thanks for considering!

from magnet.

Yeah, I had this optimization too, but it stopped working with AGP 3.3.0. If you don't mind, I'm going to close this issue, because there is no plans for supporting kotlin source generation in the near future.

from magnet.