On Friday, 10 January 2014 at 20:30:34 UTC, John Colvin wrote:
I don't think i've ever run anything using unity before. Also,
I'm on an Intel AZ-210 so it's x86-android, which probably
means quite a few untested corner-cases for unity and other
libs.
Wow, one of the mythical Android/x86
The bug turned out to be me not using importPaths correctly,
so my bad.
On Friday, 10 January 2014 at 18:48:11 UTC, Atila Neves wrote:
I finally got around to cloning the git repo and trying the
latest dub and how dub test would work.
1st of all there is a bug, should I also add it to the
On 1/9/2014 10:38 AM, anthonyb wrote:
On Thursday, 9 January 2014 at 17:56:46 UTC, Adam D. Ruppe wrote:
On Thursday, 9 January 2014 at 16:15:23 UTC, bearophile wrote:
Is QtD not good enough?
When I tried it, a while ago, it was completely unusable - random
runtime crashes.
Which i a real
Hi everyone,
Just wrote annotated v1.2.7 of Mono-D:
http://mono-d.alexanderbothe.com/completion-ldc2-compatibility-dub-fix-v1-2-7
I'm too lazy to mention every part of it again over here - if
there are questions: Here, in #d.mono-d, on the blog, on github -
you know the usual places where to
On Sunday, 12 January 2014 at 23:40:33 UTC, Alexander Bothe wrote:
Hi everyone,
Just wrote annotated v1.2.7 of Mono-D:
http://mono-d.alexanderbothe.com/completion-ldc2-compatibility-dub-fix-v1-2-7
I'm too lazy to mention every part of it again over here - if
there are questions: Here, in
On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote:
On Sunday, 12 January 2014 at 23:40:33 UTC, Alexander Bothe
wrote:
Hi everyone,
Just wrote annotated v1.2.7 of Mono-D:
http://mono-d.alexanderbothe.com/completion-ldc2-compatibility-dub-fix-v1-2-7
I'm too lazy to mention every part of