Open danielPerez97 opened 1 day ago
We also have a display link clock in Redwood, so it's possible we need to port over some improvements from it.
Hmm, I may try to rip the DisplayLinkClock code from Redwood, and rebuild Molecule locally with some includeBuild()
magic then. Would this be the file to rip?
I'm completely new to getting a Kotlin Multiplatform library to run on iOS, if there's any way you know where I can get you better error messages I'd be happy to enable whatever I need to. I'm really unsure if this is even a Molecule issue.
Edit: It seems there is some redwood-specific stuff in the DisplayLInkClock. I'll just wait on an update, thanks for the help.
This is the one we use in production: https://github.com/cashapp/redwood/blob/trunk/redwood-treehouse-host/src/iosMain/kotlin/app/cash/redwood/treehouse/IosDisplayLinkClock.kt
It's not exactly the same setup as a "normal" FrameClock
, but it drives an abstraction which is nearly identical.
Hello. I'm not entirely sure this is an error with Molecule itself or I am just setting up the Gradle code for building the XCFramework poorly. Any help would be appreciated. I am building a Kotlin Multiplatform module that uses Molecule for iOS and trying to run it mixed with Swift code.
Here is the error in XCode:
I've put the code in this repo. Running the Android app works perfectly using the
:Frontend
module, but just not having the same luck on iOS. https://github.com/danielPerez97/Pourover/Steps to Recreate: 1) Run
gradlew Frontend:assembleFourSixFrontendLibDebugXCFramework:
2) Copy the XCFramework atFrontend/build/XCFrameworks/debug/FourSixFrontendLib.xcframework
intoiOS/Pourover
3) Run the iOS app on a simulatorLike I said I'm not sure this is a Molecule issue, and feel free to close it if it isn't.