[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: <cmpilato_at_collab.net>
Date: 2001-01-29 20:49:38 CET

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

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.
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.