Peter Steele wrote:
I'd vote against such a habit for a number of reasons:
1) You may be compiling with different versions of the compiler
That's not a problem in our case...
2) You may be compiling with different compiler switches (debug vs.
production)
That's well controlled in our case; not a problem.
3) What happens if you support multiple platforms (someday).
Ultimately no different than Release vs. Debug builds; we'd just
use different directories for different platforms...
All of these isssues can be worked around, certainly, but why
add the extra
hassle to your development cycle? Is your project so large
and VC++ so slow
that the extra compile time makes a big difference?
We're at 200000+ and counting. It will get a lot bigger and developers are
already complaining about how much time is being lost in long compiles.
We're on tight deadlines and every minute counts...
Snort. We compile 3.4 million lines of source into 115 executable images.
Make sure your makefiles (or projects) are doing the right thing. If
they're not, get Jam/MR from Perforce and do it right.
3 messages in com.perforce.perforce-user[p4] RE: Do *you* source control your...