Perhaps, if you already have the source tree available in an environment where you can run findstr on it, and know about findstr. Google does a much quicker and easier job on this problem for everyone else, and is arguably more informative since it gives the check-in comments as well as at least some of the definitions and uses.
> From: Thomas J. Hruska [mailto:shineli...@shininglightpro.com] > Sent: Thursday, April 10, 2014 8:53 AM > > On 4/9/2014 8:03 PM, Jeremy Farrell wrote: > > Googling "check_winnt" suggests openssl/e_os.h. > > findstr /sic:"check_winnt" * > > Is, IMO, easier and more informative than using Google. Results in: > > apps\apps.c: if (check_winnt()) > crypto\bio\bss_log.c: if (check_winnt()) > crypto\cryptlib.c: if (check_winnt() && OPENSSL_isservice() > 0) > crypto\rand\rand_win.c: if (check_winnt() && OPENSSL_isservice()>0) > e_os.h:# define check_winnt() (1) > e_os.h:# define check_winnt() (GetVersion() < 0x80000000) > > Used four times, has two #defines. > > -- > Thomas Hruska > Shining Light Productions > > Home of BMP2AVI and Win32 OpenSSL. > http://www.slproweb.com/ ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
