(26-03-2020, 12:06 PM)Gleb Palchin Wrote: To recreate the problem do this steps:
1. Create an empty Unity project in Unity 2019.2.20f1
...
Exact same bug, Catalina 10.15.2, Xcode 11.5, Unity 2019.3.12f1
It's an Obi thing, we have done 10 projects and released 3 with these configuration, without any problem.
(30-03-2020, 09:14 AM)josemendez Wrote: Depends entirely on how/when Apple responds to my bug report (posted a screenshot of it in this thread: http://obi.virtualmethodstudio.com/forum...p?tid=2124). No response yet, but it's been weekend so let's give them a few days.
This is a serious bug btw, as most static libraries I've tried to link against cause 11.4's linker to hang.
I can't do anything from my end. Unity forces native plugins to be statically linked in iOS, so though luck. Unfortunately we're in their hands.
An update would be appreciated, it's been two month. Thanks
(26-03-2020, 04:22 PM)josemendez Wrote: I'm pretty sure it has something to do with xcode.
As said, Obi's physics engine comes precompiled (the libOni.a file) and the C# wrapper is compiled by Unity when generating the xcode project. So all Obi related code arrives at xcode compiled and ready to be run. For some reason, xcode is choking when linking the project, but really sounds like a xcode issue. It should either link successfully, or return a linker error, not get stuck forever.
What Xcode version are you using, btw?
I don't think this is how it works anymore. Your code is compiled to an intermediate language using bitcode, the actual machine language is generated later (probably at link time). So there is definitely some sort of compilation going on at link time. It can also happen on the App Store servers if you choose so
https://medium.com/codebbkaf/what-is-bit...dd8a434af8