January 28, 2012
On 2012-01-28 11:08, Nick Sabalausky wrote:
> What's the current state of D on iOS and Android? I know someone has been
> working on connecting D up to Objective-C somehow, and either GDC or LDC has
> at least partial support for Arm (but with some caveats, right?).
>
> Has anyone actually made anything in D on iOS and/or Android? It is feasable
> yet? (On just one, or on both?) If not, what's needed?

This would be one of the projects for connecting D with Objective-C:

http://michelf.com/projects/d-objc/

-- 
/Jacob Carlborg
January 28, 2012
On 28 January 2012 17:15, Jacob Carlborg <doob@me.com> wrote:

> On 2012-01-28 14:34, Manu wrote:
>
>> On 28 January 2012 14:58, Chad J <chadjoan@__spam.is.bad__**gmail.com<http://spam.is.bad__gmail.com> <http://spam.is.bad__gmail.com**>> wrote:
>>
>>    On 01/28/2012 05:08 AM, Nick Sabalausky wrote:
>>
>>        What's the current state of D on iOS and Android? I know someone
>>        has been
>>        working on connecting D up to Objective-C somehow, and either
>>        GDC or LDC has
>>        at least partial support for Arm (but with some caveats, right?).
>>
>>        Has anyone actually made anything in D on iOS and/or Android? It
>>        is feasable
>>        yet? (On just one, or on both?) If not, what's needed?
>>
>>
>>
>>    The state of D on Android ...
>>    http://interaxiom.blogspot.__**com/2011/08/android-d-stuff.__**html
>>
>>    <http://interaxiom.blogspot.**com/2011/08/android-d-stuff.**html<http://interaxiom.blogspot.com/2011/08/android-d-stuff.html>
>> >
>>    ... seems to be unmaintained?
>>
>>    I want this.  And if there's any way D android apps could run
>>    without rooting the phone, then I /really/ want this.
>>
>>
>> Since Android 2.3 it has been possible to run fully native apps, and a GDC for android will work just as well as any C compiler, although some work will have to be done to produce bindings for the NDK libraries. What I'm most excited about is being able to use D to wrap the NDK libraries to create an android experience that's very similar to the Android Java API's, but with native code throughout.
>>
>
> The ARM support needs to be added to the runtime.


Sure. I'd gladly do that myself the instant I had a toolchain.


January 28, 2012
On 2012-01-28 14:45:15 +0000, Manu <turkeyman@gmail.com> said:

> There's one problem with using D to write iOS software though, Apple
> strictly require that any apps submitted MUST use their XCode toolchain.

They've refrained from that a while ago.
<http://www.apple.com/pr/library/2010/09/09Statement-by-Apple-on-App-Store-Review-Guidelines.html>

-- 


Michel Fortin
michel.fortin@michelf.com
http://michelf.com/

January 28, 2012
On 28-01-2012 16:15, Jacob Carlborg wrote:
> On 2012-01-28 14:34, Manu wrote:
>> On 28 January 2012 14:58, Chad J <chadjoan@__spam.is.bad__gmail.com
>> <http://spam.is.bad__gmail.com>> wrote:
>>
>> On 01/28/2012 05:08 AM, Nick Sabalausky wrote:
>>
>> What's the current state of D on iOS and Android? I know someone
>> has been
>> working on connecting D up to Objective-C somehow, and either
>> GDC or LDC has
>> at least partial support for Arm (but with some caveats, right?).
>>
>> Has anyone actually made anything in D on iOS and/or Android? It
>> is feasable
>> yet? (On just one, or on both?) If not, what's needed?
>>
>>
>>
>> The state of D on Android ...
>> http://interaxiom.blogspot.__com/2011/08/android-d-stuff.__html
>> <http://interaxiom.blogspot.com/2011/08/android-d-stuff.html>
>> ... seems to be unmaintained?
>>
>> I want this. And if there's any way D android apps could run
>> without rooting the phone, then I /really/ want this.
>>
>>
>> Since Android 2.3 it has been possible to run fully native apps, and a
>> GDC for android will work just as well as any C compiler, although some
>> work will have to be done to produce bindings for the NDK libraries.
>> What I'm most excited about is being able to use D to wrap the NDK
>> libraries to create an android experience that's very similar to the
>> Android Java API's, but with native code throughout.
>
> The ARM support needs to be added to the runtime.
>

It's more or less done in GDC.

- Alex
January 28, 2012
On Sat, Jan 28, 2012 at 03:34:22PM +0200, Manu wrote:
[...]
> Since Android 2.3 it has been possible to run fully native apps, and a GDC for android will work just as well as any C compiler, although some work will have to be done to produce bindings for the NDK libraries.  What I'm most excited about is being able to use D to wrap the NDK libraries to create an android experience that's very similar to the Android Java API's, but with native code throughout.

+1 to this. I've been looking forward to getting an Android (either phone or tablet) and writing apps for it. If I can write apps in D, that would simply be awesome. (And you never know, maybe it will be an Android killer app that will make D really take off... ;-))

As far as I know, gdc can already produce ARM code since it uses the gcc backend. All we need now is a nice native D interface to the Android libraries, and I'll be a very very happy man.


T

-- 
The early bird gets the worm. Moral: ewww...
January 28, 2012
On 28 January 2012 18:19, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:

> On Sat, Jan 28, 2012 at 03:34:22PM +0200, Manu wrote:
> [...]
> > Since Android 2.3 it has been possible to run fully native apps, and a GDC for android will work just as well as any C compiler, although some work will have to be done to produce bindings for the NDK libraries.  What I'm most excited about is being able to use D to wrap the NDK libraries to create an android experience that's very similar to the Android Java API's, but with native code throughout.
>
> +1 to this. I've been looking forward to getting an Android (either phone or tablet) and writing apps for it. If I can write apps in D, that would simply be awesome. (And you never know, maybe it will be an Android killer app that will make D really take off... ;-))
>
> As far as I know, gdc can already produce ARM code since it uses the gcc backend. All we need now is a nice native D interface to the Android libraries, and I'll be a very very happy man.


Libraries are the easy part. If you can make a build-script that 'just works' for the average man, and perhaps also mingw binaries for the Win users, I think progress in this area will explode almost instantly.


January 28, 2012
On Sat, Jan 28, 2012 at 06:42:14PM +0200, Manu wrote:
> On 28 January 2012 18:19, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:
[...]
> > As far as I know, gdc can already produce ARM code since it uses the gcc backend. All we need now is a nice native D interface to the Android libraries, and I'll be a very very happy man.
> 
> Libraries are the easy part. If you can make a build-script that 'just works' for the average man, and perhaps also mingw binaries for the Win users, I think progress in this area will explode almost instantly.

OK, what do you mean by "just works"? What is needed to in the script? I'll admit I haven't really looked too closely at the Android docs yet, but shouldn't it just be a matter of compiling your D sources with gdc as usual, and then link it with a particular set of libraries?

Well, OK, so you do need to setup an ARM cross-compiler, so you'll need either to build gdc/gcc yourself (ugh) or have someone provide the binaries. What else?


T

-- 
Тише едешь, дальше будешь.
January 28, 2012
On 28 January 2012 19:03, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:

> On Sat, Jan 28, 2012 at 06:42:14PM +0200, Manu wrote:
> > On 28 January 2012 18:19, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:
> [...]
> > > As far as I know, gdc can already produce ARM code since it uses the gcc backend. All we need now is a nice native D interface to the Android libraries, and I'll be a very very happy man.
> >
> > Libraries are the easy part. If you can make a build-script that 'just works' for the average man, and perhaps also mingw binaries for the Win users, I think progress in this area will explode almost instantly.
>
> OK, what do you mean by "just works"? What is needed to in the script? I'll admit I haven't really looked too closely at the Android docs yet, but shouldn't it just be a matter of compiling your D sources with gdc as usual, and then link it with a particular set of libraries?
>

Just build with GDC as usual, and link with the Android NDK libs (we'll obviously need D bindings). They're distributes as binaries with each revision of the Android NDK.


> Well, OK, so you do need to setup an ARM cross-compiler, so you'll need either to build gdc/gcc yourself (ugh) or have someone provide the binaries. What else?


That's enough. A script to fully automate building the Android toolchain,
and ideally, a set of mingw binaries put on the web somewhere.
Google have instructions to build the toolchain on the Android developer
website, they provide a nice set of scripts to do it on linux... It should
just be a matter of patching GDC support into their script and letting it
do its thing.

The rest can be left to the community, ie. druntime, making bindings for the NDK libraries (binaries are provided in the NDK distro). I'm sure that'll take care of its self within short time.


1 2
Next ›   Last »