Hi Soren,
Anyway, I first tested Crypto++ with static linking. I succeeded in using the HexEncoder when generating code with both the /MTd and /MDd flags. It turns out this works on my own computer as well.
Here's what I know about random errors which disappear when moving between static and dynamic linking: I once had a project with the following settings: Crypto++ (static linking) (version 4 something, or early 5) MFC (dynamic linking) Dinkumware STL(static linking into a library backed by a DLL) The project was MDI, so I was having big time problems with the Document Iterator and Dinkumware 's library. I got it to compile eventually with some warnings about mixing and match (symbol xxx already defined, use 'no default lib'...). If the Release EXE was run from a Network Drive, I would get random crashes in Ordinal 6758. See http://groups.google.com/group/microsoft.public.vc.mfc/tree/browse_frm/thread/cbad8aa7d0ad6b13/22a323ded8787db3 It's not a solution, just a heads up. Jeff dreijer wrote:
Okay, so I have installed VS2005 Professional on a clean Windows XP SP2 machine. I have not yet installed VS2005 SP1 as it takes forever. The build of the library still fails due to the custom build rule on adhoc.cpp.proto. I get the following output: ------ Rebuild All started: Project: cryptlib, Configuration: Debug Win32 ------ Deleting intermediate and output files for project 'cryptlib', configuration 'Debug|Win32' Performing Custom Build Step The system cannot find the path specified. Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step" Build log was saved at "file://c:\Documents and Settings\Søren Dreijer\Desktop\cryptopp54\Win32\cryptlib\Debug\BuildLog.htm" cryptlib - 1 error(s), 0 warning(s) Anyway, I first tested Crypto++ with static linking. I succeeded in using the HexEncoder when generating code with both the /MTd and /MDd flags. It turns out this works on my own computer as well. Previously, I've been using the DLL rather than the static library in my own applications. Before I even got to test the behavior of the DLL today, however, I experienced another problem. When the application uses the DLL and it executes the first call to the library, I get the following exception: Crypto++ was not able to obtain new and delete function pointers. First-chance exception at 0x7c812a5b in Cryptopp Test.exe: Microsoft C++ exception: int at memory location 0x0012f190.. I've had this appear occasionally onm VS2003 too, but it seemed to go away. The library and the application are using the same runtime library (/MTd) and the same calling convention (__cdecl (/Gd)) It appears the dlltest project included in the library uses the __stdcall (/Gz) calling convention. I tried doing the same in my own application, but I still got the exception. Hmm..
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cryptopp-users?hl=en -~----------~----~----~----~------~----~------~--~---
