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 <rcdailey_at_gmail.com>
> 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_at_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
>> > VC9 because neon defines 'vsnprintf' by itself. After commenting out
>> > macro, it compiles fine. How do you guys eliminate this problem? Do you
>> > 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
Received on 2009-05-01 21:07:40 CEST