Anyone succeeding at meta-programming in MPP projects with kapt or other ways to codegen for all platforms? Kapt is JVM only and we rely on Arrow on annotation processing to generate code at the moment. Not being able to use kapt in MPP projects is currently not allowing to publish for JS and native. Any advice or recommendations are much appreciated. Thanks!

I don't know much about Kotlin compiler plugins, but I'm guessing you've already looked into them?

yes, undocumented and unclear how to get the most basic info out of types. Even for the current implementation we are having to use a combination of TypeElement from the Java apis, Kotlin Poet and @Eugenio meta data lib to be able to actually get the Kotlin info out of the types. Meta programming in Kotlin it's in a very sad state unless I'm missing some obvious lib. I don't want to go down the path of parsing sources and coming up with my own AST and pseudo type checker.

What about generating common code as a separate step using Kapt?

The issue is that kapt actually has made the decission to not run on MPP projects it requires the projects to be JVM only

I think here's a great example of multiplatform Kotlin codegen that doesn't rely on annotations to generate other code: https://github.com/square/sqldelight

thanks @louiscad

It looks so. The authors present on this Slack (

@jw

and

@alec

) may help you if you struggle understand the organization of SQLDelight codegen code. You can also reach them and possibly other maintainers in #squarelibraries and in GitHub issues if needed.

thanks Louis, much appreciated 👍

Well... if you're insane, you could always do what I did. Take a look at #mirror. I wrote a plugin that reads

.kotlin_metadata

and

.kt

files to generate code. I'm not sure I recommend it, but it's possible and I've done it. It relies on no PSI stuff.

The issue is that kapt actually has made the decission to not run on MPP projects it requires the projects to be JVM only

This is not a “decision” , but Kapt just based on Java-only API. What I suggested is to use Kapt and JVM to generate common code, this is similar to what Louis also suggested

@gildor that is what we want to do but all of our attempts to have kapt run over an MPP layout have failed

what do you mean “MPP layout”?

Modules that are common on MPP projects. Kapt requires the module to be JVM only or we have not figured it out otherwise.

Yes, what I propose, 1 Add common code source set to special JVM module with Kapt 2. generate code using Kapt using common-code 3. add generated code as source set to common module

thanks @gildor, the issue is that arrow usage of kapt is not limited to the library build but we also export annotations that we ask users to place in places if they want to take advantage of codegen. Is there a way in kapt or in gradle to bundle this behavior so you can just run

kapt

on an common module?

No, you cannot run kapt on common module without writing some additional build step that would generate code first

ok, I'll look into how this is done in Gradle. Thanks

In Gradle?

yes, the idea is to create a small plugin as part of arrow meta that when activated in an common module it would take the sources, create a jvm temp project layout, run kapt and copied the codegen over back to the common place.

Yeah, this looks reasonable

@raulraja have you been able to build your mentioned plugin?

@Jonas Bark almost there, currently.buikdimg IDEA support and generating synth resolution but met can already do compiler tree transformations in the analysis phase and ir manipulation pretty easily

okay, thanks for letting me know! I'm gonna look into this as I'm also looking for something like this

yes, that is great

@raulraja nice progress on arrow meta! does it work on sources only, or also klib?

Everything related to sources works in the analysys and sythtetic resolution phases as a Tree transformation that modified the document. That is for the CLI compiler, the IDEA implementation runs it inside the SynthResolver phase on demand as the user types providing synth descriptors automatically. Beside these source level transformations user can intercept IR or traditional codegen but that has no impact in IDEA since for that we would have to scan the .class files and generate synth descriptors for them even if they are for the same module