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

Re: Using svn.exe with nightly build

From: Dave Lawrence <dlawrence_at_ad-holdings.co.uk>
Date: Thu, 27 Nov 2008 18:23:37 +0000

Stefan Küng wrote:
> Dave Lawrence wrote:
>> Has the procedure for doing this changed?
>>
>> I understood that I should copy svn.exe from your nightly builds page
>> into my tortoisesvn bin directory then fix my path to ensure that's the
>> one it uses.
>>
>> But now it complains about various missing dlls eg libsvn_client-1.dll.
>> I notice that isn't there is the installation, presumably you link it
>> statically.
>>
>> Am I doing something wrong or is this svn.exe not usuable at the moment.
>
> Make sure that you really are using the svn.exe from our nightly build
> server - that one doesn't require any libsvn_* dlls at all but links
> everything statically.
> I just downloaded the svn.exe from the server to make sure it was built
> correctly, and I can verify that it doesn't require additional dlls
> (apart from those in the TSVN bin folder).
>
Seems windows was calling multiple copies of svn.exe? Is this possible?

I'd removed the collabnet installation from my path. If I did "svn
--version" I first got the errors, then got the version info, which
definately indicated it was from your nightly build.

So I removed the collabnet install completely, and now it's fine.

I can only imagine that something in the registry made it reference the
collabnet svn, which then couldn't find the dll's (due to lack of path)
and so windows carried on searching and found your svn and decided to
run that instead. Does it do really things like that?

Thanks for your help.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-11-27 19:24:01 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.