[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: D.J. Heap <djheap_at_gmail.com>
Date: 2006-01-07 17:44:33 CET

On 1/5/06, Tim Van Holder <tim.van.holder@telenet.be> wrote:
> 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.


> I only have 2 reasons for not using swig:
> - I have absolutely no experience with swig
> - from what I can tell, it maps everything directly to static functions
> of a class, with no name changes. This makes it fit in very badly
> with other .NET class libraries (naming conventions, etc.)
> But I'll look into it.

I'm not a swig expert, but I think the bindings come in two layers --
a low level layer directly from swig that just wraps functions and
stuff, and then a (partially?) hand-crafted higher level layer that is
customized more to the language. At least, that is my understanding
based on conversations I've seen here.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 7 17:45: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.