Re: cvs: php4 / Makefile.global acinclude.m4 configure.in /main php_embed.c php_embed.h /sapi/cgi Makefile.frag config.m4 /sapi/cli Makefile.frag
config.m4 /sapi/embed config.m4 php_embe

> That might be, but this doesn't answer my question :) Wouldn't it be > very useful of the PHP lib gets compiled/installed on every compile just > like CLI? I think it would be very useful that lib, CLI and the SAPI of > choice are compiled at the same time. This was also Edin's reasoning to > implement it like he did. I disagree. There is nothing special about the embedded SAPI module and thus it does not get special treatment, including poluting all kind of files. The Unix build chain has been crafted around the idea that there is one specific target with an explicit set of requirements (especially regarding type of linkage). The CLI SAPI module is a target which does not care how its modules were compiled. This is not the same case with the embedded SAPI module where the target is a library. We could come up with an extension to the build chain which allows us to build multiple SAPI modules in a single build tree. This extension would have to analyze the requirements of a set of activated SAPI modules and would then choose the best build target (shared, static) for the set. - Sascha