Has anyone got recent experience of building an Xcode project (XP) for iOS, having the j901 source code directly embedded as a "group"?
By "recent" I mean Xcode version 11 running on macOS Mojave. I have a working iOS prototype that calls libj.dylib, and runs on my private iPad. I was rather pleased with it. But when I uploaded it to App Store for TestFlight release Apple told me the dylib needs to be separately reviewed and granted a certificate. *Any* change to the dylib thereafter needs a new certificate – which needs a new review. So… although it is possible to ship an iOS app containing a dylib, Apple really wants to see a monolithic block of code in the app, plus having the archived XP for inspection. I reluctantly conclude I'll get an easier ride through the development cycle if I include jsource directly in the XP of the app. Which is just what the j701 release for iOS did. You'd think it would be a simple matter to replace the *.c and *.h files of the original j701 XP with its j901 counterpart: jsource-master/jsrc/. It isn't. (Not with my present level of knowledge of how jsource works). But has anyone done it – or anything remotely like it with Xcode? Which .c or .h files do I customize -- or omit? (They don't all compile). How do I find my way among the battalion of compiler directives? My main sticking point is: cpuinfo.c. I also have problems with andjnative.c, linenoise.*, not to mention aes*.* . None of these files were present in 701 jsource (…which I think I now broadly understand). I managed to hack the 901 code to make it compile and build, but the resulting app was corrupt, and made my iPad gag. Obviously I'd thrown the baby out with the bathwater. Is the iOS platform supported by jsource? I'd guess not. But there's code in there which engages with it. Which makes me think that someone has tried already. Did they succeed? Ian Clark ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
