build log of sample app after no file changes where made
text/html
1745
Comments
Comment #0 by ben.stembridge — 2016-10-17T02:14:34Z
Regardless of whether files have changed im always forced to rebuild.
example output:
Building Win32\Debug\ConsoleApp1.exe...
Win32\Debug\ConsoleApp1.exe not up to date: link dependency file b:\ConsoleApp1\Win32\Debug\ConsoleApp1.lnkdep does not exist
Notice that the link file is named .lnkdep and it does not exist in the project directory. But there is a .dep file in the folder. Could the tool be looking for the wrong extension?
It seems this issue was reported before and was listed as fixed in v0.3.40-beta1:
http://forum.dlang.org/post/[email protected]
I had originally started with 0.3.43 and also tried 0.3.44.
This is win7 64bit with VS 2005, Im not sure if its because of the old version of VS but everything else seems to work ok.
Comment #1 by r.sagitario — 2016-10-17T06:53:09Z
I suspect VS005 does not come with the file tracking utilities of later versions, so Visual D falls back to it's own implementation. Not sure what's wrong with it in your case, though. Could you please attach the build log from the output folder?
As a workaround you can disable linker dependency tracking in the global options page: Tools->Options->Projects and Solutions->Visual D Settings->Monitor linker dependencies.
Comment #2 by ben.stembridge — 2016-10-17T10:46:35Z
Created attachment 1620
build log of sample app after no file changes where made
I notice that pipedmd.exe has -deps Win32\Debug\ConsoleApp1.lnkdep
When unchecking "monitor link dependencies" as suggested that part of the build is gone and only builds when the main source file has changed as expected.
Comment #3 by ben.stembridge — 2016-10-17T10:57:43Z
Disabling "monitor link dependencies" seems to be a good enough workaround in my case. I dont have any complex link dependencies and the project detects source file changes and rebuilds anyway.
Comment #4 by r.sagitario — 2017-06-05T17:26:51Z
The newest version https://github.com/dlang/visuald/releases/tag/v0.45.0-beta1 uses generic dependency tracking for the compiler, too. So you might get hit by this issue again with the next version.
If you are still using VS2005, I'd recomment installing some MS package containing the file access tracker.exe. It should be part of anything containing MSBuild, e.g. .NET SDK, Build Tools or other SDKs.
Comment #5 by r.sagitario — 2018-06-10T09:08:59Z
Sorry, but still actively supporting VS2005 is such a rare case that it doesn't seem worth the effort.