Sorry; wrong list, I get boths lists in the same mailbox and I just replied
to a message already there.

> -----Original Message-----
> From: Sam Liddicott 
> Sent: 26 April 2002 12:01
> To: [EMAIL PROTECTED]
> Subject: phpize writes config.m4
> 
> 
> I'm making some more changes to php-swig, where it writes out 
> the sample config.m4 file.
> 
> It's pretty complete now but it strikes me that this code 
> should probably be part of phpize.
> 
> Most modules have the same requirements for config.m4 (below).
> Perhaps we could have a phpize.in file where we provide the 
> module name, required header and library files and an 
> optional symbol to test compile each library.
> 
> Does this make sense?  I've already done it for swig but I 
> think it belongs in phpize
> 
> Sam
> 
> 1) PHP_ARG_WITH....
> 
> 2) search paths for INCDIR looking for certain include files
> 
> 3) search paths for LIBDIR looking for certain LIBS
> 
> 4) PHP_REQUIRE_CXX, AC_CHECK_LIB(stdc++, cin) if it is a C++ module
> 
> optional 5) AC_CHECK_LIB... to check the library links and a 
> test symbol is present
> 
> 6) PHP_SUBST(***_SHARED_LIBADD)
>    AC_DEFINE(HAVE_***, 1, [ ])
>    AC_DEFINE_UNQUOTED(PHP_***_DIR, "$***_DIR", [ ] )
> 
> for each library
>   PHP_ADD_LIBRARY_WITH_PATH(***, $***_LIBDIR, ***_SHARED_LIBADD)
> 
> for include path
>   PHP_ADD_INCLUDE($***_INCDIR)
> 
> 7) PHP_EXTENSION(***, $ext_shared)
> 




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

Reply via email to