My goal is NOT TO REMOVE mbstring FROM THE ext DIRECTORY. Here is what I do want:
I build php for tens of thousands of web servers. Those servers are all over the world. I only want to build one default PHP core apache module that only has the standard core things and then everything else as shared extensions. This way all the servers in the US don't have to include mbstring, but the server in JP can add one line in the php.ini to load mbstring and use it. Another example is why do all of the server have to have xml/xslt in their PHP module when only a very few will be using it, this way those few can edit php.ini and load the extension. I would like to make a suggestion on extension in the ext directory. If your extension is not in the standard directory, then you should to be able to be built both statically and shared from *BOTH* the PHP ./configure line and using phpize, ./configure, make methods. I know of 2 modules that can not be built shared from the PHP ./configure line, but I do believe work with the phpize method. I will be sending another message about today about mysql, the other is sessions. I guess my sales pitch of "can be removed from ext" back fired. :-) Should of just stuck with "can be built as a shared extension". Thanks, Brian At 1:57 PM +0100 6/21/02, Wez Furlong wrote: >mailparse (now in PECL) also requires that mbstring be installed. >More specifically, it requires that the mbstring headers are installed >in the pear header directory when building it (mailparse) as a SCE. > >Also, isn't the new multibyte support in ZE dependent on mbstring in >some way? (I'm just guessing here, so excuse me if I am wrong) > >We really need to make sure that pear/pecl installs relevant headers >for SCEs when they are built, so that other SCE will work nicely too. > >If you do decouple mbstring, please make sure that the mbstring headers >are still installed in the pear include directory too! > >--Wez. > >On 20/06/02, "Brian France" <[EMAIL PROTECTED]> wrote: >> Ok, what does exif need from mbstring, code wise? Taking a look at >> it I don't see any references to mbstring in the code. >> >> Thanks, >> >> Brian >> >> At 8:27 PM +0200 6/20/02, Marcus Börger wrote: >> >You will break ext/exif when removing mbstrings current integration >> > >> >At 04:17 20.06.2002, you wrote: >> >>I am testing a patch that allows mbstring to be built as a shared >> >>extension instead of static. This would allow removing any >> >>reference to mbstring from the core PHP code and making mbstring >> >>movable out of the ext directory possible. Not that moving it out >> >>needs to happen, but as much talk about moving things out of the >> >>ext directory I thought it would be a selling point :-) >> >> >> >>The patch basically renames php_treat_data to >> >>php_treat_data_default, creates a function pointer called >> >>php_treat_data that is defaulted to php_treat_data_default, removes >> >>all mbstrings references in php_main.h and makes mbstring.c change >> >>the php_treat_data to mbstr_treat_data in the INIT function and >> >>restores its value in SHUTDOWN. >> >> >> >>Would you be interested in it? >> >> >> >>Thanks, >> >> >> >>Brian >> >> >> >>At 10:36 AM +0900 6/20/02, Yasuo Ohgaki wrote: >> >>>Marcus BöRger wrote: >> >>>>helly Wed Jun 19 17:55:46 2002 EDT >> >>>> >> >>>> Modified files: >> >>>> /php4/ext/mbstring mbstring.c Log: >> >>>> correct handling/generating of php_mbstr_default_identify_list >> >>> >> >>>As I posted before, I'll try merge changes made in php4/ext/mbstring >> >>>to PHP i18n project repository's source. Please note that I'm not >> >>>promising that for sure. >> >>> >> >>>mbstring source has been modified a lot. >> >>>Please check http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/php-i18n/ >> >>>to avoid duplicated work or to make sure your work is included. > > >>> > > >>>-- > > >>>Yasuo Ohgaki > > >>> > > >>> > > >>> > > >>>-- > > >>>PHP Development Mailing List <http://www.php.net/> > > >>>To unsubscribe, visit: http://www.php.net/unsub.php > > >> > > >> > > >>-- >> >>PHP Development Mailing List <http://www.php.net/> >> >>To unsubscribe, visit: http://www.php.net/unsub.php >> >> >> -- >> PHP Development Mailing List <http://www.php.net/> >> To unsubscribe, visit: http://www.php.net/unsub.php > > > > >-- >PHP Development Mailing List <http://www.php.net/> >To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
