I would like to use the latest stable/released GDC on Windows, but I find having to build it myself to be annoying and error-prone. This enhancement request is for an automated build script to be developed, that allows creating Windows binaries, such that the GDC developers (as well as a continuous integration server) can automatically produce Windows binaries, and these can then be released to the public. Note: the reason I ask for this to build on a CI server is not really for continuous builds, but just to validate that the build scripts works independently of a particular developers machine.
https://www.bountysource.com/issues/1523615-build-script-and-infrastructure-to-produce-and-release-windows-binaries/bounties
(In reply to comment #0) Building GDC on Windows is not as simple as building it on Linux, there is a series of patch to apply before building ... Here are the scripts used to build the latest available windows versions of GDC : https://bitbucket.org/venix1/mingw-gdc
Those patches aren't essential. The recent mingw builds are evident of that. However I am aware of some essential runtime fixes in those patches (some TLS related) but almost all are unsuitable for inclusion.
(In reply to Iain Buclaw from comment #3) > Those patches aren't essential. The recent mingw builds are evident of that. > However I am aware of some essential runtime fixes in those patches (some > TLS related) but almost all are unsuitable for inclusion. Ian, I didn't understand your point, it seems self contradictory. You say the patches aren't essential, and yet at the same time that there are "some essential runtime fixes in those patches" ?..
(In reply to Bruno Medeiros from comment #4) > (In reply to Iain Buclaw from comment #3) > > Those patches aren't essential. The recent mingw builds are evident of that. > > However I am aware of some essential runtime fixes in those patches (some > > TLS related) but almost all are unsuitable for inclusion. > > Ian, I didn't understand your point, it seems self contradictory. You say > the patches aren't essential, and yet at the same time that there are "some > essential runtime fixes in those patches" ?.. First point was in response to patches needed to apply to build it (compiler patches, build patches). These are not required. The second point was runtime support, which needs some love. For instance, I have implemented EmuTLS in the runtime backend, but it's not yet working with the GC (attempts to hook the data regions into the D GC have so far caused deadlocks). If this were to be fixed, you can build GDC on MinGW with --disable-tls
When you say "runtime support", is that D runtime, or the underlying C runtime?
Am I correct to assume that: ftp://ftp.gdcproject.org/binaries/x86_64-w64-mingw32/x86_64-w64-mingw32_2.066.1_gcc4.9.2_f378f9ab41_20150413.7z is the most recent version for compiling for mingw? In which case its missing on the download page. On the other hand, it looks like the most recent gcc version is actually 6.3? In which case, why is there no recent build for the mingw target?