You can build a static library that contains only code that are not in the DLL, by building the "DLL-Import Debug" or "DLL-Import Release" configuration instead of the "Debug" or "Release" configuration. Then you can link your application with both the DLL and the static library.
----- Original Message ----- From: "Nick42" <[EMAIL PROTECTED]> To: "Crypto++ Users" <[EMAIL PROTECTED]> Sent: Monday, August 20, 2007 4:28 PM Subject: Question about FIPS dll usage and util functions > > I've been using crypto++ as a static lib for a while, and am trying to > convert to use as a FIPS certified dll. However, only some of the > objects are included in the FIPS dll, and we are using some of the > others also, which is causing linking to fail. > > Is there a suggested way to link both the FIPS certified dll and the > extra utility code? I didn't see a lib with only the utility code. Has > anyone else attempted this, and/or is there something easy I'm missing? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
