You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@subversion.apache.org by void pointer <rc...@gmail.com> on 2009/05/01 05:26:16 UTC

libneon & subversion API

I'm currently in the process of building the SVN API and I have a few
questions. Right now I'm building neon 0.26.1, and it fails to compile with
VC9 because neon defines 'vsnprintf' by itself. After commenting out this
macro, it compiles fine. How do you guys eliminate this problem? Do you use
a later version of Neon? Is it save to use version 0.28.X?

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2008182

Re: libneon & subversion API

Posted by void pointer <rc...@gmail.com>.

This is getting really annoying...
The INSTALL file states to use vc6-build.bat on Windows, however this batch
file is completely invalid. It assumes everything is in C:\SVN, which is not
very practical, especially for my case. I need something a little more
flexible and that uses the concept of a current working directory to
determine the location of Subversion. Can I use nmake anywhere? I'm trying
to automate the Subversion build process on Windows. I have a script that
downloads Subversion, extracts it, and needs to build it. I want to minimize
the amount of file modifications I have to do. I would like to just properly
place subversion's dependencies and issue a build and have it work.

Can someone help me out please?

2009/5/1 Robert Dailey <rc...@gmail.com>

> Thanks.
> So if I just wanted the SVN API libraries and headers, would I change
> anything about the way I build subversion 1.6.1? I don't want to have to
> download and compile dependencies that I might not need because I'm not
> using the client.
>
>
> On Fri, May 1, 2009 at 7:53 AM, Arfrever Frehtes Taifersar Arahesis <
> arfrever.fta@gmail.com> wrote:
>
>> 2009-05-01 07:26:16 void pointer napisał(a):
>> > I'm currently in the process of building the SVN API and I have a few
>> > questions. Right now I'm building neon 0.26.1, and it fails to compile
>> with
>> > VC9 because neon defines 'vsnprintf' by itself. After commenting out
>> this
>> > macro, it compiles fine. How do you guys eliminate this problem? Do you
>> use
>> > a later version of Neon? Is it save to use version 0.28.X?
>>
>> Currently we recommend Neon 0.28.4.
>>
>> --
>> Arfrever Frehtes Taifersar Arahesis
>>
>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2018246

Re: libneon & subversion API

Posted by Peter Samuelson <pe...@p12n.org>.

[void pointer]
> So if I just wanted the SVN API libraries and headers, would I change
> anything about the way I build subversion 1.6.1? I don't want to have
> to download and compile dependencies that I might not need because
> I'm not using the client.

The Subversion client is almost entirely in libraries - libsvn_client
at the top.  And, given the need to support the 'file://' protocol (for
which there is no separate server), the client libraries will need most
of the "server" stuff too.  The main thing you don't need is an Apache
server extension development environment.
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/

Re: libneon & subversion API

Posted by void pointer <rc...@gmail.com>.

Thanks.
So if I just wanted the SVN API libraries and headers, would I change
anything about the way I build subversion 1.6.1? I don't want to have to
download and compile dependencies that I might not need because I'm not
using the client.

On Fri, May 1, 2009 at 7:53 AM, Arfrever Frehtes Taifersar Arahesis <
arfrever.fta@gmail.com> wrote:

> 2009-05-01 07:26:16 void pointer napisał(a):
> > I'm currently in the process of building the SVN API and I have a few
> > questions. Right now I'm building neon 0.26.1, and it fails to compile
> with
> > VC9 because neon defines 'vsnprintf' by itself. After commenting out this
> > macro, it compiles fine. How do you guys eliminate this problem? Do you
> use
> > a later version of Neon? Is it save to use version 0.28.X?
>
> Currently we recommend Neon 0.28.4.
>
> --
> Arfrever Frehtes Taifersar Arahesis
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2017491

Re: libneon & subversion API

Posted by Arfrever Frehtes Taifersar Arahesis <Ar...@GMail.Com>.

2009-05-01 07:26:16 void pointer napisał(a):
> I'm currently in the process of building the SVN API and I have a few
> questions. Right now I'm building neon 0.26.1, and it fails to compile with
> VC9 because neon defines 'vsnprintf' by itself. After commenting out this
> macro, it compiles fine. How do you guys eliminate this problem? Do you use
> a later version of Neon? Is it save to use version 0.28.X?

Currently we recommend Neon 0.28.4.

-- 
Arfrever Frehtes Taifersar Arahesis