November 29Re: dud: A dub replacement
Posted in reply to Adam D. Ruppe
On Thursday, 28 November 2019 at 14:06:39 UTC, Adam D. Ruppe wrote: > On Thursday, 28 November 2019 at 13:10:44 UTC, Atila Neves wrote: >> This is the done already by reggae. Unfortunately, since every D module is effectively a header, the number of files that need to be recompiled is usually large, despite the fact that for most changes the recompilation isn't actually necessary. > > Do you think it might work if it did dmd -H and make the auto-generated .di file and then did a content-based change detection on them for recompiling dependencies? Probably. In fact, I had a plan to do exactly that and measure to see what the difference was. I just haven't gotten around to doing it yet. > It'd prolly still do more work than it has to, but seeing .d changed, rebuild .di, if .di changed, rebuild other stuff might just avoid full rebuilds upon just simple function body changes. That was my idea as well.
6 days agoRe: dud: A dub replacement
Posted in reply to H. S. Teoh
On Monday, 25 November 2019 at 18:28:55 UTC, H. S. Teoh wrote: > - lack of support for build-time code generation (i.e., build a subset > of files into an executable, run the executable to generate .d files, > compile output .d files plus other existing .d files into final > product). I am doing exactly that. It can be done through preGenerateCommands, calling either a secondary build script or nested dub project, optionally using excludedSourceFiles. The only reason it doesn’t work well is because of https://github.com/dlang/dub/issues/1474. But there are workarounds, and a poc fix. Bastiaan.
Copyright © 1999-2018 by the D Language Foundation