As commonizer develops, is there any hope for impl...
# announcementsb
Big Chungus
11/24/2020, 10:10 AMAs commonizer develops, is there any hope for implicit platforms for published libraries? i.e. I write a lib that has all its code in commonMain sourceSet (no platform-specific dependencies) and as an author, I only declare JS & WASM32 targets. However since all metadata is available for all other targets, it should be possible to build platform-specific artefacts (i.e. JVM) on the consumer's side, even if the author didn't publish JVM artefact. Thoughts?
This might require changing the way how libraries are published at the moment, instead of publishing platform-specific artefacts and simply choosing between flavours at consumer end, it could publish main klib artefact (that has common code) and platform-specific "appendixes". These could be then used on consumer size to figure out what platforms the lib can support (in case of common-only code this should be all platforms) and generate required platform-specific artefacts.
Basically lowest common denominator problem
2 Views