Add building of windows binaries to GitHub releases

[realFlowControl]

This PR will add making Windows releases and magically add them to the GitHub release for https://github.com/php/pie to find them. Once this PR is merged and working, we should fully support pie

[realFlowControl]

Thanks @cmb69, but it is still not working :-(
What I am trying is to support pie and following this https://github.com/php/pie/blob/main/docs/extension-maintainers.md#automation-of-the-windows-publishing
I guess we could also just use the already existing windows.yml and change the filenames so that they fit the schema that pie needs...
Just hoped it would be easier migrating to what is proposed ...

[cmb69]

@realFlowControl, should use php-windows-builder for release builds by all means for stability reasons (ideally all extensions should use exactly the same dependency versions etc.) For push CI this is not really a concern.

[cmb69]

Not sure if the build log is supposed to be contained in the download artifact, but otherwise this looks quite good now.

[realFlowControl]

Technically CI is green, but all tests are skipped 😱

[cmb69]

Oh, indeed. I guess that pthreads is not found. I'd remove the manual "Fetch dependencies" step (maybe that interferes), and see if it works.

PS: from a quick look at the implementation of php-windows-builder, it looks like it runs php run-tests.php directly (instead of nmake test), so deps\bin\ is not in the PATH.

PPS: I've filed php/php-windows-builder#9. You can verify the hypothesis by adding a test which does not rely on ext-parallel, but merely outputs the PATH, e.g.

--TEST--
Show PATH
--FILE--
<?php
var_dump(getenv("PATH"));
?>
--EXPECT--

[realFlowControl]

@cmb69 could you do me a favour and check if the binaries produced from the job do work for you?
https://github.com/krakjoe/parallel/actions/runs/13029111249?pr=336
AFAIK you are using PHP on Windows.

[cmb69]

I've only quickly checked the PHP 8.4 x64 build, and couldn't find any issues. However, the download package has a strange structure; the relevant files are in a zip archive inside the downloaded zip, and the build logs are also distributed. It might be necessary to add a release step.