30890 2009-10-28 16:58:32 -0700 Windows build: changes in header files do not always trigger correct rebuild. 2010-11-10 04:54:10 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) PC Windows Vista NEW P2 Normal --- 1 dimich webkit-unassigned aroben mrowe sfalken oldest_to_newest 158776 0 dimich 2009-10-28 16:58:32 -0700 Example: recent change to JavaScriptCore/wtf/MessageQueue.h broke the Windows build because MessageQueue.h is not included anywhere in JavaScriptCore so the project JavaScriptCore was not build. this project has "post-build step" which make copy of header files to the build directory from where the subsequent WebCore build includes JSC headers. As a result, the stale header of MessageQueue.h was used and build broke. Changing a cpp file from wtf caused recompile of JavaScriptCore and updated the headers. I'm not sure what the right fix for this is. 307297 1 aroben 2010-11-10 04:54:10 -0800 The right fix is to move all header copying into a Makefile-based project (like JavaScriptCoreGenerated). Makefile-based projects run on every build regardless of whether any .cpp files changed.