spierce7
01/27/2023, 8:48 PMDragos Rachieru
08/10/2023, 11:24 AMspierce7
08/10/2023, 11:20 PMLucas Marçal
08/07/2024, 6:07 PMErik Kerber
10/17/2024, 4:23 AMrules_jvm_external
, which is the de-facto way of resolving Maven dependencies, does not really yet understand KMP. This mostly means you should expect to manually list out coordinates for various platform-specific libraries. It's more an annoyance than a blocker.
• There exist no open source rules that leverage kotlin-native
to build i.e. Apple/Windows apps. There are companies that have their own rules that do, and I don't think are that hard to make if you are familiar with rule writing.spierce7
10/17/2024, 10:16 PMErik Kerber
10/17/2024, 10:18 PMspierce7
10/17/2024, 10:18 PMspierce7
10/17/2024, 10:19 PMErik Kerber
10/17/2024, 10:22 PMspierce7
10/17/2024, 10:43 PMsheatrevor
12/05/2024, 12:01 AMsheatrevor
12/05/2024, 12:05 AMSridhar Mocherla
06/23/2025, 3:22 PMrules_jvm_external
https://github.com/bazel-contrib/rules_jvm_external/pull/1357 so we should be able to resolve KMP artifacts automatically for different platforms with gradle metadata with a small amount of follow-up work (right now it'll resolve JVM as the default platform and we need to request explicit variant attributes for other platforms). I am going to look into adding that next and then look into adding back JS support in the rules (assuming there's no one else looking into it).