utenma
11/22/2024, 1:12 AM$compose.desktop.currentOs
but there is no way to use current os in other dependenciesmagnumrocha
11/22/2024, 10:24 AM# Android-only dependencies
dependencies@android:
# Android-specific integration with Compose
- androidx.activity:activity-compose:1.7.2: exported
- androidx.appcompat:appcompat:1.6.1: exported
utenma
11/22/2024, 1:34 PMAnton Prokhorov
11/27/2024, 10:45 AMcompose.desktop
there is no way to use current os for other dependencies
however, I'm curious: what do you need that for? Let's discuss: do we need that feature or if there is a better way to do thatmagnumrocha
11/27/2024, 12:45 PMAnton Prokhorov
11/27/2024, 2:25 PMmagnumrocha
11/27/2024, 3:22 PMmagnumrocha
11/28/2024, 8:22 AMAnton Prokhorov
11/28/2024, 11:34 AMjvm
target which is truly cross-platform in wild nature might exist, indeed
However, keep in mind that scenario you are describing according to me, doesn't exist yet
There is a compiler limitation, you can't just depend on library with native targets from jvm module
I get the intention here, though
For now the reason why $compose.desktop.currentOs
escape hatch exists is that every package contains OS-dependant binary called through jni
There are other ways how to do that all of them aren't perfect, though
This is why I'm eager to see more real-life examples of this to understand the actual demand considering all the limitations of runtime/compiler/etcutenma
11/28/2024, 4:18 PM