Home >Backend Development >PHP Tutorial >Do libmysqldll and phpini really need to be copied to the c:windows directory?

Do libmysqldll and phpini really need to be copied to the c:windows directory?

WBOY
WBOYOriginal
2016-07-29 08:42:161059browse

Is this necessary? Many posts on the Internet are based on what others say. Others say they want it, and they also say they want it. In fact, it is practical to copy and fiddle with it again every time you reinstall the system. It is too hard. Friends who have used APMServ, a fool-proof installation package, may find that after the first installation, this thing will not be reinstalled even if the system is reinstalled in the future. Just run the main program and you can run WAMP without any fuss. over and over again.
Some people may think that it copies libmysql.dll to the c:windows directory. In fact, it is not the case. If you don’t believe it, go look for it. Since APMServ can do it, we can do it too. After comparing APMServ with the WAMP we installed, we found that the secret lies in apache's httpd.conf configuration file. When loading PHP in httpd.conf, everyone knows to add this sentence:
LoadModule php5_module E: serverphp528php5apache2_2.dll. Some friends may also know that after adding this sentence, there is no need to copy php.ini to the system directory:
PHPIniDir E: serverphp528php.ini
Now let me talk about the way to avoid copying libmysql.dll to the system directory, which is to add this sentence before loading php5_module:
LoadFile "E:serverphp528libmysql.dll"

The above introduces whether libmysqldll and phpini really need to be copied to the c:windows directory, including the relevant content. I hope it will be helpful to friends who are interested in PHP tutorials.

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn