Re: Re: [gsoc] We need to design "commit from multiple working copies"

On Fri, May 22, 2009 at 10:01 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Fri, May 22, 2009 at 03:06:41PM +0800, HuiHuang wrote:
>>    Hey Stefan,
>>
>>    would you mind to tell me what IDE you use to develop this project? and
>>    how do you ususlly compile, build and test it? The OS I use is Windows XP.
>
> I'm afraid I don't know much about Windows at all, so I cannot
> help you :(  I use the vim editor to edit the source code, and
> compile Subversion using make. It's not really an IDE, but it
> works really well for me :)

You need Visual Studio, at least the Express version.

I just rebuilt my laptop with Vista, so I remember the things I did.

The build system also needs Perl and Python installed, so I install
those first. I just get the free versions provided from ActiveState
and let the install add to PATH etc. If you want to compile Java
bindings, you also need Java installed. To build Apache and
mod_dav_svn, you need to have "awk.exe" on the PATH.

Once I've done those things, I installed VS 2008. This includes a
recent enough Windows Platform SDK, so you do not need to install
that. If you have an older version of VS, you may need to install the
SDK.

I then downloaded OpenSSL and built it. It has a readme with instructions.

I then downloaded Apache 2.2.11 source zip file for Windows and built
it using Apache instructions on their web site. Since I just want to
be able to build and test mod_dav_svn, I do not bother trying to build
mod_deflate or SSL support.

The next thing I do is checkout SVN trunk. I also downloaded the
latest "deps" zip file for 1.6.2 to get Neon, Serf, Zlib and SQLite.
I unzip this and copied those into the checkout of trunk. I do not
copy the APR from deps because I will use the version I built with
Apache server.

I should have mentioned I do my builds from command prompt. Visual
Studio installs a shortcut that lets you open a command prompt where
it has set all the environment variables like LIB and INCLUDE for
building. I always use this so that I do not have to set those.

From the root of the Subversion checkout I run this:

python gen-make.py -t vcproj --vsnet-version=2008
--with-openssl=..\openssl-0.9.8k --with-zlib=zlib
--with-httpd=..\httpd-2.2.11 --with-apr=..\httpd-2.2.11\srclib\apr
--with-apr-util=..\httpd-2.2.11\srclib\apr-util --with-neon=neon
--with-serf=serf

This command generates the Visual Studio 2008 project files for
building. I did not bother to build BerkleyDB support.

To build Subversion, I then run this:

devenv subversion_vcnet.sln /build "Release" /project "__ALL_TESTS__"

To run the tests, I then run this:

python win-tests.py -f fsfs -c -r -v

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2352910