On 1/08/2015 4:43 a.m., Joakim wrote:
On Friday, 31 July 2015 at 04:45:30 UTC, Rikki Cattermole wrote:
So how far off are we in having a D Android stack?
Depends what you mean, native apps do not have access to the Android GUI
and some other APIs, which are only available through Java, ie JNI. So
if you simply mean running all of D on Android, not far, a couple more
modules to fix and one important GC issue, as I mentioned. If you mean
GUI and those other Java APIs, OpenGL is available now but I haven't
messed with JNI yet, doubt it'll be a problem though.
I'm aware of these issues, it's one of the reasons I forked Djvm.
Unfortunately I haven't yet worked more on my Java parser which would
make making bindings pretty easy.
With full redistribution support on dlang.org.
Not sure what you mean by redistribution, the Android NDK? If you just
mean distributing a D cross-compiler for Android/ARM, shouldn't take
long to fix these remaining issues, but it all depends on how many
people pitch in.
More or less neither.
Basically D cross compilers on all the main platforms that really only
require, here is my NDK install now lets make .adk's.
Distributed over dlang.org downloads page.
But what you are saying is very appealing ;)
I'm definitely looking forward to the point where I have no choice but
to continue working on my fork of Djvm to make it worth while to use
Android with D :)
