You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure whether this is desired or not but I noticed that tools/build_ios.sh supports PLATFORM_NAME=iphonesimulator. Unfortunately when I try to compile with this I end up running into linker errors with my application. The error is as follows:
ld: building for 'iOS-simulator', but linking in dylib ([...]/cktap-protocol-flutter/contrib/tap-protocol/build/libtap-protocol.dylib) built for 'iOS'
I tried modifying the CMakeLists.txt to use the correct libsecp256k1.a when building for the iOS-simulator but it doesn't fix the core issue.
For my use case I will test if there's a way I can work around this by excluding my plugin from building when targeting an iOS simulator. Feel free to close this if you don't wish to support the simulator.
The text was updated successfully, but these errors were encountered:
Hi,
I'm not sure whether this is desired or not but I noticed that tools/build_ios.sh supports
PLATFORM_NAME=iphonesimulator
. Unfortunately when I try to compile with this I end up running into linker errors with my application. The error is as follows:ld: building for 'iOS-simulator', but linking in dylib ([...]/cktap-protocol-flutter/contrib/tap-protocol/build/libtap-protocol.dylib) built for 'iOS'
I tried modifying the CMakeLists.txt to use the correct libsecp256k1.a when building for the iOS-simulator but it doesn't fix the core issue.
For my use case I will test if there's a way I can work around this by excluding my plugin from building when targeting an iOS simulator. Feel free to close this if you don't wish to support the simulator.
The text was updated successfully, but these errors were encountered: