Hey guys, I have 4 modules: 1. `app` plain JVM module + Android ( depends on `third` ) 1. `second`...

# multiplatform

[Davide Giuseppe Farella]

Hey guys, I have 4 modules:
1. app plain JVM module + Android ( depends on third )
2. second multiplatform without Android ( depends on third )
3. third multiplatform + Android module ( depends on fourth )
4. fourth
fourth is supposed to contain Android-only source code, so how should I set it up? Should it be multiplatform + Android or JVM only + Android?
I tried some stuff, but I have

(xxx) Could not resolve project :fourth

Required by:

project (yyy)

*Replace (xxx) with secondsourceSet and thirdsourceSet and (yyy) with :third and :second > :third

[Davide Giuseppe Farella]

Specifically:
• second is a module with integration tests
• third is a DI module, where I aggregate Koin modules from various modules
• third has an expected val AndroidModule
• on third:androidMain I aggregate Koin modules from Android modules ( HomePresentationModule for example )
• forth is an Android presentation module, it contains the Koin module HomePresentationModule

[Javier]

forth can be an android library which third can add in the android source set dependencies

[Davide Giuseppe Farella]

I tried something like that but failed.
I was thinking that it might be better to have:
• app > third:android
• second > third:kotlin

[Davide Giuseppe Farella]

So split third in 2 submodules

[Javier]

Which is the fail?

[Davide Giuseppe Farella]

The one I mentioned in the first message

[Javier]

there is no difference between a kmp with android which only has android code and an android library

[Javier]

have you done androidMain.dependencies { implementation(...) }?

[Davide Giuseppe Farella]

So I probably did something wrong 😄 But btw having 2 separate lines would be better

[Javier]

on third

[Javier]

or you tried in commonMain

[Davide Giuseppe Farella]

Tried that and

dependencies {
  implementation()
}

[Javier]

that is not going to work

[Javier]

if you want to use the normal dependencies block

[Davide Giuseppe Farella]

*an was supposed to be and

[Javier]

you need to

dependencies {
    "androidMain"(...)
}

[Davide Giuseppe Farella]

Tried both

[Javier]

if you run ./gradlew third:assemble, does it work?

[Davide Giuseppe Farella]

Same error, but doesn’t matter much now 😄

[Javier]

is it open source?

[Davide Giuseppe Farella]

https://github.com/4face-studi0/CineScout

[Davide Giuseppe Farella]

Pushed a commit now with the change I mentioned

[Javier]

which is third and which fourth

[Davide Giuseppe Farella]

third is cinescout/di , fourth is cinescout/home/presentation

[Javier]

not sure if it is a GitHub outage or you have deleted the content of those files

[Davide Giuseppe Farella]

First one should be home/presentation , not only home , second you’re looking into the last commit

[Davide Giuseppe Farella]

Look into the one before, as now I have di/android and di/kotlin

[Davide Giuseppe Farella]

Empty gradle files are required for my modules plugin, otherwise I cannot guarantee a path for modules

[Davide Giuseppe Farella]

Because /home/presentation, for example, would have a different path whether home is a module or a plain folder, so I made them all modules 🙂

[Javier]

weird setup, intermediate path are already modules too without those gradle files

[Davide Giuseppe Farella]

No, they’re just plain folder

[Javier]

gradle treats them as modules anyway

[Davide Giuseppe Farella]

In my case, home-presentation path is :cinescout:cinescout-home:cinescout-home-presentation , without it would be :cinescout:cinescout-home-presentation

[Racka N]

Weird setup. Though your issue might be because you don't have an android() target inside the build.gradle file for di/kotlin. Specifically inside the kotlin {} block

[Davide Giuseppe Farella]

I may didn’t update my repo, but I added it before trying ( same as manifest file )