We have a relatively complicated project, where our iOS application is relying (dependent on and linking against) 3 iOS static framework, which in turn rely on a few more iOS static frameworks. They even have cross usage. All the iOS static frameworks are of our own making (internal to the organization), and build from our projects. It all works fantastic with Xcode 5.1.1, and even on Xcode 6.x.x, Except for building for simulator.
Then our application emits 3 link errors, that it can't find the framework binaries. When I look into the ~/Library/Developer/Xcode/DerivedData/ourProject_xxx/Product/Build directory, I see that the frameworks are actually built for simulator, but with a wrong binary name (and possibly wrong format)
Whereas the normal (non-simulator) builds have the binary at myFramework.framework/myFramework, in the simulator build I have myFramework.framework/objMyFramework.a instead. Of course the linker fails to find this, trying to build against the framework.
Now I don't see any build-scripts or post-build scripts in our iOS-Static Framework targets --- maybe it is part of the template installed somewhere in the bowels of Xcode itself --- so I don't know how to start debugging this. If anyone can help me start, I'd be forever grateful. I know this project will soon die, but since we MUST release our application for iOS 6 or later - we can't use the new dynamic frameworks for a while.
We have a relatively complicated project, where our iOS application is relying (dependent on and linking against) 3 iOS static framework, which in turn rely on a few more iOS static frameworks. They even have cross usage. All the iOS static frameworks are of our own making (internal to the organization), and build from our projects. It all works fantastic with Xcode 5.1.1, and even on Xcode 6.x.x, Except for building for simulator.
Then our application emits 3 link errors, that it can't find the framework binaries. When I look into the ~/Library/Developer/Xcode/DerivedData/ourProject_xxx/Product/Build directory, I see that the frameworks are actually built for simulator, but with a wrong binary name (and possibly wrong format)
Whereas the normal (non-simulator) builds have the binary at myFramework.framework/myFramework, in the simulator build I have myFramework.framework/objMyFramework.a instead. Of course the linker fails to find this, trying to build against the framework.
Now I don't see any build-scripts or post-build scripts in our iOS-Static Framework targets --- maybe it is part of the template installed somewhere in the bowels of Xcode itself --- so I don't know how to start debugging this. If anyone can help me start, I'd be forever grateful. I know this project will soon die, but since we MUST release our application for iOS 6 or later - we can't use the new dynamic frameworks for a while.
Please help!