Vladimir Prus wrote:
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)?
Yes, indeed I tried it again to be sure. I unpack the release boost archive boost_1_43_0.tar.bz2, and build the boost libraries, all from a makefile, as a custom build step in my VS 2008 project, and boost compiles just fine. I unpack the archive with the trunk version of boost (at least as the trunk was a few days ago when I checked it out from svn) and build it in my project. Then I see the error in the Output window in VS 2008, and compilation of my project stops as the custom build step returned an error :(. You have the trimmed build logs attached. You can see a line: 1>libs\regex\build\has_icu_test.cpp(12) : fatal error C1083: Cannot open include file: 'unicode/uversion.h': No such file or directory in the second build log (with the trunk version), after boostrapping bjam, but not in the first build log (with the release tarball). (including the entire build logs would make the message too large for this mailing list /newsgroup) Thank you, Timothy Madden