Hi Wim Thanks for the response. Actually, I am trying to compile openssl for WinCE 5.0. That's why I was trying to figure out whether I should define this macro while compiling or not. However, if this macro is defined, I get few compilation errors.
Have anyone compiled the code with this flag for the same platform? Thanks Kchitiz On Wed, Aug 17, 2011 at 10:59 PM, Wim Lewis <w...@omnigroup.com> wrote: > > On 17 Aug 2011, at 7:36 AM, Kchitiz Saxena wrote: > > Can somebody briefly explain the use of macro OPENSSL_NO_STDIO. There are > few functions like SSL_CTX_use_certificate_file() which are defined only if > this macro is not defined. What is the functionality which is derived out of > this macro definition. In short, what I get/loose if I define this macro > while compiling this macro. > > It removes functions which depend on the "stdio" functions (defined in > stdio.h, which perform I/O using the FILE * type). I assume this is useful > when openssl is being compiled for use in an embedded environment or other > special situation where stdio is not available. > > I think it's not a macro that users of openssl are expected to define; > instead, it's defined when openssl is configured, and users of the library > can check whether it's defined in openssl's headers (probably via > opensslconf.h). > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org >
