hi,
On Tue, Oct 22, 2013 at 9:28 AM, Jan Ehrhardt <php...@ehrhardt.nl> wrote:
> Johannes Schlüter in php.pecl.dev (Mon, 21 Oct 2013 16:00:50 +0200):
>>On Mon, 2013-10-21 at 14:28 +0200, Kevin Ingwersen wrote:
>>> Is there anything I could do? I thought about editing config.w32 - but I had
>>> my doubts on that one.
>>
>>Why doubts? That file defines what s possible.
>>
>>In there one can read
>>EXTENSION("curl", "interface.c multi.c share.c curl_file.c", true);
>>which forces a shared build. This comes from this commit:
>>https://github.com/php/php-src/commit/deb0695069ef72d7a0936fdabaa7c9fea02f7fcd
>
> Intriguing question by Kevin. I once made a curl.exe without any need
> for external DLL's, not even libeay32.dll and the like. Only the
> standard Windows dll's and the VC++ redistributables are needed.
It is indeed possible to compile a standalone curl.exe (see the
Makefile options I added to curl), but the question here is more about
the curl extension.
Johannes is right, the last argument of the extension function is
about defining how php_curl will be built. I never tried to build it
statically. There may be some issues due to symbol clashing but
nothing that could not be fixed, while it is not a high priority,
there is nothing to gain to have curl statically built :)
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PECL development discussion Mailing List (http://pecl.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
