-
Notifications
You must be signed in to change notification settings - Fork 565
Support iOS i386 (32bit simulator) KonanTarget #2615
Comments
Not sure what's the practical sense of doing that. |
our continuous integration enumerates all the supported iOS builds and runs unit tests in a simulator on them. We support iOS 10 which has arm32 devices supported still, and the simulators that run those images need i386. |
Considering Apple is phasing out 32-but phones/tablets, and iOS 11 doesn't support 32-bit devices, not sure is 32-bit simulator is critical for most users. Is it indeed absolutely critical in your case? |
AFAIK Apple Watch (except latest Series 4) is still 32-bit. But watch also requires mandatory bitcode. |
watchOS is different story, and we may eventually support it. |
isnt watchOS already supported since embedded bitcode is supported?
32bit simulator definitely is not critical in my case. It was a weird situation that we hit that others may also hit, but on our end we're just going to only build arm and not x86 from CI. We may re-enable x86 builds for all supported devices later if this becomes supported. |
watchOS requires a bit more than we have: #1202 (comment) |
got it - thanks for clarification |
+1 for x32 support, if it is not too onerous. I am running into an issue with arm32 and it might be useful to be able to debug in the iPhone 5/4S simulator. |
We have no plans to support 32-bit iOS simulator. |
Our CI build runs unit tests against every supported simulator, right now it's failing attempting to link the generated kotlin framework for the i386 architecture (x32). Would it be possible to add an
iosX32
target to support old simulators?Thanks in advance!
The text was updated successfully, but these errors were encountered: