William A. Rowe, Jr. wrote:
Martin Sebor wrote:
Could you help me understand what you mean by "being able to unwind
build problems with wrong flags, etc?" The ability to debug compiler
and linker command line options? If that's it, what makes these
automation interfaces unhelpful in this regard? (I'm not very
familiar with VisualStudio automation).
What I meant was that to most of us, looking at the build command line
commands from a makefile, which we can get by exporting the .dsp/.dsw
flavor to .mak format, is usually quite helpful. The coolaid comment
was that MS is fantastic for wrapping up the build environment into
something that 'just works', but that you can't really inspect as it
works, at least in my experience.
Aha, I think I understand.
"Hiding the ugly details from the user" is the modus operandi.
I'm not a fan of the approach :)
I agree. I also don't like the IDE hiding the command line. I like
seeing the exact command line for each source file just as it would
be issued by make, even if it's the same as for all the other sources.
Martin
