FrankenPHP is now an official php SAPI

[henderkes]

Should we include building it? It's quite simple actually, we only need go, xcaddy (and embed).

[crazywhalecc]

Do we distribute frankenPHP as well? Or just build? Since static-php-cli is the upstream project of FrankenPHP, it seems a bit strange to actively build projects that depend on it.

In fact, after spc-gnu-docker is improved, I would like to remove bin/build-static-frankenphp and replace it with vendor mode or other modes. Or I think it is feasible to add it there after spc-packages becomes stable.

BTW I plan to create some other static executables based on SPC builds after the vendor mode is implemented, which can reuse our static libraries. It's just an experimental project and organization, and other libraries may not need static builds as much or have native support.

[henderkes]

Yeah it's a bit of a woozy, but frankenphp doesn't directly depend on static-php-cli. It depends on a (any) ZTS embed build of php.

The static installation is a bit of an edge case that I would leave in the hands of the FrankenPHP repository, but we can build a version that links against libphp.so very easily.

I'll create a PR and you'll see what I mean.

[henderkes]

see: #772