Issue 27400

Summary: build berkeleydb with dmake on win32
Product: utilities Reporter: mmeeks <mmeeks>
Component: codeAssignee: mmeeks <mmeeks>
Status: CLOSED FIXED QA Contact: Unknown <non-migrated>
Severity: Trivial    
Priority: P3 CC: andreas.bille, darragh.sherwin, issues, pavel, quetschke, stx123
Version: 680   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: PATCH Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
toplevel diff
none
new dmake files
none
improved patch
none
improved patch none

Description mmeeks 2004-04-03 03:07:00 UTC
This (admittedly very limitedly tested patch) bins crack-smoking in the build,
and switches to a pure dmake build for win32.
Comment 1 mmeeks 2004-04-03 03:08:24 UTC
Created attachment 14298 [details]
toplevel diff
Comment 2 mmeeks 2004-04-03 03:08:52 UTC
Created attachment 14299 [details]
new dmake files
Comment 3 hennes.rohling 2004-04-05 14:17:10 UTC
Reassigned
Comment 4 Frank Schönheit 2004-04-05 16:08:48 UTC
not everything which has a "db" in it's name is in my responsibility :)
Comment 5 mmeeks 2004-04-13 12:09:54 UTC
New patch pair fixes a number of issues - seems to work nicely for me now;
comments appreciated.
Comment 6 mmeeks 2004-04-13 12:10:49 UTC
Created attachment 14485 [details]
improved patch
Comment 7 mmeeks 2004-04-13 12:11:14 UTC
Created attachment 14486 [details]
improved patch
Comment 8 andreas.bille 2004-06-08 15:26:51 UTC
Michael, since we will change to a newer version of BerkelyDB in the near
future, I will not use your patch currently. 
Comment 9 mmeeks 2004-07-02 14:28:49 UTC
so - be warned the Java part of this doesn't function - though it should be easy
to fix up I guess.
Prolly worth snarfing the latest version from:

http://ooo.ximian.com/ooo-build/patches/OOO_1_1

as well before going too far.
Comment 10 andreas.bille 2005-05-23 13:13:29 UTC
reop
Comment 11 andreas.bille 2005-05-23 13:14:39 UTC
will not be fixed due to change to bdb4, which, on windows, is already built
with dmake.
Comment 12 stx123 2006-02-21 14:37:38 UTC
So it looks like the patch is now obsolete. If this is the case, could you
please close the issue then.
Comment 13 mmeeks 2006-02-21 14:56:20 UTC
sure - closed fixed.
Comment 14 pavel 2006-02-21 20:37:41 UTC
.