<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 21 Apr 2020, at 7:57 am, Chris Double <<a href="mailto:chris.double@double.co.nz" class="">chris.double@double.co.nz</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Tue, Apr 21, 2020 at 7:06 AM Steve Dekorte <<a href="mailto:steve@dekorte.com" class="">steve@dekorte.com</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">Is there a build of Self for MacOS Catalina (which is now 64bit only)?<br class=""></blockquote><br class="">Unfortunately Self is still 32bit only. I think Russell uses Mac OS so<br class="">might have a work around involving virtual machines.<br class=""></div></div></blockquote><div><br class=""></div><div>It’s difficult. It isn’t just a matter of, say, Ubuntu where all you need to do is load or package the 32 bit system libraries. I did play with putting together a Linux VM with a Mac user land tool taking advantage of the Mac’s Hypervisor.framework (See eg <a href="https://github.com/machyve/xhyve" class="">https://github.com/machyve/xhyve</a>) But then you would need to have a bridge over localhost or something to talk to the Mac side to get a GUI etc.<div class=""><br class=""></div><div class="">In the end I’ve been playing instead with the online OurSelf stuff because it gets me Mac, but also Windows and iOS and a collaborative framework not just an image on a local system.<br class=""></div><div class=""><br class=""></div></div><div>Also I’m getting used to being able to just walk away from my Self world on my desktop and open it up at the same point on my laptop or iPad!</div><div><br class=""></div><div>Russell</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">I did some work a while back trying to get Self running on x86_64 by<br class="">reviving the bytecode interpreter rather than using the JIT - which<br class="">would require writing an x86_64 JIT. I wasn't able to get the<br class="">interpreter running though - I don't think it ever worked or it has<br class="">bitrot since the releases that it did work. I think if I were to<br class="">revisit it, using LLVM, or some other existing code generation<br class="">framework, might be a better idea just to get something running.<br class=""><br class="">-- <br class=""><a href="https://bluishcoder.co.nz" class="">https://bluishcoder.co.nz</a><br class="">_______________________________________________<br class="">Self-interest mailing list<br class="">Self-interest@lists.selflanguage.org<br class="">http://lists.selflanguage.org/mailman/listinfo/self-interest<br class=""></div></div></blockquote></div><br class=""></body></html>