On Thu, Nov 8, 2018 at 12:55 AM Joakim via Digitalmars-d-announce <[email protected]> wrote: > > On Thursday, 8 November 2018 at 08:29:28 UTC, Manu wrote: > > On Thu, Nov 8, 2018 at 12:10 AM Joakim via > > Digitalmars-d-announce <[email protected]> > > wrote: > >> > >> On Thursday, 8 November 2018 at 07:54:56 UTC, Manu wrote: > > > > I didn't configure the build infrastructure! > > Maybe you can? I have no experience with VS, but surely it has > some equivalent of ninja -j5?
msbuild does parallel builds quite effectively. I expect it perceives a dependency between jobs which cause it to serialise. Maybe there's a legit dependency, or maybe the msbuild script has a problem? Either way, it's not acceptable. I would log this is maximum priority bug. (https://issues.dlang.org/show_bug.cgi?id=19377) > >> > And all builds are release builds... what good is a debug > >> > build? DMD > >> > is unbelievably slow in debug. If it wasn't already slow > >> > enough... if > >> > I try and build with a debug build, it takes closer to 5 > >> > minutes. > >> > > >> > I suspect one part of the problem is that DMD used to be > >> > built with a C compiler, and now it's built with DMD... it > >> > really should be built with LDC at least? > >> > >> Could be part of the problem on Windows, dunno. > > > > Well... ffs... people need to care about this! >_< > > I agree that the official release of DMD for Windows should be > faster, and we should be building it with ldc... if that's the > problem. I think it's a combination of problems, and primary problem being criminal negligence!
