Afternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7 ?
Anatol (or anyone), is there any way to get windows ext's built against
RC's while we're waiting for PECL/pickle/apples/whatever to be sorted ?
Cheers
Joe
Afternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7 ? Anatol (or anyone), is there any way to get windows ext's built against
RC's while we're waiting for PECL/pickle/apples/whatever to be sorted ?
Cheers
Joe
Quite a few extensions are being developed via branches now. It sounds
like this will be ok if pickle is being used, but should I be worried
about causing people headaches before that is ready?
I really don't want to have a bunch of preprocessor use in the
extensions I am working on. It makes them harder to maintain, and a lot
harder for new contributors.
thanks
Ah, I didn't think of using PHP5 to run pecl package ... that works ...
Cheers ...
Afternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7 ? Anatol (or anyone), is there any way to get windows ext's built
against
RC's while we're waiting for PECL/pickle/apples/whatever to be sorted ?
Cheers
JoeQuite a few extensions are being developed via branches now. It sounds
like this will be ok if pickle is being used, but should I be worried
about causing people headaches before that is ready?I really don't want to have a bunch of preprocessor use in the
extensions I am working on. It makes them harder to maintain, and a lot
harder for new contributors.thanks
http://windows.php.net/downloads/pecl/releases/pthreads/3.0.0/logs/
Well ... that didn't work, and doesn't tell me why ... anyone know what's
up ??
Cheers
Joe
Ah, I didn't think of using PHP5 to run pecl package ... that works ...
Cheers ...
Afternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7 ? Anatol (or anyone), is there any way to get windows ext's built
against
RC's while we're waiting for PECL/pickle/apples/whatever to be sorted ?
Cheers
JoeQuite a few extensions are being developed via branches now. It sounds
like this will be ok if pickle is being used, but should I be worried
about causing people headaches before that is ready?I really don't want to have a bunch of preprocessor use in the
extensions I am working on. It makes them harder to maintain, and a lot
harder for new contributors.thanks
Afternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7 ? Anatol (or anyone), is there any way to get windows ext's built
against
RC's while we're waiting for PECL/pickle/apples/whatever to be sorted ?
Cheers
JoeQuite a few extensions are being developed via branches now. It sounds
like this will be ok if pickle is being used, but should I be worried
about causing people headaches before that is ready?
Branches are releases nightmares if they are all have the same versions,
like all are 1.4.x but only one branch supports 7.
I have asked that some time ago already and pointed out that we should
really support semver and one branch per extension version, not per
supported php version.
I really don't want to have a bunch of preprocessor use in the
extensions I am working on. It makes them harder to maintain, and a lot
harder for new contributors.
It is not necessary required, you an email multiple files. Single branche
also helps to ensure APIs compatibility across php versions (same codename
being maintained).
thanks
Afternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7
?
Anatol (or anyone), is there any way to get windows ext's built
against
RC's while we're waiting for PECL/pickle/apples/whatever to be sorted
?Cheers
JoeQuite a few extensions are being developed via branches now. It sounds
like this will be ok if pickle is being used, but should I be worried
about causing people headaches before that is ready?
Fixing autocorrect :)
Branches are releases nightmares if they are all have the same versions,
like all are 1.4.x but only one branch supports 7.
I mean if an extension uses either 1.4 for 5.x and 1.5/2.x for 7 with same
APIs. This is a long term pain from a developer and end user point of view.
I have asked that some time ago already and pointed out that we should
really support semver and one branch per extension version, not per
supported php version.I really don't want to have a bunch of preprocessor use in the
extensions I am working on. It makes them harder to maintain, and a lot
harder for new contributors.It is not necessary required, you an email multiple files.
You can use multiple files.
Single branche also helps to ensure APIs compatibility across php versions
(same codename being maintained).
thanks
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 10/09/2015 19:14, Pierre Joye a écrit :
Afternoon internals,
Is there any concrete plan for deploying pecl extensions for
PHP7 ?Anatol (or anyone), is there any way to get windows ext's
built
against
RC's while we're waiting for PECL/pickle/apples/whatever to be
sorted ?Cheers Joe
Quite a few extensions are being developed via branches now. It
sounds like this will be ok if pickle is being used, but should I
be worried about causing people headaches before that is ready?Branches are releases nightmares if they are all have the same
versions, like all are 1.4.x but only one branch supports 7.I have asked that some time ago already and pointed out that we
should really support semver and one branch per extension version,
not per supported php version.
I definitively agree on this.
" Extension version have to reflect the extension API version "
Which probably have to be the same for php 5 and php 7
Else imagine the nightmare for user to detect API...
I really don't want to have a bunch of preprocessor use in the
extensions I am working on. It makes them harder to maintain, and
a lot harder for new contributors.It is not necessary required, you an email multiple files. Single
branche also helps to ensure APIs compatibility across php versions
(same codename being maintained).
Yes multiple files is NOT perfect, but it works
(when too much conditional for a single file)
See https://github.com/pierrejoye/php_zip
And it works.
Remi.
thanks
-- To
unsubscribe, visit: http://www.php.net/unsub.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlXxv08ACgkQYUppBSnxahhOOACfTOWy9MnNlTCezhO3BeIDvRyU
OlsAn3zM1h7gGxm/OJ4R8EhvwV5cvkHN
=rFRS
-----END PGP SIGNATURE
Hi Joe,
-----Original Message-----
From: Joe Watkins [mailto:pthreads@pthreads.org]
Sent: Thursday, September 10, 2015 4:25 PM
To: PHP internals internals@lists.php.net
Subject: [PHP-DEV] PHP7 PECL ExtensionsAfternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7 ? Anatol (or anyone), is there any way to get windows ext's built against RC's
while we're waiting for PECL/pickle/apples/whatever to be sorted ?
Yeah, I've just tried to replace 7.0.0 with 7.0.0RC2 in the package.xml and it went through. But also need the vc14 deps, I've planned time to build them in the week after next.
Regards
Anatol
Hi Anatol,
I thought vc14 deps were just copied from somewhere else, that's what I
did to test ?
Does that mean no dlls for now ?
Any time is good, you have more important things to do ;)
Cheers
Joe
On Thu, Sep 10, 2015 at 5:20 PM, Anatol Belski anatol.php@belski.net
wrote:
Hi Joe,
-----Original Message-----
From: Joe Watkins [mailto:pthreads@pthreads.org]
Sent: Thursday, September 10, 2015 4:25 PM
To: PHP internals internals@lists.php.net
Subject: [PHP-DEV] PHP7 PECL ExtensionsAfternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7 ? Anatol (or anyone), is there any way to get windows ext's built
against RC's
while we're waiting for PECL/pickle/apples/whatever to be sorted ?
Yeah, I've just tried to replace 7.0.0 with 7.0.0RC2 in the package.xml
and it went through. But also need the vc14 deps, I've planned time to
build them in the week after next.Regards
Anatol
-----Original Message-----
From: Joe Watkins [mailto:pthreads@pthreads.org]
Sent: Thursday, September 10, 2015 6:25 PM
To: Anatol Belski anatol.php@belski.net
Cc: PHP internals internals@lists.php.net
Subject: Re: [PHP-DEV] PHP7 PECL ExtensionsHi Anatol,
I thought vc14 deps were just copied from somewhere else, that's what I did
to test ?
Does that mean no dlls for now ?
Yep, those are copied from the prepared deps, but those deps are not built yet.The core deps are in place of course, but they're also built by humans :)
Any time is good, you have more important things to do ;)
Heh, a bit overdue now, but pthreads is now the first ringing bell witnessing the pecl deps should be done very soon. I'll see to build the pthreads ones this WE so you at least can avoid longer detention.
Regards
Anatol
Hugely appreciated, thank you ;)
Cheers
Joe
On Thu, Sep 10, 2015 at 5:37 PM, Anatol Belski anatol.php@belski.net
wrote:
-----Original Message-----
From: Joe Watkins [mailto:pthreads@pthreads.org]
Sent: Thursday, September 10, 2015 6:25 PM
To: Anatol Belski anatol.php@belski.net
Cc: PHP internals internals@lists.php.net
Subject: Re: [PHP-DEV] PHP7 PECL ExtensionsHi Anatol,
I thought vc14 deps were just copied from somewhere else, that's
what I did
to test ?
Does that mean no dlls for now ?
Yep, those are copied from the prepared deps, but those deps are not built
yet.The core deps are in place of course, but they're also built by humans
:)Any time is good, you have more important things to do ;)
Heh, a bit overdue now, but pthreads is now the first ringing bell
witnessing the pecl deps should be done very soon. I'll see to build the
pthreads ones this WE so you at least can avoid longer detention.Regards
Anatol
Joe Watkins in php.internals (Thu, 10 Sep 2015 17:25:22 +0100):
I thought vc14 deps were just copied from somewhere else, that's what I
did to test ?Does that mean no dlls for now ?
Any time is good, you have more important things to do ;)
If you want to try right now, test it with my deps:
http://phpdev.toolsforresearch.com/SDK14.tar.7z
Double 7z x [filename] to extract them with 7-Zip 9.38+. There might be
symlinks (directory junctions) in the tar and 7-zip supports them in the
newest version.
Jan
2015-09-11 23:13 GMT+02:00 Jan Ehrhardt phpdev@ehrhardt.nl:
Joe Watkins in php.internals (Thu, 10 Sep 2015 17:25:22 +0100):
I thought vc14 deps were just copied from somewhere else, that's what
I
did to test ?Does that mean no dlls for now ?
Any time is good, you have more important things to do ;)
If you want to try right now, test it with my deps:
http://phpdev.toolsforresearch.com/SDK14.tar.7zDouble 7z x [filename] to extract them with 7-Zip 9.38+. There might be
symlinks (directory junctions) in the tar and 7-zip supports them in the
newest version.Jan
--
Hello together,
it seems there are already some extensions build successfully for
php7windows
in my case i miss currently two extensions:
About imagick i found just this on gophp7
https://github.com/gophp7/gophp7-ext/wiki/ext-imagick
Are there still problems, or do they just need to be rebuild?
Best regards
Martin
Martin Keckeis in php.internals (Fri, 4 Dec 2015 09:01:20 +0100):
it seems there are already some extensions build successfully for
php7windowsin my case i miss currently two extensions:
About imagick i found just this on gophp7
https://github.com/gophp7/gophp7-ext/wiki/ext-imagick
Imagick, Apcu and a lot of others are here:
https://www.apachelounge.com/viewtopic.php?t=6359
The x86 versions are still being recompiled because of
https://github.com/krakjoe/apcu/issues/151#issuecomment-161962312
The x64 versions already have APC Backwards Compatibility.
Jan
Martin Keckeis in php.internals (Fri, 4 Dec 2015 09:01:20 +0100):
it seems there are already some extensions build successfully for
php7windowsin my case i miss currently two extensions:
About imagick i found just this on gophp7
https://github.com/gophp7/gophp7-ext/wiki/ext-imagickImagick, Apcu and a lot of others are here:
https://www.apachelounge.com/viewtopic.php?t=6359The x86 versions are still being recompiled because of
https://github.com/krakjoe/apcu/issues/151#issuecomment-161962312The x64 versions already have APC Backwards Compatibility.
Also keep in mind that the builds are triggered on the pecl release, not
when a new php version is released.
About imagick i found just this on gophp7
https://github.com/gophp7/gophp7-ext/wiki/ext-imagickAre there still problems, or do they just need to be rebuild?
Imagick needed the 7 dev branch merging to master and tagging.
Downloads that were built automatically for Windows appear to be
available on the PECL page
https://pecl.php.net/package/imagick/3.4.0RC2/windows
There is one known issue for Imagick on Linux for PHP 7; it can't be
compiled statically into PHP due to a bug in PHP's conf files, which
is already fixed for PHP 7.0.1.
cheers
Dan
Martin Keckeis in php.internals (Fri, 4 Dec 2015 09:01:20 +0100):
in my case i miss currently two extensions:
APC Backwards Compatibility in the Windows builds solved:
https://github.com/krakjoe/apcu-bc/pull/2
Binaries available at
https://www.apachelounge.com/viewtopic.php?t=6359
You will have to load the extensions in this way:
extension=php_apcu.dll
extension=php_apc.dll
Or for *nix:
extension=apcu.so
extension=apc.so
I guess Joe Watkins will make a new release soon and then the Windows
binaries will be become available at http://pecl.php.net/package/APCu
Jan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 10/09/2015 16:25, Joe Watkins a écrit :
Afternoon internals,
Is there any concrete plan for deploying pecl extensions for PHP7
?Anatol (or anyone), is there any way to get windows ext's built
against RC's while we're waiting for PECL/pickle/apples/whatever to
be sorted ?
I think "pecl" is already ready ;)
pecl install apfd
downloading apfd-1.0.1.tgz ...
Starting to download apfd-1.0.1.tgz (4,375 bytes)
.....done: 4,375 bytes
<snip>
Build process completed successfully
Installing '/usr/lib64/php/modules/apfd.so'
install ok: channel://pecl.php.net/apfd-1.0.1
configuration option "php_ini" is not set to php.ini location
You should add "extension=apfd.so" to php.ini
Cheers Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlXxvMwACgkQYUppBSnxahgcRQCfXZxLwX21BKV2zEENV/GoHj3P
ypMAmwS8I76HE++9mMPT07wSW7MKRvKL
=U8mq
-----END PGP SIGNATURE