Great... meanwhile, I can't upgrade to catalina because my file system was hfs+ and disk utility won't upgrade it to apfs, and -- generally speaking, I have noticed it getting to be more ... difficult... to isolate problems in osx systems.
Anyways, dual licensing has been around for quite some time now, and I can think of more important things to be scared about. Thanks, -- Raul On Thu, Dec 12, 2019 at 4:04 PM greg heil <[email protected]> wrote: > > >i have not been following this discussion close enough to know... but a > >recent uproar in the i'verse may be relevant: It seems Apple is now on the > >warpath against ALL GPL'd code ...(the presumption is they do not like the > >viral nature) ... so it may be necessary to rethink our open source approach > >... if we want to remain in the i'verse. > > ~greg > http://krsnadas.org > > -- > > from: Ian Clark <[email protected]> > to: Source forum <[email protected]> > date: Dec 11, 2019, 4:06 PM > subject: Re: [Jsource] building jsource in Xcode for iOS platform > > >Thanks Bill. That helps me prioritize the things I'll need to try. > > >I'm building a simplified experimental rig that I can share. Then I'll > repeat the errors I encountered in the context of a tested cookbook recipe > I'm writing, on how to hack /jsrc/. > > -- > > from: bill lam <[email protected]> > to: Source forum <[email protected]> > date: Dec 11, 2019, 3:40 PM > subject: Re: [Jsource] building jsource in Xcode for iOS platform > > >andjnative and linenoise are not needed for iOS. cpuinfo should be ok > >perhaps with some modification. you can ignore aes assembly sources and > >instead use the plain c reference source. > > >the clang complier already provides macro to indicate both iphone and ipad. > > >please let me know the specific error messages but right now I am on the > >road and can't give you immediate feedback. > > -- > > from: Ian Clark <[email protected]> > to: Source forum <[email protected]> > date: Dec 11, 2019, 2:14 PM > subject: Re: [Jsource] building jsource in Xcode for iOS platform > > Totally agreed, Eric. > > >I'm starting writing a clear cookbook-recipe on how to customize /jsrc/ --as > >downloaded from Github. And thus document how far I get. (It's a maze that > >will branch a bit, because there are so many things to try.) > > >It's in draft form, but soon fit to send to you. Who will quickly see where > >I've blundered. > > >Once done, it ought to be writeable back into jsource, with a compiler > >directive like: #ifdef IOS (… and in time: IPADOS too!) Until then we're > >committing ourselves to following this recipe again and again, with > >successive j901 releases. > > >It encourages me to know that nobody has yet done this. I was getting > >discouraged to think I was reinventing the wheel. > > -- > > from: Eric Iverson <[email protected]> > to: Source forum <[email protected]> > date: Dec 11, 2019, 1:54 PM > subject: Re: [Jsource] building jsource in Xcode for iOS platform > > >Your message was bang on. Unfortunately no on know anything about this stuff > >except for me. And what I did was as brutal a quick hack as I could do to > >get something to work. Your task with 901 is much more difficult. We want > >something that works that we can also properly integrate into the source so > >that 902 is a much simpler step. > > >Main point right now is to not use dylib and to keep your hacks as few and > >as simple as possible with an eye to someday having them merged in with the > >main source. > > -- > > from: Ian Clark <[email protected]> > to: Source forum <[email protected]> > date: Dec 11, 2019, 1:47 PM > subject: Re: [Jsource] building jsource in Xcode for iOS platform > > Thanks, Eric. > > >But I knew you were busy and wanted to exhaust my own resources first. > > -- > > from: Eric Iverson <[email protected]> > to: Source forum <[email protected]> > date: Dec 11, 2019, 1:43 PM > subject: Re: [Jsource] building jsource in Xcode for iOS platform > > >I doubt anyone in the source forum will be able to help with you specific > >questions. I will get back to you directly with some answers. > > -- > > from: Ian Clark <[email protected]> > to: Source forum <[email protected]> > date: Dec 11, 2019, 1:36 PM > subject: [Jsource] building jsource in Xcode for iOS platform > > >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? > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
