The general process is almost explained on the Internet, mainly due to encountering several pitfalls.
Let’s briefly talk about the process:
InstallationActivePerl-5.22.1.2201-MSWin32-x64-299574.msi, I did not download this from the official website Find it on the website, and find it directly in the csdn resource.
Install openssl, I used git clone directly.
I also installed these two on the C drive according to the tutorial.
Use the command line tool, enter the C:\Perl64\eg path, and execute "perl example.pl". If "Hello from ActivePerl!" is displayed, Perl is installed successfully.
My execution was not successful at first. I had to configure the perl environment variables before this could appear.
Then I used the developer command prompt tool of vs2013 to execute perl configure VC-WIN32. I kept getting errors, showing:
nasm is not found
I installed nasm, but The situation has not improved, and it is still not found. Finally I saw an article saying to use this command:
perl Configure VC-WIN32 no-asm –prefix=c:\openssl
It works, but the prompt:
I just Execute according to the prompts:
ppm install dmake
Okay, this error will not be reported.
Finally run
ms\do_ms
nmake -f ms\ntdll.mak
It still reports an error, no matter what.
Starting with 1.1.0 there are no msdo_*.bat files anymore.Instead execute the following steps: x32 compilation on Windows: perl Configure VC-WIN32 nmake nmake test x64A compilation on Windows: perl Configure VC-WIN64A nmake nmake test
That is to say, when configuring openssl-1.1.0 or above, msdo_*.bat and other things will not be generated
Just skip this step
As mentioned above, run nmake first, and then run nmake test. It took a while and it took a long time, but it was finally done.
The above is the detailed content of Detailed explanation of the process of installing openssl under windows10. For more information, please follow other related articles on the PHP Chinese website!