As a result of #42 findings with limitations on running executables for iOS (not impossible but highly regarded), I believe it be best to provide 4 variants with differing support. This will require changes to kmp-tor-core and kmp-tor repositories
:resource-tor-static
:resource-tor-static-gpl
:resource-tor-exec
:resource-tor-exec-gpl
:resource-tor-static* supported targets:
Android
Jvm
Linux
iOS
tvOS
macOS
watchOS
Windows
:resource-tor-exec* supported targets:
Android
Jvm
Node.js
Linux
macOS
Windows
This requires a modification to kmp-tor-core:core-api module to provide a new abstraction (sealed class) which will provide the 2 implementations for all targets. For the time being, that new abstraction can be kept in this repository until work on this is completed, whereby it can then be moved to kmp-tor-core:core-api.
Once that is done, can update kmp-tor to account for the 2 loader methods and platforms.
05nelsonm
commented
2 months ago
As a result of #42 findings with limitations on running executables for
iOS(not impossible but highly regarded), I believe it be best to provide 4 variants with differing support. This will require changes tokmp-tor-coreandkmp-torrepositories:resource-tor-static:resource-tor-static-gpl:resource-tor-exec:resource-tor-exec-gpl:resource-tor-static*supported targets:AndroidJvmLinuxiOStvOSmacOSwatchOSWindows:resource-tor-exec*supported targets:AndroidJvmNode.jsLinuxmacOSWindowsThis requires a modification to
kmp-tor-core:core-apimodule to provide a new abstraction (sealed class) which will provide the 2 implementations for all targets. For the time being, that new abstraction can be kept in this repository until work on this is completed, whereby it can then be moved tokmp-tor-core:core-api.Once that is done, can update
kmp-torto account for the 2 loader methods and platforms.