> 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
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4