振奋人心！php官方扩展安装程序pie发布 | laravel | laravel china 社区-380玩彩网官网入口

起飞了

感觉没有太大变化，pie用phar实现安装脚本，pecl是c安装脚本。

这有啥振奋的 :flushed:

一定也不振奋啊

半点卵用没有的功能

pie都不带点介绍的吗？首先，图片看不到

很多东西都出晚了，，

windows support in order to support windows users, you must publish pre-built dlls, as pie does not currently support building dlls on the fly. the expected workflow for windows-compatible releases is:

the release is made on github (only github is supported at the moment) a ci pipeline runs to build the release assets, e.g. in a github action the resulting build assets are published to the github release in a zip file the name of the zip file, and the dll contained within must be:

php_{extension-name}-{tag}-{php-maj/min}-{ts|nts}-{compiler}-{arch}.zip example: php_xdebug-3.3.2-8.3-ts-vs16-x86_64.zip the descriptions of these items:

extension-name the name of the extension, e.g. xdebug tag for example 3.3.0alpha3 - defined by the tag/release you have made php-maj/min - for example 8.3 for php 8.3.* compiler - usually something like vc6, vs16 - fetch from 'php extension build' flags in php -i ts|nts - thread-safe or non-thread safe. arch - for example x86_64. windows: architecture from php -i non-windows: check php_int_size - 4 for 32-bit, 8 for 64-bit. contents of the windows zip the pre-built zip should contain at minimum a dll named in the same way as the zip itself, for example php_{extension-name}-{tag}-{php-maj/min}-{ts|nts}-{compiler}-{arch}.dll. the .dll will be moved into the php extensions path, and renamed, e.g. to c:\path\to\php\ext\php_{extension-name}.dll. the zip file may include additional resources, such as:

php_{extension-name}.pdb - this will be moved alongside the c:\path\to\php\ext\php_{extension-name}.dll *.dll - any other .dll would be moved alongside c:\path\to\php\php.exe any other file, which would be moved into c:\path\to\php\extras{extension-name}. automation of the windows publishing php provides a set of github actions that enable extension maintainers to build and release the windows compatible assets. an example workflow that uses these actions:

name: publish windows releases on: release: types: [published]

permissions: contents: write

jobs: get-extension-matrix: runs-on: ubuntu-latest outputs: matrix: ${{ steps.extension-matrix.outputs.matrix }} steps: - name: checkout uses: actions/checkout@v4 - name: get the extension matrix id: extension-matrix uses: php/php-windows-builder/extension-matrix@v1 build: needs: get-extension-matrix runs-on: ${{ matrix.os }} strategy: matrix: ${{fromjson(needs.get-extension-matrix.outputs.matrix)}} steps: - name: checkout uses: actions/checkout@v4 - name: build the extension uses: php/php-windows-builder/extension@v1 with: php-version: ${{ matrix.php-version }} arch: ${{ matrix.arch }} ts: ${{ matrix.ts }} release: runs-on: ubuntu-latest needs: build if: ${{ github.event_name == 'release' }} steps: - name: upload artifact to the release uses: php/php-windows-builder/release@v1 with: release: ${{ github.event.release.tag_name }} token: ${{ secrets.github_token }} source:

好消息，支持windows了

本该十几年前就出的东西, 如今如落西山才出来

现在出也不晚，确实跟composer统一了，以后安装扩展和安装包一样简单了

感觉有点晚了，同时没有啥大的亮点。现在集成环境、docker之类的安装扩展也很方便，大家只会选择最熟悉的。

看上去还不错。不过可用这个命令安装的扩展太少了。只有20个左右，实际的php扩展应该有过百了。

干啥用的

ubuntu 安装扩展,比如 php7.4-cli， 感觉这个已经很方便了

不是二进制分发的。安装 swoole 一直超时，编译还一直报错。如果可以像remi一样并且支持windows，那就真的飞起来了

我觉得还是让composer支持二进制扩展编译安装比较合适，就类似于npm那种