Playing with KSP on a multiplatform project compilation is c

Question

Playing with KSP on a multiplatform project compilation is crashing because of multiple classesDirs as I understand it It s crashing in <https cs android com android studio kotlin + master libraries tools kotlin gradle plugin src main kotlin org jetbrains kotlin gradle targets js ir KotlinJsIrLink kt l=54 q=KotlinJsIrLink kt|KotlinJsIrLink l54> where the code use a single on a list that I suppose has the classes dir + the generated dir Is my understanding correct and should I discuss this in multiplatform JS instead

Ting-Yuan Huang · Answer

Can you provide a test case or stacktrace So that we can understand what happened better and whether it should be fixed in KSP or compiler

Grégory Lureau · Answer

Here a simple project that reproduces the error stacktrace available in the README md <https github com glureau ksp kmp issues tree kotlinjsir single crashing>

Grégory Lureau · Answer

Note that I also reproduced another issue with an infinite build time on another branch Build ends with a stackoverflow due to recursive calls for some reasons Not related to the other issue I think you can reproduce the issue on this branch <https github com glureau ksp kmp issues tree stackoverflow>

Grégory Lureau · Answer

I ve asked on the javascript channel for help on the and created an for the crash Let me know if I can help with the KotlinJsIr limitation as I didn t found any workaround so far and it s quite annoying

Ting-Yuan Huang · Answer

Thanks a lot for the test case and filing the issues I ll take a look next week

Alex Vanyo · Answer

If helpful I ve also ran into the Collection has more than one element error when trying to add a `js` target with `ksp` in my multiplatform branch here <https github com livefront sealed enum tree av multiplatform js ksp error>

Grégory Lureau · Answer

Should I create a Kotlin Js IR issue for the `Collection has more than one element ` error

Grégory Lureau · Answer

I think I ve found an ugly workaround don t provide the annotation interface in a dedicated module but duplicate it in every modules where you need to run KSP Each duplicated annotation must have a different name Then I pass the full name manually via gradle KSP options to the processor