Can you have a mulitplatform project with a Multip...

# multiplatform

[basher]

Can you have a mulitplatform project with a Multiplatform subproject and avoid publishing an extra binary for the subproject? I'd like it all to end up in a single AAR, but it seems no matter what I do, the sub-project module shows up in the gradle module metadata, and then dependency resolution fails when I try to use the multi-project library

[Dominaezzz]

I don't think this is possible, unless your project is publishing binaries.

[basher]

overall project publishes an aar

[Dominaezzz]

I can assure you that you'd have to do some ugly hack.

[Dominaezzz]

Why have the subproject be separate?

[Dominaezzz]

Why not stick it in a different package?

[basher]

I want to pull it into a subproject as a step toward open-sourcing some code

[Dominaezzz]

Oh... so you're gonna publish it anyway. 😂

[basher]

So it will be eventually. It seemed like this was a good option as a step toward doing that. Turns out I then I have to publish again anyway

[Dominaezzz]

Can I ask what the subproject is (gonna be)?

[basher]

Sure! Working on open-sourcing the worker code that lets us run multi-threaded coroutine-type code in common code. It's not perfect, but it's keeping us out of the "no multi-threaded coroutines in native" hole

[Dominaezzz]

Interesting, I can't wait to see your approach. I've been postponing multi-threading for ages because I can't be arsed to freeze things.

[basher]

Spoiler: it freezes things

[basher]

I think that model needs some improvement around tooling (improved error messages, improved data structures that showcase how to work in this model, etc.), but once you learn the tricks to working with frozen structures, it's not so bad. just forces you to think differently about your problems

[Dominaezzz]

Agreed

[louiscad]

Subprojects are like sibling projects. If you depend on them, you need to publish them too.