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

Re: Recommended build method for SVN?

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Mon, 01 Dec 2008 17:38:30 +0100

Ben Collins-Sussman wrote:
> Do you really need to be rebuilding svn trunk code daily, in order for
> your own project to make progress? If not, why not just have *one*
> person (you?) build trunk every month or so, and distribute the
> libraries via svn.
> I can't believe I'm recommending this, since I've spent years telling
> people to only put 'non-derivable' stuff (i.e. code) into version
> control... but building svn on Windows is Really Really Hard.

I'd say it depends :)
Building svn on Windows with the recommended python build scripts
requires a lot of manual steps, because the dependencies (e.g., apr) are
not built with those scripts and have to be built separately.

But I've created some NAnt scripts for TSVN which do all this in one
step: build all the dependencies (apr, openssl, ...) and the Subversion
libs by simply executing 'nant Subversion'. The only thing those NAnt
scripts require is that all libraries (source code) are stored in a
defined location (i.e., there's no way to tell the script where the
sources are: it assumes the sources are where it expects them to be).

If there's a demand for a more Subversion-only NAnt script, I could
create one.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net

Received on 2008-12-01 17:39:00 CET

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.