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

RE: Subversion 0.27

From: Lübbe Onken <L.Onken_at_rac.de>
Date: 2003-08-20 09:53:07 CEST

Hi Folks,

I solved problem two (compiling neon with ssl support) without having to
compile openssl and to install perl before being able to do so.

Here's the recipe:
1) Grab a binary distribution of openssl, that contains the header files
plus libeay32.lib and ssleay32.lib. That's enough, if you want to build with
statically linked OpenSSL support.
1a) If you want dynamically linked OpenSSL support, you need libeay32.dll
and ssleay32.dll as well.

2) I've got the following directory layout:
\source\svn
\source\openssl
\source\zlib

3) Place the header files in \source\openssl\inc32\openssl

4a) if you want statically linked OpenSSL support, place the lib files in
\source\openssl\out32
4b) if you want dynamically linked OpenSSL support, place the lib files in
\source\openssl\out32dll and make sure that libeay32.dll and ssleay32.dll
are in your path (e.g. c:\winnt\system32)

5) change to \source\svn and run "gen-make.py --with-openssl=..\openssl
--with-zlib=..\zlib -t whatever"
5a) if you want statically linked OpenSSL support, edit
build\win32\build_neon.bat, look for:
"@rem OpenSSL support" and add the following line:
"set OPENSSL_STATIC=yes directly" directly after it

6) make a clean build of neon and rebuild svn.

both dynamically and statically linked svn clients worked fine on my
machine.

Cheers
- Lübbe

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 20 09:58:07 2003

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

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