Re: [PHP-DEV] Re: cleaning/building just one extension

2002-12-12 Thread Hans Zaunere

--- Sascha Schumann [EMAIL PROTECTED] wrote:
 On Thu, 12 Dec 2002, Andrei Zmievski wrote:
 
  With the new build system, is there a way to clean/build just one
  extension, as opposed to having to do it to the whole tree? Something
  like make clean ext=wddx, perhaps?
 
 We could add a target clean-ext-EXTNAME..

This is akin to my questions yesterday, as obfuscated as they may have been. 
To my understanding, this is what phpize is for? ie, given a PHP source tree,
you can build the framework in any directory for a personal extension.

But in general, what's the excepted way to distribute compiled extensions,
if, for example, I wanted to release a .so that would work with 4.2.x and
newer (and assuming only Apache at this point)?  Would I need to release
specific versions; if so, how many permutations would I need to consider, and
what variables would I need to accomodate?  Initially, I see that
Apache/Apache2-MPM is a big one.



=
Hans Zaunere
New York PHP
http://nyphp.org
[EMAIL PROTECTED]

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] Re: cleaning/building just one extension

2002-12-12 Thread Sascha Schumann
On Thu, 12 Dec 2002, Andrei Zmievski wrote:

 On Thu, 12 Dec 2002, Sascha Schumann wrote:
  We could add a target clean-ext-EXTNAME..
 
  - Sascha

 What about build-ext-EXTNAME? I ran into this yesterday when I checked
 out a fresh copy of the tree and wanted to build only wddx module as a
 shared library.

If you want to build a stand-alone extension, I suggest you
use phpize.

- Sascha


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php