Hello, thanks to this group I was able to solve some problems with static linking and dynamic linking of unmanaged code. Currently I'm working on using the Crypto++ in an "advanced level" ,-)) That is: A project in .NET 2003 C++ that mixes managed and unmanaged code...to make this even worse: The result of tihs build is a dll. And this dll should be able to cope with the downloadable DLL/FIPS version of crypto++. In general this should work, or as Wei Dai states that "using a DLL from another DLL" should be no problem in general. I guess he had never the "opportunity" to try this with managed code <g>
So I downloaded the FIPS-DLL 5.2.3 precompiled library, installed it and made some minimal enhancements of my current project: Definded "CRYPTOPP_DLL_ONLY" in the preprocessor, included "dll.h" before any other crypto include and added the appropriate include and additional paths to the linker. Compiling was 100% error/warings free, but the linking failed with the following problems: ================================================================== LINK : error LNK2020: Nicht aufgelöstes Token (0A0000F0) [EMAIL PROTECTED] [EMAIL PROTECTED]@CryptoPP@@@CryptoPP@@2QBEB LINK : error LNK2020: Nicht aufgelöstes Token (0A000105) ? [EMAIL PROTECTED]@CryptoPP@@[EMAIL PROTECTED] [EMAIL PROTECTED]@std@@[EMAIL PROTECTED]@2@@std@@B LINK : error LNK2020: Nicht aufgelöstes Token (0A000107) g_pAssignIntToInteger LINK : error LNK2020: Nicht aufgelöstes Token (0A000108) g_nullNameValuePairs LINK : error LNK2020: Nicht aufgelöstes Token (0A00011E) [EMAIL PROTECTED] [EMAIL PROTECTED]@CryptoPP@@@CryptoPP@@2IB ================================================================== Any ideas to that? I would have assumed to see some problems with the new/delete redefinitions but the above linking problems kind of dazzled me. Best regards, Soeren Gerlach --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
