John Maddock wrote:
This happens on the trunk version of boost, from svn, the release tarball indeed does not display the message. Actually this only happens when building boost as a custom build step in my project's build process, from Visual Studio 2008. Building from the command line does not display the message. Which might make sense, since the message does not follow output redirection anyway.
Maybe cl.exe somehow feels it is invoked from a subprocess of VS, or sees some environment variables, and knows how to output the message ?
Hmmm, no idea.... apparently you should never see the error messages - it's redirected to a log file. So it sounds like this could be a Visual Studio issue...
Just to clarify one detail above this thread -- is this issue happening only with trunk, and not with release (when both are built inside VS)? - Volodya