Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51716
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=GoFkkxaNfHq46Xm43aJYES7JUd+lzs27e5xpykXWKajXH+2mD+nEH/V4ydmGGOx4za
         8zwWbA1U1PZgDSNfv8vnkyA/Wno+cwYE/tswEEfRzHru69UiIAZptCHfbH67K9SpdA2o
         +JRtxP+GsKdbAqLVP+PnxgqOpD1+Y+8Vsx/DE=
Message-ID: <4D8109CF.9040008@gmail.com>
Date: Wed, 16 Mar 2011 20:04:47 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: Alec <alecgorge@gmail.com>
CC: PHP Developers Mailing List <internals@lists.php.net>
References: <AANLkTimB8JEuc-PLRS2Gd59EU3suoeLuPV3c2U=iURMK@mail.gmail.com>	<50863.5626b73e.1300221859.nsm@avilys.eik.lt>	<AANLkTinUin5_npno2LvzNzjY3gMNcZtPn-AC4my-o78_@mail.gmail.com> <AANLkTinuiT1ZT7JUM6W_O7pXBAenpuZER1QnqsfrSzsF@mail.gmail.com> <06.04.19768.955008D4@pb1.pair.com>
In-Reply-To: <06.04.19768.955008D4@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Package php binaries + php script into one singleexecutable
 file
From: keisial@gmail.com ("=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=")

Alec wrote:
> I actually wrote that. I never imagined someone would actually find
> that useful!
>
> If you don't mind having a few external dlls, you can use dl (ick!) to
> load the extensions.
>
> I gave up supporting that because compiling the custom lightweight
> stubs took more work than I cared for. I am considering reviving the
> project and this time not writing in PHP (PHP should really not be
> used for GUIs IMO).

I have given a look at
http://winbinder.org/forum/viewtopic.php?f=10&t=1178 Your usage of
php.exe and php5ts.dll in the stub folder confused me, but I guess that
it is there just for being able to debug with that stub, and actually
never used.

Your current approach for a stub (set of php + libraries) seems to be:
* Configure php with the chosen extensions as static
* Add a static target to Makefile
* Compile
* Link library with embedder (a bit inefficiently by using the GUI)

I think that could be done faster if instead you built all extensions as
shared and modified the Makefile to convert all those dll to static
libraries. Then you would build php once, and get the different stubs
just by linking with different objects.
You would need to change zend_API.h's ZEND_GET_MODULE to define a
constructor function which autoloaded the module.
That approach should work for most extensions.