In message on Wed, 4 Jan 2017
12:21:31 -0600, Benjamin Kaduk said:
bkaduk> Interestingly, having recently configured 1.1.0c on a windows system,
bkaduk> something printed out a warning to the effect of "you seem to not have
bkaduk> nmake.exe on your path; you probably want to install it or dmak
On 01/04/2017 07:09 AM, Richard Levitte wrote:
> Try with nmake, which comes with Visual Studio.
>
> (I now noticed we haven't made nmake a requirement, while we expect
> everyone to use it with the VC-* config targets. We should be more
> explicit about this)
>
Interestingly, having recently con
Use Microsoft's nmake, not dmake. The VC-WIN32 configuration generates
makefiles for use with nmake, which is included with Visual C. You told the
OpenSSL build process to configure itself for Visual C (the "VC" part); now you
have to use it.
If you want to build OpenSSL using some custom toolc
In message
on Wed, 4 Jan 2017 11:14:48 +, Rajat Srivastava
said:
rajat.srivastava01> Hi,
rajat.srivastava01>
rajat.srivastava01> I am working on windows 7 Professional Service Pack 1
rajat.srivastava01>
rajat.srivastava01> I downloaded OpenSSL version openssl-1.1.0c and installed
Activ
Hi,
I am working on windows 7 Professional Service Pack 1
I downloaded OpenSSL version openssl-1.1.0c and installed Active Perl v5.24.0
built for MSWin32-x64-multi-thread
I installed Text::Template, dmake and MinGW (not sure if I should have
installed MinGW)
I ran command "perl configure VC