A modern programming language that makes developers happier.

kotlinlang

Anybody using a buildSrc precompiled gradle kts file to manage building / targets for a KMP library?

I’ve got a repo I’m trying to update that has 5 libraries and 1 example KMP app. Currently the build.gradle.kts sets the KMP build targets for the library, but I want to move this to buildSrc and apply it directly to the libraries. 

Instead of build source I would recommend looking at composite builds to create plugins that you apply instead which is what we do. Underlying reasoning is build cache is simplified and plugins dont have to stay lock step with your project that way and could be reused in other projects more easily in the future which we've also done.

Yeah it seems like buildSrc / pre compiled scripts have known limitations that aren’t communicated well. I’ll take a shot at a composite build plugin, thanks Ian!

Funnily enough the repo was referenced here awhile ago, I’m trying to get this updated: <https://kotlinlang.slack.com/archives/C0346LWVBJ4/p1731661221557559?thread_ts=1731622252.424579&amp;channel=C0346LWVBJ4&amp;message_ts=1731661221.557559|https://kotlinlang.slack.com/archives/C0346LWVBJ4/p1731661221557559?thread_ts=1731622252.424579&amp;channel=C0346LWVBJ4&amp;message_ts=1731661221.557559>

I believe this is the documentation/sample code I used when I set it up for our project, hope it helps :+1: <https://docs.gradle.org/current/samples/sample_composite_builds_plugin_development.html>

It's not the cleanest, but its working a bit. I ended up using precompiled scripts in the buildSrc folder, and its pretty cool!

<https://gist.github.com/schott12521/f8195d2716b93fbcb480c78ca9cec362>

I took a lot of reference from <https://github.com/eduayuso/kmp-gradle-optimized/tree/main>

<#C061JJM6YUQ|> uses <https://github.com/nesk/akkurate/tree/60de92a3370b086f7895e4eec7912ae4938711a7/buildSrc/src/main/kotlin|a buildSrc> to provide some convention plugins <https://github.com/nesk/akkurate/blob/60de92a3370b086f7895e4eec7912ae4938711a7/library/build.gradle.kts#L6|to the various projects> of the repository

But the buildSrc also contains <https://github.com/nesk/akkurate/blob/60de92a3370b086f7895e4eec7912ae4938711a7/buildSrc/src/main/kotlin/dev/nesk/akkurate/gradle/Targets.kt|custom code> which can be called <https://github.com/nesk/akkurate/blob/60de92a3370b086f7895e4eec7912ae4938711a7/integrations/arrow/build.gradle.kts#L10-L15|from the gradle.kts files>. This allows to bring more flexibility.