Is it possible to set up my project such that I ca...
# compose-desktopz
zt
07/02/2023, 10:45 PMIs it possible to set up my project such that I can use expect/actual for platform dependent code? My application runs on both windows and linux
👍 2
j
jw
07/03/2023, 12:26 AMI think you can use normal polymorphism (i.e., an interface and two implementations) more simply than what it would take to actually use expect/actual
z
zt
07/03/2023, 12:57 AMMaybe that would work. Just not sure how to implement the part to choose which implementation to use
j
jw
07/03/2023, 12:58 AMYou would check against
System.getProperty("os.name")z
zt
07/03/2023, 12:59 AMI suppose that would work. I was thinking more something where I can have the windows executable contain the windows implementation and vice versa rather than both platforms containing both implementations
j
jw
07/03/2023, 1:00 AMi mean, you can do that but it's just more complicated to set up
z
zt
07/03/2023, 1:02 AMI'm willing to try it and learn something new
j
jw
07/03/2023, 1:20 AMI'm pretty sure the solution is to abandon Compose Desktop's built-in packaging, have OS-specific jvm targets, and use jlink/jpackage to build your own binaries.
👍🏻 1
jw
07/03/2023, 1:21 AMAs a bonus, unlike Compose Desktop's built-in packaging support, you can "cross-compile" (or, cross-bundle) the packages for Windows and Linux on whatever OS you want as long as you have that OS's JDK.
m
Michael Paus
07/03/2023, 6:28 AM@jw Could you please elaborate on that? Jpackage has no cross-building capabilities. (Which is a pity.)
m
Marcin Wisniowski
07/03/2023, 10:34 AMI will soon be starting a Compose Desktop project that should run on Linux and Windows, is the built-in packaging not good?
For platform specific code I was thinking to use separate Gradle modules per platform, containing the implementations of common interfaces.
m
Michael Paus
07/03/2023, 10:54 AM@Marcin Wisniowski The built-in packaging is OK but has a few limitations. E.g., you cannot cross build for another platform. I.e., you have to run the build on the same platform for which you want to create the build. This is mostly because jpackage uses some platform specific tools for certain tasks. I use GitHub hosted action runners to solve that issue. The only problem is that GitHub still does not have runners for all platforms, e.g., ARM macs but Rosetta 2 comes to the rescue in this case.
3 Views