Not sure if you are aware but the project templates for iOS have been broken since Xcode 6. I'm going to look at fixing them but they are not in the repo so I thought I'd ask if you want them in there. Perhaps it would be better to have a gyp file in the repo that could be used to create a project. Obviously for iOS and OSX the Xcode projects are helpful though. The other thing I thought I might do is get the test app working again and ideally pull engines from the repo.

I had a little look at this today and it is the test app that is breaking things for Xcode 6+. If the test app target is deleted then you get the static lib target. I tried a few things and couldn't resolve it quickly.

The above templates combined with instructions in the README for getting what we need to build externals from the LiveCode repo is probably a good enough replacement for the iOS externals SDK which is no longer being maintained. I still need to work out the test app stuff. It doesn't look too complicated but ideally there won't need to be any user intervention required to create the test standalone.

Is it possible to run the OS X dev engine -ui. Seems to break here. I'm trying to work out if I can build the iOS external test engines on the fly rather than using pre-built standalones. It's looking like it's going to be tricky. Probably not a huge issue to open up a stack and click a button in the IDE to build new test engines when we need them.

Ok... so I need a linked version of the device build to build the test harness from so I've made some tweaks to bind-ios-standalone.sh in order to pump out standalone-mobile-community-linked.ios-engine. Next step is to work out how to do a deploy build for the test harness as an extra build phase. As we can't call on the dev engine here I was wondering about the feasibility of a command line deploy tool. lc-deploy would be quite helpful for CI too...