I&#39;ve been getting Racket (not GRacket) work on iPad, without jit support but with libffi enabled (thanks to the work which has been done by someone else). My intend is to be able to run DrRacket from iPad, so that I could write rkt while I&#39;m on the way. &quot;Mono&quot; right now seems doing a good job on iOS and Android. I believe it should be not that difficult to cross-compile the relative small C code, and I could try hopefully this week based on my work for iOS. In order to make DrRacket to work, we&#39;ll have to rewrite gui part or create a brand new UI for Mobile DrRacket, am I understanding right?<div>
Looking forward to dogfood DrRacket on my favorite mobile device :)</div><div><br></div><div>Nevo<br><br><div class="gmail_quote">On 19 January 2011 10:51, Neil Van Dyke <span dir="ltr">&lt;<a href="mailto:neil@neilvandyke.org">neil@neilvandyke.org</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Has anyone looked at the implications that the emerging Android NDK (ARM native code support) has for Racket on Android devices?<br>

<br>
I&#39;m wondering whether native code possibilities can change the development strategy radically. Like, for example, starting as a port by simply getting the existing C code to cross-compile, hack up a NativeActivity for it, get it to boot without GC, and going from there to see how viable to move forward. Could this be a fast path to getting full Racket, even including DrRacket, on Android?<br>