[Python-Dev] Windows x64 & bsddb 4.4.20 woes

"Martin v. Lšwis" martin at v.loewis.de
Fri Mar 14 16:59:21 CET 2008


> I reviewed all the compiler options used by db_static.vcproj -- the
> only thing I needed to bring over was -DDIAGNOSTIC for debug builds.
> Everything else either had no impact and could be safely dropped, or
> conflicted with compiler options used by the rest of the python build
> (function level linking, buffer overflow checks, etc).

If you take out those options from the db_static project, it *should*
work just the same as what you've got now, right?

Can you use that approach to determine the culprit for making the static
library approach fail?

> As it stands now, the .lib generated by db_static.vcproj for x64
> builds just straight out does not work.  That can be fixed in two
> ways: coerce db_static.vcproj into matching our build, or mimicking
> db_static in a new .vcproj that's contained with our build,
> inheriting our property sheets.  I chose the latter.

I would *really* prefer the former.

Regards,
Martin




More information about the Python-Dev mailing list