summaryrefslogtreecommitdiffstats
path: root/PCbuild/readme.txt
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2002-11-23 18:48:06 (GMT)
committerTim Peters <tim.peters@gmail.com>2002-11-23 18:48:06 (GMT)
commit84c7a3f3289ef786a756faf52c188d2b08c52f34 (patch)
treed607ec04fe6d534ea003a10b5cea801cc80908f3 /PCbuild/readme.txt
parentef7fe2e8137824248cf45d316535b76dae302b5a (diff)
downloadcpython-84c7a3f3289ef786a756faf52c188d2b08c52f34.zip
cpython-84c7a3f3289ef786a756faf52c188d2b08c52f34.tar.gz
cpython-84c7a3f3289ef786a756faf52c188d2b08c52f34.tar.bz2
Try linking the static Sleepycat lib into _bsddb.pyd. Hard to say
whether this is a correct thing to do: + There are linker warnings (see PCbuild\readme.txt). + test_bsddb passes, in both release and debug builds now. + test_bsddb3 has several failures, but it did before too. Also made pythoncore a dependency of the _bsddb project, updated build instructions, added database conversion XXX to NEWS, and fiddled the Windows installer accordingly.
Diffstat (limited to 'PCbuild/readme.txt')
-rw-r--r--PCbuild/readme.txt28
1 files changed, 16 insertions, 12 deletions
diff --git a/PCbuild/readme.txt b/PCbuild/readme.txt
index 7f8e138..94594d0 100644
--- a/PCbuild/readme.txt
+++ b/PCbuild/readme.txt
@@ -161,6 +161,8 @@ bz2
_bsddb
+ XXX The Sleepycat release we use will probably change before
+ XXX 2.3a1.
Go to Sleepycat's patches page:
http://www.sleepycat.com/update/index.html
and download
@@ -182,19 +184,21 @@ _bsddb
yes, of course). Choose configuration "db_buildall - Win32 Release",
and build db_buildall.exe.
- XXX You have to copy
- XXX dist\db-4.0.14\build_win32\Release\libdb40.dll
- XXX into PCbuild (or elsewhere on your path) before the tests
- XXX will run.
-
- XXX A debug-mode build blows up when running this, presumably because
- XXX I'm mixing debug-mode MS stuff with Sleepycat's release-mode
- XXX DLL. This gives me a headache. I would *like* to, as the old
- XXX bsddb 1.85 project apparently managed to do, link the Berkeley
- XXX DLL into the guts of our _bsddb.pyd. I don't know how to.
+ XXX We're actually linking against Release_static\libdb40s.lib.
+ XXX This yields the following warnings:
+"""
+Compiling...
+_bsddb.c
+Linking...
+ Creating library ./_bsddb.lib and object ./_bsddb.exp
+LINK : warning LNK4049: locally defined symbol "_malloc" imported
+LINK : warning LNK4049: locally defined symbol "_free" imported
+LINK : warning LNK4049: locally defined symbol "_fclose" imported
+LINK : warning LNK4049: locally defined symbol "_fopen" imported
+_bsddb.pyd - 0 error(s), 4 warning(s)
+"""
+ XXX This isn't encouraging, but I don't know what to do about it.
- XXX The Sleepycat release we use will probably change before
- XXX 2.3a1.
YOUR OWN EXTENSION DLLs