S
simon22
Guest
Hi - I'm getting an awful lot of unnecessary Visual Studio (2017) rebuilds. Mine is a big Visual C++ project and all these builds are hitting my productivity badly so all help much appreciated.
I can't detect a pattern to the problem. My perception is that sometimes it rebuilds practically every file when I've just changed one .cpp file. Sometimes after a full build, if I hit build again, it will rebuild loads more files. But sometimes it doesn't rebuild anything because it recognises that everything is up-to-date.
When this happened yet again just now (loads of files being rebuilt for no reason that I could see), I stopped the build and clicked on Tools -> Options. I chose Projects and Solutions -> Build and Run and selected Diagnostic in “MSbuild project build log file verbosity”. I then restarted the build, waited a while, and checked the log file. It had more than 10 pages filled with lines like this:
<source file>.cpp will be compiled because it was not found in the tracking log. (TaskId:28)
Anyone got any suggestions what the problem could be?
Simon
Continue reading...
I can't detect a pattern to the problem. My perception is that sometimes it rebuilds practically every file when I've just changed one .cpp file. Sometimes after a full build, if I hit build again, it will rebuild loads more files. But sometimes it doesn't rebuild anything because it recognises that everything is up-to-date.
When this happened yet again just now (loads of files being rebuilt for no reason that I could see), I stopped the build and clicked on Tools -> Options. I chose Projects and Solutions -> Build and Run and selected Diagnostic in “MSbuild project build log file verbosity”. I then restarted the build, waited a while, and checked the log file. It had more than 10 pages filled with lines like this:
<source file>.cpp will be compiled because it was not found in the tracking log. (TaskId:28)
Anyone got any suggestions what the problem could be?
Simon
Continue reading...