..\cryptlib does not look kosher. Specify the full path.
Jeff On 12/12/06, Dane Anderson <[EMAIL PROTECTED]> wrote: > OK. Attached are: > LibSourcePath.JPG - directory where I put/built the library. > > AppSourcePath.JPG - directory where I am trying to build my app from > > IncludeDirectories.JPG - application property page (properties - C/C++ - > General - additional include directories) > > LibPath.JPG - application property page (properties - linker - General - > additional library directories) > > Any suggestions you can make to help me get this fixed would be > appreciated. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:cryptopp- > > [EMAIL PROTECTED] On Behalf Of Jeffrey Walton > > Sent: Tuesday, December 12, 2006 11:42 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Crypto++ 5.4 beta release > > > > > > Hi Dane, > > > > Send me screen shots of the Lib Path, Include Path, and Source Path. > > Using <ALT> <PRINT SCREEN> (it captures the foreground Window). Go off > > the group. > > > > Jeff > > > > On 12/12/06, Dane <[EMAIL PROTECTED]> wrote: > > > > > > > > > Jeffrey Walton wrote: > > > > Hi Dane, > > > > > > > > Are you using the Crypto++ namespace? (the errors are usally a bit > > different). > > > > > > I added: > > > > > > using namespace CryptoPP; > > > > > > to my StdAfx.h, after getting this response. No soap. Still getting > > > the same unresolved symbols. > > > > > > > > > > > The first think I would do is physically remove any of the old > > > > library. (Burn it to a CD if it makes you feel better). > > > > > > Did that. > > > > > > > > > > > Then, I would rebuild CryptLib Test only, and get a little starter > > > > project going - something that is trivial. > > > > > > CryptLib Test builds, with no unresolved symbols. > > > > > > > > > > > It definetly sounds like a path problem to me. Have you verified > the > > > > path to the Lib and Header files in VC8? > > > > > > Yes, I have. In fact I used cut and paste from the Windows address > > > bar to put the paths into the properties (modified to replace common > > > ancestor dir paths with ..). So, I know it's not a problem of a > typo. > > > > > > I should think that if it were a pathing problem I would be > > > getting a can't open the header file, or library (which I DID get > > > before > > > I remembered to add the paths), rather than just an unresolved > > > external. The downloaded solution for 5.4 has the library named > > > cryptopp.lib (and cryptopp.dll), where the old library (5.1.2) was > > > called cryptlib.lib (and cryptlib.dll) (at least it is on our > setup). > > > I've > > > examined the list of libraries and cryptlib isn't in them (anymore), > > > so I know it's not using the old library erroneously. > > > > > > > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
