Is the process of publishing a MPP library that supports both macOS and Windows documented somewhere? I know its something kotlinx.coroutines does, but the gradle setup there is quite complicated to me, plus I'm less and less familiar with Groovy based gradle as I use almost only Gradle Kotlin DSL since last year. I'd like to ensure my multiplatform publication can resolve using gradle metadata in the consumer projects dependeing on the targets, but I can't run the usual publishing task since I won't be able to compile for Windows on my Mac. A clear guidance or an example I can test with a dummy bintray repo, would be helpful.

Sadly this isn't documented. It's like a secret that's passed around.

Yes, but how does the multiplatform publication gets all the targets? The last host to publish would miss the previous ones?

Like I've done so here https://github.com/Dominaezzz/kgl/blob/d48fb6a1af6611035a137279cd358a6ed19ba90f/build.gradle.kts#L39

The kotlinMultiplatform publication has gradle metadat for all the targets. If I disable a target to build from one host, it will be missing in it? Or is there a way to circumvent this or not have the problem in the first place?

You don't disable the entire target, just it's publication and compilation.

Alright, so the snippet you linked disables those gradle tasks, right?

Yup but metadata is still configured as one would expect.

And you can choose to disable it too if you want to run it only from your last building host, right?

Yes. As long as the target is declared, the result will be the same.

Thank you very mich for the help! I'll setup a CI soon™ and try it!

Sweet. Which CI are you using btw?

Also curious about the ci choice. I think we’re moving everything to azure. I know @basher has that set up for native ios/mac, windows, and linux, so might be a good reference https://github.com/benasher44/uuid/blob/master/azure-pipelines.yml

Yup azure has worked well so far. I split up my publish tasks by platform w/ custom tasks. https://github.com/benasher44/uuid/blob/master/publish.gradle#L158

About that. Why'd you split up your publish tasks?

To avoid rerunning publish tasks on multiple platforms. Metadata and jvm for example can run on multiple

For CI, I am planning to use Azure, per Ben and Jake recommendations: https://kotlinlang.slack.com/archives/C3PQML5NU/p1561941488046500?thread_ts=1561933774.044100&cid=C3PQML5NU Removing duplicates manually is a no go for me as I have dozens of modules. When I set up publish to mavenCentral, it'll be either without duplicates, as Ben seems to be doing, or using bintray sync.

I actually use vultr for ci