Thanks, everyone, for all your help. Disabling base internationalization seemed to be the final step, and, thankfully, it didn't erase my xib files. It unlinked them, since they were still in the base.lproj folder, but it was easy to get them back. The app now runs on my Lion machine, and the whole experience taught me a lot. No word yet on if it runs on the machine of the man I'm hoping to work with, but I see no reason it would not. I really appreciate all your help, and I hope this will be the only major Xcode issue I run into during this project. :)
On May 30, 2014, at 1:28 AM, Alex Hall < email@hidden> wrote:
On May 30, 2014, at 12:47 AM, Jeff Schriebman <email@hidden> wrote:
Yes it should still compile.
I build against 10.6 using the latest version of Xcode all the time and my programs run perfectly on 10.6 through 10.9.
You just need to make sure you haven’t used any 10.8 or 10.9 only subroutines in your code.
I was hoping that building against the 10.7 SDK would cause Xcode to point out any such uses of newer features. I now have 0 warnings or errors, though, yet the app still won't open on Lion.
Make sure you have set all of your build settings appropriately for 10.7. There should be no 10.9 SDKs being accessed at all, only 10.7.
I think that Lion is choking on your use of the 10.9 SDK. Linking against 10.7 your app should run fine on 10.7, 10.8 and 10.9.
I've looked, but can't find any 10.9 settings. However, I'm not sure which files to look at; the .xcodeproj and .xib, of course, but all the rest are just .h and .m files. Is there anywhere else I should be inspecting to check for 10.9 usage? As I said, Xcode isn't showing any errors or warnings at all, In fact, it won't even let me run the app now - it says:
Xcode cannot run using the selected destination. Choose a destination with a supported architecture in order to run on this system.
Good luck.
Thanks, I think I'm going to need it! :)
--
Have a great day, Alex Hall
|