Re: Question about "shared" v "not-shared"?
| From: | Alan Lord | Date: | Sun, 17 Sep 2000 08:57:29 +0000 |
| Subject: | Re: Question about "shared" v "not-shared"? | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-17071@lists.php.net to get a copy of this message | ||
Thanks for the reply.
Al
From: Rasmus Lerdorf <rasmus@php.net> To: Alan Lord <lord_alan@hotmail.com> CC: php-general@lists.php.net Subject: Re: [PHP] Question about "shared" v "not-shared"? Date: Fri, 15 Sep 2000 06:44:49 -0700 (PDT) Whilst trying to figure something else out, I was trawling through the php_config.h and config.log files and playing with various ./configure options. It seems like most of the --with-xxx options and some --enable-xxx options can take "shared" as an argument. When I try this with, for example, bcmath. It all seems to compile fine but it doesn't show up as a module when running phpinfo();. Correct, it would only show up if you added the shared module either directly by calling dl("bcmath.so") before the phpinfo() call, or if you edited your php.ini file and added "extension=bcmath.so". Is this correct behaviour? (I guess it is as it is dynamically linked in when you need it rather than built into the code directly). If this is O.K. what are the benefits/drawbacks of either approach and is there a complete list of which options can take "shared" as an argument? The main benefit is really to binary distributions. It is much simpler to generate a base PHP package and then distribute separate packages for each of the add-on features. If you are compiling from source yourself I don't see much of a benefit to going with shared extensions as opposed to just compiling in the ones you want. -Rasmus_________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.