[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: VS2005 configuration/build issues (was Re: Minor issue with VS.NET solution file generation (trunk))

From: Tim Van Holder <tim.van.holder_at_telenet.be>
Date: 2006-01-07 21:48:20 CET

D.J. Heap wrote:
> On 1/5/06, Tim Van Holder <tim.van.holder@telenet.be> wrote:
> [snip]
>
>>That's what I thought too - apr.h even duplicates the #define and
>>there's no compiler warning from that, only for the first one.
>>As it turns out, the /D command line option of the compiler is
>>documented as defaulting to a value of 1.
>>So the predefinition in the project file is
>> #define FOO 1
>>while apr.h uses
>> #define FOO
>>so the definition isn't identical.
>>Perhaps using _CRT_SECURE_NO_DEPRECATE= (with the added '=') in the list
>>of additional preprocessor defines of the subversion projects also
>>makes the warnings go away - I'll check when I get home from work
>>tonight.
>
> Thanks.

Putting "_CRT_SECURE_NO_DEPRECATE=;_CRT_NONSTDC_NO_DEPRECATE="
in the preprocessor settings for apr does not avoid the "macro
redefinition" warning. So either the svn config process needs to
exclude them from the apr projects it generates, or the apr folks
need to put "#if !defined()" guards around their definition.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 7 21:51:10 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.