RE: [PHP-GENERAL] Compiling

Loading all these 3rd party libraries on startup, assuming all the extensions were enabled, would slow things down a bit, but once you are up and running the performance difference should be insignificant. -Rasmus On Fri, 23 Jun 2000, Boaz Yahav wrote: > So what you are saying, if I get you correctly, if someone was to create > some > huge tar.gz file which contains it all and opens into one huge tree of > directories > of all of the modules and with the proper script to compile it all in the > proper way > there should be no problem to do this? > > No performance costs etc? > > berber > > > -----Original Message----- > From: Rasmus Lerdorf [mailto:rasmus@php.net] > Sent: Friday, June 23, 2000 6:58 PM > To: Boaz Yahav > Cc: PHP General (E-mail) > Subject: Re: [PHP-GENERAL] Compiling > > > > I often see people get to a situation where they are missing a module and > > have to recompile PHP. > > Well, doing something like: > > ./configure --with-mysql=shared > make > > does actually work. It creates modules/mysql.so (along with a standalone > PHP binary, but you can ignore that) > > This mysql.so can be loaded into PHP using dl() or via the extension > directive in the php.ini file, so you don't actually have to recompile PHP > to add a module. This is true for both the static and the DSO version of > PHP. > > > Is there a reason not to compile it all always? I mean, simply compile all > > of the options like > > LDAP, PDF,FTP, GD, ODBC etc... and the rest of the things most of us use > or > > maybe will use > > sometime. > > The reason being that most of these things require third-party library > support and trying to compile it all will be difficult since we would have > to go hunting all over the file system looking for the needed stuff and > most of it won't be available. > > -Rasmus >