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

Re: [patch] added db win32 portability includes to build projects

From: Branko Čibej <brane_at_xbc.nu>
Date: 2001-01-29 23:39:37 CET

cmpilato@collab.net wrote:

> Branko =?ISO-8859-2?Q?=C8ibej?= <brane@xbc.nu> writes:
>> Could you explain why this is necessary? The binary distribution of DB3
>> I made available (see the HACKING file) has no build-win32 directory.
>> That include dir is only in the sources.
>> In fact, this change breaks the build for me.
> This from the HACKING file:
> If you want to build the server components, you'll also need a
> copy of Berkeley DB, version 3.1.14 or newer. The sources are
> available at http://www.sleepycat.com, but you can download a
> binary distribution of version 3.1.17 libraries and tools from
> http://www.xbc.nu/svn/db3-win32.zip

And it goes on to say:

    Unpack the distribution, then set the environment variable
    SVN_DB3_WIN32 to the full path of the db-win32 directory (use the
    System control panel on WinNT/Win2k). MSVC will look for the include
    files in $(SVN_DB3_WIN32)\include, and the libraries in

> Given the two options, I chose the former (grabbing the source from
> sleepycat.com). In the tarball from sleepycat (db-3.1.17.tar.gz), the
> file db.h exists only in build_win32, build_vms, and build_vxworks
> directories. In fact, upon building the DB code using the VS
> workspace in the build_win32 directory, libdb31s.lib is indeed
> created, but no /lib directory is created.
> Now, I'm perfectly willing to entertain the idea that the actual
> Berkeley source distribution doesn't automagically arrange its output
> in a fashion consistent with the binary distribution. If this is
> case, however, we should decide on which of the two distributions is
> legitimate for the purposes of Subversion's build process, and then
> clarify such in the HACKING file--and my vote would fall for the
> source distribution.

O.K., we have to decide about that. Given that we use an installed DB3
on Unix, I wanted to avoid using the source distribution on NT. That's
one reason why I packaged the libraries, includes and docs in a
moredately Unix-ish way; the other is that it's easier for people to
just grab the binaries.

Oh, well. If sou think it's worth the trouble to change this and force
everybody to compile their own version of DB3, go ahead. Personally I'd
rather just put a note in HACKING that you have to copy the include
files and libraries into the ...\include and ...\lib directories.

Brane �ibej
    home:   <brane_at_xbc.nu>             http://www.xbc.nu/brane/
    work:   <branko.cibej_at_hermes.si>   http://www.hermes-softlab.com/
     ACM:   <brane_at_acm.org>            http://www.acm.org/
Received on Sat Oct 21 14:36:20 2006

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.