Re: [Boost-users] How to disable the check or the error after checking for ICU (for regex lib) when building boost ?

Subject: Re: [Boost-users] How to disable the check or the error after checking for ICU (for regex lib) when building boost ?
From: Ilya Sokolov (ilyasokol_at_[hidden])
Date: 2010-08-16 09:30:33

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=FDBK33583

> Thank you,
> Timothy Madden