killer App for D? (was: State of D on iOS/Android)

Johannes Pfau spam at example.com
Sun Jan 29 03:10:29 PST 2012


Manu wrote:

> On 29 January 2012 07:42, Andrew Wiley <wiley.andrew.j at gmail.com> wrote:
> 
>> On Sat, Jan 28, 2012 at 9:11 PM, Nick Sabalausky <a at a.a> wrote:
>> > "Alex Rønne Petersen" <xtzgzorex at gmail.com> wrote in message
>> > news:jg29bs$2dm8$1 at digitalmars.com...
>> >>
>> >> Yes, D on Android would be great.
>> >>
>> >> In fact, D already runs on Android if you do some tweaks to the GDC
>> build.
>> >> I've managed to get D apps running on both a Galaxy Tab 10.1 and an
>> Efika
>> >> MX.
>> >>
>> >
>> > CAN I HAZ DETAILS PLZ?
>> > KTHNXBYE
>> >
>>
>> I can't speak to Android, but I know that building GDC on ARM is
>> fairly routine these days. Make sure to build with
>> DFLAGS="-fno-section-anchors" in the environment, but otherwise,
>> follow the normal build instructions.
>> I would assume the same would apply when building a cross compiler for
>> ARM (although the normal build instructions are just a bit harder).
>>
> 
> Am I the only one that finds it annoying that any dev that wants to use D
> seems to have to A) use linux, and B) know how to build GCC on their own?
> How many people does this turn away?
Some linux distributions ship gdc already, also following the gdc build 
instructions isn't hard. Once GDC is part of GCC that problem is solved 
anyway.
This is of course different for cross compilers, but Iains time is limited 
and few people are aware of the gcc/gdc/dmd internals, so other 
architectures are not really supported in gdc. For example, 
https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-arm 
needs to be fixed before we could call GDC on ARM alpha state. I might have 
another look at that issue in ~2 months, but without knowledge of gdc/gcc 
internals, fixing it isn't easy.
  
> 
> Build scripts and mingw binaries plz! Then devs can actually get to work
> and start writing software. 90% of my time spent with D involves trying to
> fuck around with msys/cygwin environments, trying to build toolchains, and
> having an endless stream of related problems. Complete waste of my time,
> and loss of community contribution.

Using "-fno-section-anchors" is only a workaround to get gdc working on ARM. 
It's never been documented, it's only mentioned in bug #120 and using a gdc 
built like that is in no way supported. Doing stuff like that isn't really 
supposed to be easy.


More information about the Digitalmars-d mailing list