Windows DLL for Phalcon 5 + PHP 8.2 missing #16318
Comments
vibonaccidtt
added
the
new feature request
vibonaccidtt
changed the title
|
Every time it is hard to do that, as PHP core developers are not interested to support that, even in PECL it is impossible to download new .dlls any more. I'll see what we can do, but in middle/long term I think PHP team will drop Windows support and focus only on Unix. Especially when Windows has WSL (Windows Subsystem for Linux). |
|
Last update from windows.php.net dated 17 Oct 2022:
Doesn't sound very promising... |
|
Inside the apachelounge.com forum, there is an awesome guy "Jan-E" who provides windows PHP builds including nearly all possible existing php extensions which dont have official windows builds since ages (most probably the ones you are waiting for to be able to compile phalcon 5.x for PHP 8.2+ (PHP 8.3 is around the corner in november as well 😉 and he already provides builds for that as well) I posted there if he might be able to help you out getting phalcon running for windows in PHP 8.2+ |
Done. https://www.apachelounge.com/viewtopic.php?p=42029#42029 |
|
Quote from UPGRADING.INTERNALS of PHP 8.3:
Fixed building for PHP 8.3 |
|
Googling around I found only 1 php_protobuf.dll. For PHP 5.6, so I thought that would not be easy. But it actually was easy, if you know how to write a config.w32 for Windows that mimics the config.m4 for *nix. grpc compiled out-of-the-box, but it took a long time and generated a massive pdb file (75 MB). I will not include the phalcon and grpc extension in my regular builds, because they take too much my laptop-resources and my own time. You can find the PHP 8.2 builds with phalcon, grpc and protobuf here: |
|
Awesome. Thank you very much :) EDIT: a couple of example workflows: |
|
The sources of the extensions and my patches are not stable enough for something like github actions. I had to try a config.w32 for grpc twice before it worked. And the new config.w32 for protobuf something of 8 times. A real test for an extension requires building all PHP sources and then reconfigure PHP after each edit in a config.w32. And rebuild the extension a couple times until it succeeds. Manual edits and rebuilds, which you cannot script. |
|
from where i can find php_phalcon.dll file for phalcon 5+, kind of stuck now |
I guess i am new to it, how can i download php_phalcon.dll file from your build and the link provided by you? please help me out |
|
https://www.apachelounge.com/viewtopic.php?t=6359 Once PHP 5.2.8 is released the links to PHP 8.2.7 will disappear (but the files still there) and I will not be automatically compile phalcon and protobuf anymore. Then you will have to use these links: |
This PR adds a config.w32 for the PHP extension and includes it in the tgz for PECL. I used this to build php_protobuf.dll for PHP 8.2.7. See phalcon/cphalcon#16318 (comment) for the request to build the extension and the result. Please review and merge. Closes #13097 COPYBARA_INTEGRATE_REVIEW=#13097 from Jan-E:php-windows 4259af1 PiperOrigin-RevId: 542050878
|
@Jeckerson considering that now you have all the required extension .dlls can you release a Phalcon build for php 8.2 on next Phalcon release? |
Hello @Jan-E Sir, they have solved deprecated errors in Phalcon 5.2.3 for php 8.2, can you please help us to provide PHP builds for the same, as the older version has so many deprecated errors that if we enable error reporting it just goes bad gateway. |
|
@HiralRajgor unfortunately they only fixed some of the deprecation warnings. For now you can just disable error reporting for deprecation warnings: error_reporting(E_ALL ^ E_DEPRECATED); |
|
@hakimio |
|
well, at this point I understand why Phalcon 6 with 100% PHP 8.x source was considered. |
|
Thanks for this! Would it be possible to compile the latest Phalcon 5.6.1 for PHP 8.3.0? |
|
This has been addressed with #16533 Thanks to @JMoodyFWD The DLL files for 5.6.1 have been uploaded in the release page. |
Windows DLLs for Phalcon 5 + PHP 8.2 are missing.
Are these coming at a later date or was Windows support dropped?
The text was updated successfully, but these errors were encountered: