Allow ios-sim to handle multiple versions of Xcode -------------------------------------------------- Key: JBIDE-17607 URL: https://issues.jboss.org/browse/JBIDE-17607 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Affects Versions: 4.1.1.Final Environment: Mac OS X Mavericks (10.9.3), Xcode 5.1.1 (preinstalled) and Xcode 5.0.2 (installed later) Reporter: Vineet Reynolds Assignee: Gorkem Ercan Fix For: 4.2.0.Beta3 I get the following error when running a HMT project in an iOS simulator on JBDS 7.1.1 GA: {noformat} dyld: Library not loaded: @rpath/iPhoneSimulatorRemoteClient.framework/Versions/A/iPhoneSimulatorRemoteClient Referenced from: /Applications/jbdevstudio7.1.1.GA/studio/configuration/org.eclipse.osgi/bundles/923/data//ios-sim Reason: image not found {noformat} Xcode 5.1.1 is default (Mac OS X Mavericks) and was installed into {{/Applications/Xcode.app/}}. Xcode 5.0.2 was installed into {{/Applications/Xcode 2.app/}} and was selected as the default version through {{xcodeselect}}. But the error was still reported. This is because the ios-sim binary is linked against the {{/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/PrivateFrameworks}} directory, as seen in output of {{otool -l /Applications/jbdevstudio7.1.1.GA/studio/configuration/org.eclipse.osgi/bundles/923/data/ios-sim}}: {noformat} ... Load command 17 cmd LC_RPATH cmdsize 128 path /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/PrivateFrameworks (offset 12) Load command 18 cmd LC_RPATH cmdsize 80 path /Applications/Xcode.app/Contents/Developer/../OtherFrameworks (offset 12) ... {noformat} Implying that Xcode must be installed into the /Applications/Xcode.app directory and not any other, which prevents {{xcodeselect}} from being completely useful to 'fix' the desired version of Xcode to use. The requirement is to not have this limitation of having the selected version of code installed into {{/Applications/Xcode.app}}. One way to workaround this limitation currently is to export the project as an Xcode project and then work on it in an older Xcode project.