Is it possibile, inside `targets`, to place an `android` clause including a sibling module that is a...

# multiplatform

[Riccardo Montagnin]

Is it possibile, inside targets, to place an android clause including a sibling module that is an android app?

I have the current structure:

project 
   |- android-app
   |- common
        |- commonMain
        |- iosMain
        |- jvmMain

I would like to create some actual implementations inside the android-app module, which is an Android application module. How would I have to do?

Right now when I compile the Android app the jvmMain is compiled, but I would like to provide some custom actual implementations for the Android app

[Sabrina Namur]

As far as i know it is not possible to use expect/acual between two modules. But i think you can add a addition target 'android' inside your common module and compile it like you do it with your jvmMain.

[ribesg]

You should merge your android project and your mpp project. I have a single build.gradle.kts

[ribesg]

project 
    |- commonMain
    |- androidMain
    |- iosMain
    |- jvmMain

[Riccardo Montagnin]

Mmm ok, I'll try that as I'm currently setting up everything from scratch

[gildor]

It actually depends on your use case

[gildor]

if your MPP is library used by multiple platforms, it’s fine to keep Android app separately, but if your project is a multiplatfrom application, than I don’t see why would Android app should be separated

[Riccardo Montagnin]

It will actually be an application, yeah. I want to create an Android, iOS and desktop application that shares the same code between all of them

[Riccardo Montagnin]

The desktop app will be made using Java, but with different implementations than the Android version. That's why I'd like to have a commonMain, an iosMain a jvmMain and an androidMain

[gildor]

yes, it make sense

[Riccardo Montagnin]

Should I go with one module or multi modules?

[gildor]

Multi modules? Depends on your architecture. This supported by mpp

[ribesg]

I guess it’s a matter of preference, I prefer to have a single build file, but I understand that one could need to split some things, especially in the case of mobile apps with tons of flavors

[h0tk3y]

By the way, even with one module, one can still split the build logic by moving parts of the main script into *.gradle or *.gradle.kts script plugins and applying them in the main build script.

[ribesg]

That’s right, if you need an example of that I think Ktor uses that a lot in its build

[Riccardo Montagnin]

Thank you all guys

[uli]

Is it possible to have one more source set, common to Android and jvm? For things that are the same on both platforms but different on iOS?

[ribesg]

Yes, just define a new sourceSet and state that both the android sourceSet and the jvm sourceSet depend on it

[uli]

thx