Re: Publish pinpoint-apm PHP extension in PECL
| From: | Christoph M. Becker | Date: | Mon, 29 Jul 2024 09:56:52 +0000 |
| Subject: | Re: Publish pinpoint-apm PHP extension in PECL | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-17597@lists.php.net to get a copy of this message | ||
Hi!
I'm also replying to the mailing list, since that might be interesting
for others, too.
On 29.07.2024 at 05:51, Mile Jeason wrote:
> I searched all doc but not found any document about release .dll(windows extension ) to
> pecl.php.net.
Windows builds are done by those who operate
<https://github.com/php/php-windows-builder>,
and these people will also
upload the DLLs so they are available on PECL.
For that to work, you first need a config.w32 (in addition to
config.m4), and Windows must generally be supported by your package. If
you have a Windows build environment, see
<https://wiki.php.net/internals/windows/stepbystepbuild_sdk_2>
on how to
actually do these builds yourself (for testing and maybe bug fixing).
If you don't, you can set up a Github action to do Windows test builds,
either using <https://github.com/php/setup-php-sdk> or
<https://github.com/php/php-windows-builder>.
I haven't tried the
latter yet, but have some experience with the former. See e.g.
<https://github.com/php/pecl-database-dbase/blob/master/.github/workflows/ci.yml>
how this can be done for simple extensions which do have no further
library dependencies.
If your package has external requirements, these would need to be built
by <https://github.com/winlibs/winlib-builder>,
and uploaded to the
distribution server.
> 3.
> How to replace/remove an existed release.
That is usually not done. Instead just create a new release with a new
version number and upload that. You can mention in the changelog what
was wrong with the old release.
Cheers,
Christoph