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

Re: svn commit: rev 5638 - in trunk: . subversion/bindings/com subversion/clients/cmdline subversion/libsvn_client subversion/libsvn_delta subversion/libsvn_diff subversion/libsvn_fs subversion/libsvn_ra subversion/libsvn_ra_dav subversion/libsvn_ra_local

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-04-16 20:24:46 CEST

On Wed, Apr 16, 2003 at 08:02:53AM +0100, Tim Kemp wrote:
> And how do you expect us Win32 peeps to build now, I suspect that you
> have forgotten to check the dsw in :o)
> And I suppose that I need python now too,
> Any thing else????

The .dsw is generated along with the .dsp files.

As before, you can do one of two things:

1) pull from version control directly and use autogen.sh. this will require
   Python for the gen-make steps in autogen (we've always required Python
   for people who work from source control).
   [ but see below ]

2) use a source tarball/ZIP. the dsp and dsw files will be present as part
   of the release procedure.

Note that the system requires an "apr" and "apr-util" subdir from the trunk,
which is the same as before. Since that isn't the case for everybody who
runs autogen.sh, I could not (for now) run the DSP gen-make process
automatically from autogen.sh. (hmm; but I don't supposed you're running
autogen.sh on Windows anyways :-).

Thus, the steps to build from source control are:

1) grab source
2) gen-make.py -t dsp
3) open the .dsw

So one more step if you build from source control. The release process
handles step (2) automatically.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 16 20:25:14 2003

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.