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

Windows build system: build or not external libraries automatically

From: Ivan Zhakov <chemodax_at_gmail.com>
Date: 2007-04-02 22:05:43 CEST

Everybody knows that Subversion windows build system is messy. One of
reason is external libraries that we trying to build automatically
during Subversion build.
Actually we have inconsistency: some libraries build automatically and
some doesn't. Also for some libraries we provide precompiled binaries
and for some don't.

For present time status is:
- apr, apr-util, apr-iconv build automatically. No precompiled binaries.
- neon builds automatically.
- serf builds automatically
- zlib builds automatically
- Berkley DB has to build manually, but we provide precompiled binaries.
- sqlite has to build manually
- openssl has to build manually (actually we don't use openssl
directly, we use it
  through neon library)
- gettext has to manually, we provide patched precompiled binaries
- libsasl -- I don't know

From my experience, most problems, that I had with building
Subversion, caused by external libraries.

I propose to remove automatic building of external libraries from
Subversion windows build system.
It better for us to focus on:
- checking for problems in gen-make.py
- improve building process of some libraries
- provide precompiled binaries of libraries, like we did for bdb
- provide batch scripts for building external libraries
But don't build external libraries using generated project files from
Visual Studio.

Ivan Zhakov
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 2 22:06:24 2007

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.