Hi All, Got the solution.
The problem was due to difference in building environment of Application & OpenSSL. Some of the application binaries were built using their older project format, i.e. *.vcproj & rest other binaries were built using their newer project format, i.e. *.vcxproj. Thanks to all, who reponded to my query. Thanks, Pravesh On Wed, Sep 4, 2013 at 4:37 AM, Watson, Patrick <patrick.wat...@ncr.com>wrote: > Check out this page: > http://www.openssl.org/docs/crypto/OPENSSL_Applink.html**** > > ** ** > > Basically, you just need to #include <openssl\applink.c> in your > application. That file defines a virtual table like list of things related > to stdout, stderr, etc. This file only appears to be needed when you start > using functions that might access FILEs or the console, like > ERR_print_errors_fp. **** > > ** ** > > I’m not sure why you are only seeing it in VS2012; maybe you added logging > code so you diagnose issues in the new DLL?**** > > ** ** > > *Patrick Watson, CISSP* > *Software Engineer > Data Security & Electronic Payment Systems > NCR Retail* > > **** > > *From:* owner-openssl-us...@openssl.org [mailto: > owner-openssl-us...@openssl.org] *On Behalf Of *Pravesh Rai > *Sent:* Friday, August 30, 2013 1:07 AM > *To:* openssl-users@openssl.org > *Subject:* Openssl 1.0.1x build using VS 2012**** > > ** ** > > Hi,**** > > **** > > Even though I'm successful in getting the OpenSSL build using VS 2012, but > getting following error message:**** > > **** > > OPENSSL_Uplink(000007FED5A31000,08): no OPENSSL_Applink**** > > **** > > while trying to 'load' libeay32.dll. The problem is solved, if we use > another libeay32.dll, which is built using VS 2005. Except for this, all > other development & usage environment is totally same.**** > > **** > > Do anybody has any clue on this?**** > > **** > > Thanks,**** > > Pravesh**** > > ** ** >
