On Thu, Oct 2, 2008 at 3:29 PM, Purple Streak
<mrpurplestreak_at_googlemail.com> wrote:
> 2008/10/2 Mark Phippard <markphip_at_gmail.com>:
>> And my only point there was, why not
>> consider the "include single file" approach and build it into our
>> library.
>
> I used sqlite on windows in a project and iirc it was a no brainer to
> build on windows
>
> (in fact I just did this now to check - download the "single file" bit
> and just pass it to the compiler - cl /Fosqlite3.obj sqlite3.c)
>
> I would just take the single file of sqlite3 and embed it wholly
> inside whichever library needs it (or with a SVN wrapper round it) and
> put it into the build system. Simplest all round surely?
>
> (Building SVN on windows is a major pain - mainly because of all the
> external things needed to be brought in and the instructions are
> really hairy - i've done it but it wasn't something I wanted to repeat
> on a new machine. but this is another discussion! Sqlite is one of
> the easiest things so just check the source in and don't make it yet
> another thing to download I implore you!)
When we were using this during 1.5 development we were requiring it be
built as a DLL and it was just more difficult. Not impossible. Also,
they do not include any MSVC project like a lot of other products.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-02 21:52:33 CEST