On Sat, 09 May 2015 21:09:33 -0400, Ali Çehreli <acehr...@yahoo.com> wrote:
On 05/09/2015 07:01 AM, bitwise wrote:
./main.d
./pack/foo.d
./pack/sub/bar.d
dmd main.d pack/foo.d pack/sub/bar.d -ofTest -H
This dumps all the *.di files into the output directory ignoring the
directory structure.
Is there some rational for it being this way?
Wouldn't it be much more useful if directories were preserved?
Bit
As far as I know, every other similar tool works the same way:
$ gcc -c foo/foo.c
foo.o is outputted to the current directory.
The common solution that I know is to use makefiles to manage file
dependencies. For example, the rule for .di specifies the file that it
depends on (the .d corresponding to that .di) and 'make' handles it
automatically.
Ali
I'm not sure I understand what you mean, but my point is, that as is, this
feature of DMD is broken.
If people are successfully using dmd -H right now, they must not be using
packages, or their 'package.di' files would be overwritten. So I'm
wondering if I should do a PR to fix this.
Bit
