On Sun, Apr 14, 2013 at 1:48 PM, Ben Reser <ben_at_reser.org> wrote:
> On Sun, Apr 14, 2013 at 10:24 AM, Branko Čibej <brane_at_wandisco.com> wrote:
>> Have you seen:
>>
>> https://github.com/brainy/subversion-windeps
>
> No I had not. I'd known that you'd done some work but didn't realize
> you'd gotten so far.
>
> I'm not sure which approach is better. I see that you've given
> yourself standard Unix tools. I went with Perl since I could get away
> without having them. I was also trying to keep the required
> dependencies to use it down to a minimum.
I am not sure where he keeps it, but Bert has an msbuild script that
does everything as well. I believe the only thing you needed to have
installed was a recent Windows SDK and it used the compiler from that.
I do not recall how he handled different bindings, but I recall the
script could even build Python from source so you did not need any of
it installed.
For SVN Edge we used his script as a starting point and then modified
it so that we could use pre-built zips of things we do not want to
rebuild every time like Perl/Python:
https://ctf.open.collab.net/integration/viewvc/viewvc.cgi/trunk/svn-server/windows/?root=svnedge&system=exsy1005
I know we are using VS 2008 and not the SDK. I do not recall if that
is because we ran into an issue where we needed it or not.
I think these scripts are useful for people doing packaging, but I am
not sure how good they are if you want to hack on Subversion using
Visual Studio where you want to use the debugger and have incremental
rebuilds etc. I think those are the kinds of docs that would be
needed.
TortoiseSVN build also uses a lot of the same concepts:
https://code.google.com/p/tortoisesvn/source/browse/trunk/build.txt
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2013-04-14 20:19:26 CEST