https://issues.dlang.org/show_bug.cgi?id=13517
--- Comment #20 from Ketmar Dark <[email protected]> --- (In reply to Steven Schveighoffer from comment #17) so it's not a "side effect", .di file has to be explicitly asked. > > and why build tool doesn't know about '.di'? > I mean, the build tool knows it only as a dependency, not as a target. It > has no idea how to build the .di file. The .di file is built as a side > effect of building the .o file. no, it's not a "side effect". and build tool doesn't know how to build .o from .d too. one must provide the rule which builds .o from .d. one must provide the rule which builds .di from .d. simple and easy. > But as I said, you would need to ensure the project that builds the .di file > cannot depend on the .di file, because it doesn't know how to build them, it > just does so as a side effect. if project uses generated files that eventually needs regeneration and it's build system doesn't know about that files, this project's build scripts are foobared. that is exactly the mess that will lead to complete disaster sooner or later. --
