GtkD Blog Now Up and Running

Petar Petar
Fri Feb 1 07:43:23 UTC 2019


On Thursday, 31 January 2019 at 20:33:43 UTC, Ron Tarrant wrote:
> On Wednesday, 30 January 2019 at 21:21:24 UTC, Mike Wey wrote:
>
>> This is whats going on: 
>> https://issues.dlang.org/show_bug.cgi?id=15418
>>
>> To work around this you can either build things with 
>> "--arch=x86mscoff" or tell dub not to build the debug version 
>> with "--build=plain".
>
> Ah! Thanks, Mike. Does the lack of an answer to the last 
> question there mean that this is an on-going issue?

The issue is unrelated to dub. It only has to do with object 
format and linker that dmd uses on Windows by default.
This issue is perhaps the reason why you had to use the -m64 dmd 
flag in your first post. If you don't specify the target arch on 
Windows - the -mXX flag for dmd, or the --arch=YYY flag for dub - 
the default is going to be -m32 and --arch=x86 respectively.

So, assuming you have the MSVC C++ toolchain installed, just 
build with dub by specifying either the --arch=x86_mscoff or 
--arch=x86_64 flags.
But no one should ever need to modify their dmd installation, in 
order to use gtkd.



More information about the Digitalmars-d-announce mailing list