On 2013-12-03 10:43 AM, Iain Buclaw wrote:
On 3 December 2013 15:30, Joakim <[email protected]> wrote:
On Tuesday, 3 December 2013 at 15:13:36 UTC, Johannes Pfau wrote:
Am Tue, 03 Dec 2013 12:26:57 +0100
schrieb "Joakim" <[email protected]>:
Seems like you got pretty far with your Android port: are you planning on
submitting any of these patches back upstream?
At some point, probably yes. However, I want to get the 'easy' stuff
working first. This means a stable and well-tested ARM/Linux/glibc
build should be available first. (It makes more sense this way as we
still have/had some ARM codegen bugs in the compiler.)
OK, anything against putting your incomplete Android port online someplace,
say on github? I'm working on an Android/x86 port now, that way we could
work together and submit our patches together. This would especially allay
Iain's concerns about future conflicts between Android/x86 and Android/ARM
patches. My work is publicly available here:
https://github.com/joakim-noah/druntime/tree/android
They are also the concerns of Walter, David and Kai. But yes I'm a
bit more vocal about it than some. :~)
I'm very interested in this, more specifically when ARM support is such
that porting the vibe.d library to Android/ARM or Linux/ARM in general
would allow lightweight micro serial-port servers like the BeagleBone to
be operated on with WebSockets. This would definitely make robotics more
simple. I know it would be interesting for me, I'd use it to build a
simple, mini RC airplane equipped with a GoPro! camera that works over
LTE. Oh the fun I'd have :) Keep it up
