Frustrated by the outdated instructions of building OpenSSL on different platforms. I am collecting a static snapshot
 of the versions I forked on 5/16/2019 for my own use, and docuement the build steps that I have tested. 
  
 Copyright (c) 2019 John Xu.  This version works for Windows and tested on windows 10 using Visual Studio 2017. 
                              For version works for Sony Playstation platforms. See https://github.com/v-yuehxu/openssl

 The 64 bit build instruction for windows is as follows:

  0. get the code from my forked repo location:

       git clone https://github.com/cndpost/openssl

  1. launch a Visual Studio X64 Native tools Command prompt for VS 2017 (if you use X64_86 Cross Platform tools, you will
      have following errors in the end: fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86')

  2. change to the directory where you have copied openssl sources, such as cd c:\myPath\openssl

  3. configure for the target OS with the command:
        
         perl Configure VC-WIN64A

      You may also be interested to set more configuration options as documented in the general INSTALL 
      For instance: 
 
         perl Configure no-asm VC-WIN64A.

  4. run command:

         NMake

 The 32 bit build instruction for windows is as follows:

  0. get the code from my forked repo location:

       git clone https://github.com/cndpost/openssl

  1. launch a Visual Studio x86 Native tools Command prompt for VS 2017 

  2. change to the directory where you have copied openssl sources, such as cd c:\myPath\openssl

  3. configure for the target OS with the command:
        
         perl Configure VC-WIN32

      You may also be interested to set more configuration options as documented in the general INSTALL 
      For instance: 
 
         perl Configure no-asm VC-WIN32

  4. If we had build 64 bit before, and now we switch to 32 bit version, we need to run following command to clean the existing .obj files:

         NMake clean

  5. run command:

         NMake





=====================Original Readme from https://github.com/openssl================
 OpenSSL 3.0.0-dev

 Copyright (c) 1998-2018 The OpenSSL Project
 Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson
 All rights reserved.

 DESCRIPTION
 -----------

 The OpenSSL Project is a collaborative effort to develop a robust,
 commercial-grade, fully featured, and Open Source toolkit implementing the
 Transport Layer Security (TLS) protocols (including SSLv3) as well as a
 full-strength general purpose cryptographic library.

 OpenSSL is descended from the SSLeay library developed by Eric A. Young
 and Tim J. Hudson.

 The OpenSSL toolkit is licensed under the Apache License 2.0, which means
 that you are free to get and use it for commercial and non-commercial
 purposes as long as you fulfill its conditions.

 OVERVIEW
 --------

 The OpenSSL toolkit includes:

 libssl (with platform specific naming):
     Provides the client and server-side implementations for SSLv3 and TLS.

 libcrypto (with platform specific naming):
     Provides general cryptographic and X.509 support needed by SSL/TLS but
     not logically part of it.

 openssl:
     A command line tool that can be used for:
        Creation of key parameters
        Creation of X.509 certificates, CSRs and CRLs
        Calculation of message digests
        Encryption and decryption
        SSL/TLS client and server tests
        Handling of S/MIME signed or encrypted mail
        And more...

 INSTALLATION
 ------------

 See the appropriate file:
        INSTALL         Linux, Unix, Windows, OpenVMS, ...
        NOTES.*         INSTALL addendums for different platforms

 SUPPORT
 -------

 See the OpenSSL website www.openssl.org for details on how to obtain
 commercial technical support. Free community support is available through the
 openssl-users email list (see
 https://www.openssl.org/community/mailinglists.html for further details).

 If you have any problems with OpenSSL then please take the following steps
 first:

    - Download the latest version from the repository
      to see if the problem has already been addressed
    - Configure with no-asm
    - Remove compiler optimization flags

 If you wish to report a bug then please include the following information
 and create an issue on GitHub:

    - OpenSSL version: output of 'openssl version -a'
    - Configuration data: output of 'perl configdata.pm --dump'
    - OS Name, Version, Hardware platform
    - Compiler Details (name, version)
    - Application Details (name, version)
    - Problem Description (steps that will reproduce the problem, if known)
    - Stack Traceback (if the application dumps core)

 Just because something doesn't work the way you expect does not mean it
 is necessarily a bug in OpenSSL. Use the openssl-users email list for this type
 of query.

 HOW TO CONTRIBUTE TO OpenSSL
 ----------------------------

 See CONTRIBUTING

 LEGALITIES
 ----------

 A number of nations restrict the use or export of cryptography. If you
 are potentially subject to such restrictions you should seek competent
 professional legal advice before attempting to develop or distribute
 cryptographic code.