July 31, 2015
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.

> 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.
August 01, 2015
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 :)
August 01, 2015
"Joakim" <dlang@joakim.fea.st> writes:

> Some good news, I've made progress on the port to Android/ARM, using ldc's 2.067 branch.  Currently, all 46 modules in druntime and 85 of 88 modules in phobos pass their tests (I had to comment out a few tests across four modules) when run on the command-line.

:-)
August 03, 2015
On Thursday, 30 July 2015 at 19:38:12 UTC, Joakim wrote:
> On Monday, 25 May 2015 at 20:08:48 UTC, Joakim wrote:
>> [...]
>
> Some good news, I've made progress on the port to Android/ARM, using ldc's 2.067 branch.  Currently, all 46 modules in druntime and 85 of 88 modules in phobos pass their tests (I had to comment out a few tests across four modules) when run on the command-line.  There is a GC issue that causes 2-3 other modules to hang only when the tests are run as part of an Android app/apk, ie a D shared library that's invoked by the Java runtime.
>
> [...]

Would those patches for ldc/druntime/phobos be applied & merged into LDC eventually?
August 03, 2015
On Monday, 3 August 2015 at 12:46:51 UTC, Elvis Zhou wrote:
> On Thursday, 30 July 2015 at 19:38:12 UTC, Joakim wrote:
>> On Monday, 25 May 2015 at 20:08:48 UTC, Joakim wrote:
>>> [...]
>>
>> Some good news, I've made progress on the port to Android/ARM, using ldc's 2.067 branch.  Currently, all 46 modules in druntime and 85 of 88 modules in phobos pass their tests (I had to comment out a few tests across four modules) when run on the command-line.  There is a GC issue that causes 2-3 other modules to hang only when the tests are run as part of an Android app/apk, ie a D shared library that's invoked by the Java runtime.
>>
>> [...]
>
> Would those patches for ldc/druntime/phobos be applied & merged into LDC eventually?

For the ones I wrote which have not been upstreamed already, yes, I'll submit PRs once I get them cleaned up.  For example, I'd like to devise a way not to use dl_iterate_phdr to load pre-initialized data, so that Android versions older than 5.0 can run D too.  I need to look into employing the same bracketed sections approach that dmd uses.
1 2 3 4
Next ›   Last »