Bruce Atherton wrote:
> At 05:13 AM 1/31/2002 -0500, Geisser, Oliver wrote:
>
>> I think it would be helpfull to mention that the "INSTALL" document
>> describes the install/build requirements for Linux/Unix.
>>
>> The windows requirements are a little bit different.
>
>
> This is a good point and I will make that change. In addition, I'm
> going to take all the building information out of HACKING (which
> includes instructions on building for Win32 platforms) and integrate
> it into INSTALL, as well as adding instructions for bootstrapping from
> the Windows ZIP file.
That'd be great, thanks!
> My problem is that I haven't compiled Subversion under Windows and I
> haven't noticed (or at least haven't retained) much in the way of
> instructions from the mailing list.
>
> For example, how is getdate.c generated on a Windows platform? Do you
> require a Cygwin or Mingw or DJGPP version of yacc/bison in order to
> compile?
If those were required, they'd be listed HACKING. :-)
There's a pre-build getdate.cw that gets copied to getdate.c on Windows.
> For bootstrapping, what about diff and patch. The README included with
> the precompiled windows client suggests that they have to be stored in
> "C:\Program Files\cygnus\cygwin\bin", yet I have cygwin installed in a
> different directory and it seems to work. Do they just have to be on
> the PATH? Does the libdb DLL or the svn EXE?
That's interesting. The paths to diff and patch are hard-coded in
svn_private_config.hw (and can of course be changed for your setup). I
wonder if the diff- and patch- spawining code hasn't changed to use PATH
... it hasn't. Weird. Are you sure you actually called diff and/or
patch? IIRC they only get used for merging local changes during update,
si you might not have hit that code yet.
The Berkeley DB dll has to be either in the PATH or in the same
directory as svn.exe
svn.exe doesn't have to be in the PATH, of course -- but it's easier to
invoke it if it is. :-)
> The fact that the Neon and Berkeley DB libraries are precompiled
> suggests that getting them to compile in the first place is a pain.
> Should there be instructions about how to do that or just a blanket
> recommendation that people use the downloaded version? What else needs
> to change in the description currently in HACKING?
I couldn't integrate neon into the Windows build until the recent 0.18.5
release, which includes all of my patches for the Neon build system (can
use zlib and OpenSSL, yeah!).
Berkeley DB has its own build instructions. I just uploaded the binaries
as a convenience, because the Windows build system requires the includes
and libs in a specific location. There's no reason why you couldnt build
Berkeley DB and put the files in the right places yourself.
> I'd appreciate any feedback on this before I submit another patch, so
> that the documentation can at least approximate reality.
I'd appreciate any and all patches to the Win32 build docs. I'ts pretty
hard to write good user docs if you set up the system yourself; I
usually forget to mention one or two crucial steps that I take for
granted. :-(
>> For example on windows there is no libtool or autoconf needed
>> but you need Visual Studio.
>
>
> Don't you mean Visual C++ 6.0 or greater? I haven't installed it
> myself, but I assume that it includes Visual Studio. If it doesn't,
> can you still use the project files?
Yep, that's right. "Visual Studio" can bean VB, FoxPro, Java and even C#
these days, not to mention Python and Perl from ActiveState. MSVC++6.x
is right.
And I hope that someday soon we'll be able to add instructions for
installing mod_dav_svn into Apache on Win32. Hold your breath ...
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:03 2006