After too many days of frustration to be able to count, I finally
discovered what works for our builds: the debug build of 64-bit
dmd on Windows.
When I build the release version from the Makefile or use digger,
it produces a dmd binary that crashes randomly (bad enough) or
compiles executabl
On Wednesday, 13 June 2018 at 17:13:09 UTC, Atila Neves wrote:
This post is both a warning to the intrepid D programmers out
there who'd rather not hit a 4GB RAM limit for no reason on
Windows and also a question to see if anybody has been able to
use 64-bit dmd on Windows like intended.
Wor
On Wednesday, 13 June 2018 at 17:13:09 UTC, Atila Neves wrote:
After too many days of frustration to be able to count, I
finally discovered what works for our builds: the debug build
of 64-bit dmd on Windows.
When I build the release version from the Makefile or use
digger, it produces a dmd
On Wednesday, 13 June 2018 at 17:30:34 UTC, Vladimir Panteleev
wrote:
On Wednesday, 13 June 2018 at 17:13:09 UTC, Atila Neves wrote:
After too many days of frustration to be able to count, I
finally discovered what works for our builds: the debug build
of 64-bit dmd on Windows.
When I build t
On Wednesday, 13 June 2018 at 17:30:34 UTC, Vladimir Panteleev
wrote:
On Wednesday, 13 June 2018 at 17:13:09 UTC, Atila Neves wrote:
[...]
I've used 64-bit DMD exclusively while Windows was my primary
OS, but that was a few years ago.
[...]
Reviewing the dustmite documentation, I'm not su
On Wednesday, 13 June 2018 at 17:54:29 UTC, Atila Neves wrote:
Reviewing the dustmite documentation, I'm not sure how the
reduction would work when the build that's broken is a dub one
that uses local packages.
You will need to either reduce the test to a command which does
not involve dub (i
