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

Re: Attn: Windows Devs -- Need to add missing sqlite build options for Windows (issue #3364)

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 18 Feb 2009 12:30:22 -0500

On Wed, Feb 18, 2009 at 12:09 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>> No we don't want users to look in our database, but why can't I access my
>> own sqlite database? (TortoiseSVN uses sqlite for its log cache if I
>> remember correctly)
> Ahem: no. The log cache uses its own binary format. No db backend at all.
>> And why don't we want users to share the same sqlite installation on
>> Windows, while we can't even specify a standard version of sqlite on other
>> OSs?
> shared libs on Windows is always a very bad idea. Only optimists who
> never had their app in use by more than 2 people would even consider
> such a thing.
> Seriously: in TSVN, we use our own build script not just because we can
> automate the whole build that way, but also to 'rename' all the shared
> libs to avoid any possible problems of the so called 'dll hell'.

This is what I was thinking too. Look how often we have to deal with
crappy apps that dump old OpenSSL DLL's into the Windows\System32
folder. I am also thinking of apps like TortoiseSVN and AnkhSVN that
will use the latest Visual Studio to compile everything, and Subclipse
and the command line which still use MSVC 6. We would not want those
DLL's to mix.

Mark Phippard
Received on 2009-02-18 18:30:38 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.