this may be a silly question but im confused about creating

Question

this may be a silly question but im confused about creating a multi module application from the compose desktop starter project i know how to add a module on android but here it seems that the base module is top level the jvmMain and jvmTest directories i dont know whether to also consider them modules or not dont have their own build gradle file where i would add things like `implementation path common `

ephemient · Answer

jvmMain and jvmTest are not modules they are source sets

ephemient · Answer

similar to how a pure Android project will have main test androidTest debug debugTest debugAndroidTest release releaseTest source sets

abbic · Answer

ooh

abbic · Answer

fascinating

abbic · Answer

so then adding more seems like its only mostly relevant for multiple platforms

ephemient · Answer

if none of your code is platform specific then it would be expected that you only need commonMain and commonTest

abbic · Answer

makes sense +1 although this begs the question for me of how to actually implement modularisation in a project like this

abbic · Answer

as ive implied i only know how to do anything of the sort when working on android projects i dont even know what to google to get a primer on the matter

abbic · Answer

actually there s a question what do i call this kind of desktop jvm development in a way that will bring up relevant info on google

ephemient · Answer

it really isn t that different from Android s variants

ephemient · Answer

in the Android world by default you have ``` lib src main src debug src release app src main src debug src release``` ` lib` produces two variants `debug` which includes code from both `src main` and `src debug` and `release` which includes code from both `src main` and `src release` in ` app` code in `src main` can use code in ` lib` s `src main` code in `src debug` can use code in ` lib` s `src main` and `src debug` and code in `src release` can use code in ` lib` s `src main` and `src release` there s some boundaries here that aren t as well enforced as KMP but that s basically the idea

ephemient · Answer

similarly in your multiplatform setup you can have ``` lib src commonMain src jvmMain app src commonMain src jvmMain``` with the `jvm` platform containing code in both `src commonMain` and `src jvmMain` and matching across module dependencies

ephemient · Answer

within a single project module there are dependencies within source sets but that doesn t matter outside of the project

abbic · Answer

this tracks the only issue im seeing from my end is that directory wise things are laid out like ```root project lib src commonMain src jvmMain app src commonMain src jvmMain``` this makes sense to me but the default compose multiplatform project looks more like ``` root project src commonMain src jvmMain```

abbic · Answer

so the root build gradle is bot a root project gradle file and a module one and in IDEA when you add another module it is created in parallel like ``` root project src commonMain src jvmMain module etc```

ephemient · Answer

so you can create subprojects just fine even if there s code within the root project

abbic · Answer

and they dont seem to link up together like how id expect

ephemient · Answer

but if you want to modularize it I would move things from the root project into a subproject

ephemient · Answer

it works even if you don t though

abbic · Answer

yes thats the impression i was beginning to get from our discussion just move things around until they look like how id expect if i want to

ephemient · Answer

you ll just have ``` src lib src ```

abbic · Answer

this is also my first project with kotlin gradle files so its a bit of a double culture shock

abbic · Answer

nothing i cant handle though i think p thanks for your help