RE: MFC Debug Link Error

[Henry Kropf]

Title: RE: MFC Debug Link Error

I don't think RC2 is exposed in the dll, but there is a library you can build in the source directory that will work in conjunction with the DLL's lib to expose all the other functionality.   -----Original Message----- From: Seshu Madabushi [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003 9:11 AM To: [EMAIL PROTECTED] Subject: RE: MFC Debug Link Error I am trying to use the RC2 encryption function call and facing the same problem. I am trying to link a dll (compiled with stdcall) with the FIPS cryptodll. I am able to access other functions like RSA, DES etc.Can anyone please explain.   Thanks Seshu -----Original Message----- From: Kirsch, James C. [mailto:[EMAIL PROTECTED] Sent: Mon 11/24/2003 10:44 AM To: '[EMAIL PROTECTED]' Cc: Subject: RE: MFC Debug Link Error Thank you.  This seems to be the problem.   From: Henry Kropf [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 6:24 AM To: [EMAIL PROTECTED]             I've run into this, It's because the FIPS dll is compiled with the stdcall model, and by default a VC++ project is cdecl.         If you're in the unfortunate circumstance we're in of being locked into cdecl, you'll have to edit many of the function prototypes in the crypto++ headers to add _stdcall.   -----Original Message----- From: Wei Dai [mailto:[EMAIL PROTECTED]] Sent: Saturday, November 22, 2003 8:02 PM To: [EMAIL PROTECTED] Subject: Re: MFC Debug Link Error   Please send the project file and source code so I can reproduce this problem. You might want to send it directly to me. On Fri, Nov 21, 2003 at 02:21:18PM -0800, Kirsch, James C. wrote: > I could use some help figuring out why I get the following link error... > >  > > EncryptDecrypt.obj : error LNK2001: unresolved external symbol > "__declspec(dllimport) public: static char const * __cdecl > CryptoPP::DES_EDE3_Info::StaticAlgorithmName(void)" > ([EMAIL PROTECTED]@CryptoPP@@SAPBDXZ) > > ..\shared\debug\Communicator.exe : fatal error LNK1120: 1 unresolved > externals > > Error executing link.exe. > >  > > This only happens when I try and compile my program in debug.  Release > versions build fine.  My program is a MFC VC6.0 application and I am simply > linking in the FIPS 140-2 compliant download dll.  Thank you. > >  > > James Kirsch > The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, forwarding, or otherwise copying of this message is strictly prohibited.  If you have received this communication in error, please notify Padcom immediately by e-mail at [EMAIL PROTECTED] and delete the original message.  Although Padcom utilizes industry accepted methods to scan email and attachments for viruses, it does not guarantee that either is virus-free and accepts no liability for any damage sustained as a result of viruses.  Padcom makes no representation or warranty (express or implied) as to the accuracy or completeness of any information provided in this e-mail message and expressly disclaims any and all liability that may be based on information contained therein. The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, forwarding, or otherwise copying of this message is strictly prohibited. If you have received this communication in error, please notify Padcom immediately by e-mail at [EMAIL PROTECTED] and delete the original message. Although Padcom utilizes industry accepted methods to scan email and attachments for viruses, it does not guarantee that either is virus-free and accepts no liability for any damage sustained as a result of viruses. Padcom makes no representation or warranty (express or implied) as to the accuracy or completeness of any information provided in thi! s e-mail message and expressly disclaims any and all liability that may be based on information contained therein.