Sabeeh
08/12/2024, 9:53 AMamakeev
08/12/2024, 10:04 AMSabeeh
08/12/2024, 9:48 PMe: KLIB resolver: Could not find "ksoup:ksoup-core-placeholder" in
amakeev
08/14/2024, 8:39 AMSabeeh
08/15/2024, 2:57 PMksoup-korlib
which use korlib for IO and the other ksoup-kotlinx
, which use kotlinx-io, so users can choose between them. The concept of using Ktor engine modules is one solution that could work. However, my main issue is that it would require changing the current APIs. Right now, all the publish functions are static and can be accessed directly through the Ksoup
object class. To follow the engine module approach, I would need to add library initialization code, and users would need to create an instance of the library to use it. This would break the code for users upgrading to the new version. Ideally, I’d like to create an API module with engine-dependent function bodies set as TODO()
, which could then be replaced at compile time with the original module for ksoup-korlib
or ksoup-kotlinx
. I’ve already implemented this successfully for JVM, but it hasn’t worked for Native or JS. I'm getting compiler error:
e: KLIB resolver: Could not find "ksoup:ksoup-core-placeholder" in
I will create simple sample code and send it to you later.Sabeeh
08/15/2024, 5:05 PM