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

libdb40.lib on win32 (was: autogen.sh --release doesn't work)

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-05-07 18:18:13 CEST

On Tue, May 06, 2003 at 08:42:18PM -0500, cmpilato@collab.net wrote:
> Greg Stein <gstein@lyra.org> writes:
> > On Thu, Apr 24, 2003 at 02:41:16PM -0400, Michael Price wrote:
> > > autogen.sh --release doesn't work, likely because of gstein's changes
> > > recently to the windows build. Kinda prevents the whole release thing.
> > >
> > > I don't have to time or energy to fix this as I'm home sick today with a
> > > sinus infection. I'll check back in later tonight to see if the person(s)
> > > responsible have cleaned up after themselves.
> >
> > My first commit today should fix the --release problem, and my second commit
> > had Branko's fixes for the Windows build.
> >
> > Are you available to do the release?
>
> So, did you remember to fix the fact that the tarball users on Windows
> should *not* have to run gen-make.py to find their libdb40.lib's and
> such, like we talked about at lunch. (If you have, a simple "yep"
> will do.)

I'm not sure what the right answer is there. However, in both releases, the
library needs to reside in a particular location, so I'm not sure that we've
regressed (?). Maybe the current, expected location isn't ideal and we need
to change that.

The underlying problem is that we don't have a "configure" step on Windows
(and never did). What should we do instead?

Unblocking the 0.22 release seemed a bit more important than introducing a
new concept into the Windows build...

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 7 18:17:50 2003

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.