Visual studio not detecting that exe is out of date after perforce revert
- by CHaskell2
This is a bit of an odd situation. Here's what's happening.
So, we have a VS2008 project which outputs to a number of files under perforce control. These files have the always writable flag set.
I compile the project in VS, which gives me up to date binaries on my machine. If I then revert those binaries via perforce, I have the version of the binaries that were up on perforce (ie, old ones.)
Despite this, compiling the project again at this point detects no changes and will not remake those binaries. In a way, this makes sense, since none of the code or obj files have changed, but it's not really what I want to happen.
This comes up in an edge case on our automated build server. I can think of tons of different little hacks I could do to fix this, but I'm thinking I could be missing something fundamental here.
The actual build process uses the Unreal build tool, so there is a bit of magic going on behind the scenes that I'm not entirely familiar with too.
Edit: This is a C/C++ project, forgot to mention that.
