On 02.09.2010 14:15, Vladimir Prus wrote:
Timothy Madden wrote:
On 8/16/2010 4:30 PM, Ilya Sokolov wrote:
Timothy Madden wrote:
John Maddock wrote:
I get the following message when compiling boost from trunk:
1>Building the Boost C++ Libraries. 1>has_icu_test.cpp 1>libs\regex\build\has_icu_test.cpp(12) : fatal error C1083: Cannot open include file: 'unicode/uversion.h': No such file or directory 1>Performing configuration checks 1> - has_icu builds : no
Although the build succeeds (as this is a test) Visual Studio recognizes the error in the output and stops compiling the project and reports the build as failed.
Is there a way for me to suppress this message ? Or this test ?
Attempting to redirect output with&>outfile.txt do not work as the error messages still gets output in VS. Are there and build options to disable this check ?
No not at present, unless they're present in Boost.Build somewhere. Actually I *never* see this error message just the
Performing configuration checks - has_icu builds : no
part. I'm not sure what controls this, but I'll try and find out.
Please, it will help me prevent the build from stopping in VS.
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 ?
Yes, it's watching for VS_UNICODE_OUTPUT environment variable. http://connect.microsoft.com/MSDNProductFeedbackCenterRedirect.aspx?pfcId=FD...
Excelent !
I was still getting this problem with boost 1.44, so thank you for this information. Could boost better documented this somewhere ?
Better yet, could the regex build process start by unsetting this variable ? Should I report this somewhere ?
Do you always get those messages, or only when building a fresh tree for the first time?
The project pre-build event that I set up unpacks and compiles a boost release archive, that I place on source control as part of the project files, so I always compile a fresh tree. Sorry I can not answer your question. When a new boost version is released, I change the archive in the project source directory, and the Makefile deletes the previous version(s) and compiles the new one. Timothy Madden