BTW: I don't know if this is part of the problem or just makes it more confusing, but I was (accidentally) building the debug Crypto++ with a release build of my code (NDEBUG defined and -O1), so crypto was un-optimized, except for templates and inlines. I am trying (so far unsuccessfully) to build both versions and link in the right version in my executable (using GNUMakefile and gmake for Crypto++ and boost's bjam system for my app and libs). There appear to be problems with asserts still showing up in the linker even with a make clean.

Would anyone be interested in a bjam make for Crypto++ once I put it together?

Michael Hunley
Senior Engineer
PocketPurchase, Inc.


Reply via email to