![]() These instructions are from the top of my head so you may need to adjust the commands and procedures. I remember compiling the PHP from source around 5 times before it worked without any warnings.īut essentially they are telling you to compile PHP from source, then compile their extension from source and then use the built PHP+extension with the downloaded SDK. The SDK will let you know if the built PHP binaries are incompatible with the SDK version you use. so for the PHP5.5 you just built using the PHP configuration files.Īfter that you need to install the PHP SDK and configure it to use the newly built PHP binary $ dev_appserver.py -php_executable_path=/opt/php55/bin/php-cgi (That Git repository contains detailed building instructions so you should probably refer to them when building.)Įnable the resulting. Note that there is no 32-bit version of Google Chrome. Visit the official Google Chrome download page and click the Download Chrome button. Our first step is to obtain the Google Chrome. $ phpize # remember to use the phpize from the just built PHP5.5 binaries The Ubuntu apt package manager uses installation packages called. Default SDK install doesnt include some extra components like App Engine extensions. Then you need to get that source for the PHP extension and build it $ git clone gcloud is the primary CLI tool to work with Google Cloud resources. The prefix argument tells the compiler where to install the resulting application. I think Google had an official list of modules and extensions they use inside GAE PHP and inside the SDK PHP. That linked page contains instructions on building PHP but the procedure is similar to the following: $ git clone Īnd remember to pick the modules and packages you want to compile with PHP5.5 to be used in the SDK. You should grab the latest PHP5.5 branch from their source repo ( ) and build it. ![]() You need to build PHP and that extension from source. Don't remember using it on the SDK in Ubuntu 14.04. That GAE PHP extension seems like a quite new thing. ![]()
0 Comments
Leave a Reply. |