Using framework projects that build iOS and Mac versions of the same name lead to problems
| Originator: | hello | ||
| Number: | rdar://19075796 | Date Originated: | 11/24/14 |
| Status: | Open | Resolved: | |
| Product: | Xcode | Product Version: | 6.1 |
| Classification: | Reproducible: |
Summary: I've attached a sample project that illustrates the problem. I have a top-level iOS Framework project in a workspace. Its sole target depends on a framework from the "TestFramework" project in its workspace. When building in Xcode this arrangement works fine. When building with xcodebuild you can't predict wether it will build the iOS or Mac version of the Framework. Something is definitely weird about adding the TestFramework to the link list. If you hit + and select the iOS framework and then select the framework in the file browser its path is "Debug" and not "Debug-iphoneos". It's like its picking the wrong one but Xcode can somehow figure it out. Maybe this is a separate and unrelated bug? Steps to Reproduce: 1. Unzip the archive 2. in Terminal cd into the iosFramework folder 3. run the runme.sh file while nukes the build folder and builds the framework 4. repeat step 3 over and over Expected Results: I would expect it to successfully build the iosFramework target every time. Actual Results: What happens is that 50% of the time it builds properly and 50% it fails. When it fails its because the Mac version of TestFramework is being built instead of the iOS version. Version: Xcode 6.1 Build version 6A1052d Notes: Configuration: Attachments: 'xcodebuild-framework-bug-5ca9bf067ac2d7b15c31e2947b88d92c8408866c.zip' was successfully uploaded.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!