X86 versions won't work on Apache x64, that's why I need to find their x64 version. But also thank you very much. Posted: Tue 25 Aug '20 Post subject:. Indeed tangent. Thanks for jumping in. Posted: Sat 12 Jun '21 Post subject:. The latest Apache version 2. Posted: Sun 13 Jun '21 Post subject:. I've been busy elsewhere of late , but the method and details are sound. Notably, you can compare the CMake options I've chosen to use, with those in your build process.
Posted: Mon 14 Jun '21 Post subject:. Is this command line I wrote correct? You need the first of these two options for CURL.
Build, make, install; twice. Example Apache configure command line looks like this. After configure finishes we have to compile Apache. To compile Apache a utility called make is used. In the Makefile step by step instructions are written about how to compile the software. Benefit of using make is that if some of the source files are changed and we compile software again, then only files which are changed and files which depend on changed files are recompiled.
When you type make It will start compiling Apache. It will take several minutes depending upon the speed of your computer. After make finishes, shell prompt is available. Now source has been compiled. We will use make install command to install Apache.
Now test your Apache installation by starting Apache:. It'll show Apache homepage, where you can read Apache documentation to know more about Apache. You will have a file named php A new directory php Now we have to configure PHP for compilation process. There are hundreds of options which can be provided to configure script.
These options include the option to specify where PHP should be installed, which functionality should be enabled, like functionality to access mysql databases from PHP and which extensions have to be compiled etc. To see a list of options supported by PHP configure, type:. Extensions provide additional functionality which core PHP doesn't provide.
For example to create images --with-gd option can be used. But for these extensions to work, appropriate libraries must have been installed. If you use some --with option and that library isn't installed on your system then configure will fail. So, my advice is, for the first time don't try to use any extension.
Second option --with-apxs2 specifies that we want to install PHP as Apache 2 shared module. Third option --with-config-file-path specifies that PHP should look for php. Settings like path to directory where php extensions are installed.
Fourth option --with-mysql enables support to access mysql databases through PHP. To use mysql database functions you must have mysql database installed on your system. If you don't have mysql installed you can remove this option.
If this option is not used then library, which is bundled with PHP is used to access mysql databases. Example PHP configure command line looks like this. It will take several minutes to compile. After make finishes and, no error etc. If any warning is displayed then, normally, you can ignore it. If this line is not added by PHP install, which in my case wasn't, then you can add it yourself. Under this section, on a new line, add the above line.
Now you have to add another line to this httpd. When PHP parser is invoked by Apache it reads. Resulting output is then sent back to Apache which in turn sends it to web browser which requested the file. To add this line search for word AddType in httpd. There will be a line like this:.
If no error message is displayed and everything is fine, Apache is started and you are returned to shell prompt. VC9 is good enough for the moment. No big deal. I'm not sure exactly what all this means as I haven't had time to try anything myself.
Hope this helps. If you like, you can follow the goings-on in the internals mailing list here. Also, if you have windows specific questions, there is internals-win lists.
Hi, I agree with your research because according to whatever I experienced during this exercise, I felt that working on php extension is not that much easier on x64 bit because lack of support.
I don't know about the php Even php Not even this issue I faced lot of issue regarding to php So if you are working with php-extension, you have to work with x86 in present scenario. I have used following combination that gave me correct working path for php-extension. Apache 2. Weedpacket, can you give me any detail about the problems you are having? I'd be happy to post it to the windows internal list. Oh, I haven't had any problems - mainly because I haven't got around to trying it yet.
It's a reference to Step 6 of the build process. It's not clear whether the policy is "it won't build for XP" or "we don't care if it doesn't build for XP". And yet the instructions all have that -XP flag. Seems to me that these flags could have been named better. This site is best viewed in a modern browser with JavaScript enabled. Something went wrong while trying to load the full version of this site.
Try hard-refreshing this page to fix the error. No error messages and running phpinfo confirms that OpenSSL is present and enabled. Good luck, and stay out of DLL Hell. Beginning with version 1. This should be part of the documentation btw I just wanted to point out that when you compile with openssl and you're specifying a directory, the acinclude.
When I restarted my web server and examined phpinfo , there was no "openssl" headed section although there were references to openssl in other sections. When any application attempts to use a dll file in windows, the system searches for this file using the following order: 1. The directory from which the application loaded.
The windows directory. The current directory. The directories that are listed in the PATH environment variable. I haven't checked it but I would imagine if another directory in the path contains outdated openssl dlls and this is listed before the PHP directory, a similar situation would occur.
0コメント