Here’s something that’s strange though, and maybe I’m just not totally understanding the problem exactly. LiveCode 6.6.3 supports Xcode 5.1.1, and builds against the iOS SDK included with that. Apple is supposedly still accepting apps built against that SDK (at least, that’s what iTunes Connect says). But I’m getting this error even when building my app with LC 6.6.3.
So I don’t get why it’s an issue. Something else going on? But it sounds like RunRev are aware of the problem and working on a fix, according to Mike Kerner just a minute ago. > On Sep 26, 2014, at 2:01 PM, Colin Holgate <co...@verizon.net> wrote: > > One interesting thing about the Adobe thread is the number of people who > seemed to be submitting apps right now, and were hit with the problem. > > In Adobe’s case they have their own version of the linker, because they need > to be able to publish to iOS from Windows, amongst other reasons. The work > around for now is to replace the Adobe ln64 file with the system’s ln file > (renamed), then when you compile an iOS app it ends up using Apple’s linker. > > The solution doesn’t work for Windows, Adobe will have to update their own > linker to fix things there. > > From what you say it could be that LiveCode does use its own linker, or it > has an engine that your stack gets bundled with, and that engine was created > with an older Xcode. > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
