Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68569
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.179 as permitted sender)
MIME-Version: 1.0
Sender: jdavidlists@gmail.com
In-Reply-To: <CAESVnVqxuqcm6PeoS5=hVLOE8Mex-zNtAjhaAvjyCTYNO4ZcQQ@mail.gmail.com>
References: <CABXB=RS6uL-d+0HbPpYxczw7jeijxu4s1TW5Lp_8fDvmafXS0w@mail.gmail.com>
	<CAESVnVoB-38am-2bWfCYcCKKjiPVGUP34aYjdMADsR3inijBBA@mail.gmail.com>
	<CABXB=RQKhFxCRmOO1QhpejX5EvaDfjE+sK9ybTFV-On0+ukuag@mail.gmail.com>
	<CAESVnVr86ZYYUcqUwLCQ0WPzLFpah6dW9H+mAucc7F=jsubarA@mail.gmail.com>
	<CABXB=RSZyWZmVma5pmnGXzhfvCNMDAsWkKKMs8UT_R1F5e0-QQ@mail.gmail.com>
	<CABXB=RTUsoHLqtu=eo98P-OmeEbW8N+t=HD9duNtJF_nJYY7sg@mail.gmail.com>
	<CAESVnVqxuqcm6PeoS5=hVLOE8Mex-zNtAjhaAvjyCTYNO4ZcQQ@mail.gmail.com>
Date: Mon, 19 Aug 2013 14:12:01 -0400
Message-ID: <CABXB=RRrC2FGHviD0MeZ=OUEX-ra3HAS8RkZ6CQGaLRiYjCurg@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Interest in a "null" SAPI for embedding?
From: j.david.lists@gmail.com (J David)

On Fri, Aug 16, 2013 at 9:15 PM, Sara Golemon <pollita@php.net> wrote:
> Right, gotcha.  I think ideally someone should put in the grunt work to do
> what you suggested: Build libphp5.so all the time, then link up
> php/mod_php5.so/etc... against that as a shared system library (which in
> turn other programs or SAPIs could link against).
>
> I'm not sure if anyone has the time and patience to do that (for its
> relatively small return), but it'd get my vote.

That is something I would volunteer to undertake (including RFC, etc),
but in order to do so in a productive way, someone else would have to
volunteer to do the Windows portion of the work.  That's well beyond
my knowledge, ability, and available development hardware.  :(

The big preliminary question for me would be, "Is there a specific
design reason why it isn't currently done this way?"  PHP already
requires shlib's that depend on shlib's, so that functionality is
probably universally available, but I can't shake the suspicion that
maybe there is some has-to-be-supported platform or use case hiding at
the periphery that requires static linking.  (Which could
hypothetically be addressed with a libphp5.a, but that isn't something
I've looked into at all.)

On the flip side of that, if the elsewhere-proposed OS/SAPI supported
list reduction for 5.6 were to come to pass, that might be the right
time for this change as well.  (It would also allow those
lesser-used/unused SAPIs to be independently supported if necessary,
without carrying them all along in the tree forever.)

Thanks!