Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:122697 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 526431AD8F6 for ; Wed, 20 Mar 2024 09:54:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1710928460; bh=FUWyWgqYAEZEs+S7Q+ebZYmLhuAcUipKdcT5rjfRCHY=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=NEpxkWlgC9Q0R4ZL6w8+qL4paeQ76mxGPbjxuhd/KFuPgNwfvx7roNIcbkvnm+JAi cte1JW1BVciZA8Yb4spkEUT5qTZaaynFzNyujbF3wcT2iPUp50K6+74iXnRaJF4IE5 xocDYDzapuiRmGkCSQGwR0E1RBudSy5bHsqJVF7Tj7cO/9TmyvSpNQOkFw9pkAzuiR RrMqihMSLTc0xzGST/q21hpkS6MWyG5rSwproIOA/J/mJuq3639F+MOlBkgTjOsL66 evlIIjhhzf8LsknjudojAI1C3LZoe2yQ3Njx/3eWzkcL9is302xwGMTgH+MSZSHPLy lN+Hbbt1tSScw== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2F00218006E for ; Wed, 20 Mar 2024 09:54:20 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: ** X-Spam-Status: No, score=3.0 required=5.0 tests=BAYES_20,DMARC_MISSING, SPF_HELO_PASS,SPF_SOFTFAIL,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from xdebug.org (xdebug.org [82.113.146.227]) by php-smtp4.php.net (Postfix) with ESMTP for ; Wed, 20 Mar 2024 09:54:19 +0000 (UTC) Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id A485D10C05F; Wed, 20 Mar 2024 09:53:54 +0000 (GMT) Date: Wed, 20 Mar 2024 10:53:54 +0100 (CET) To: Casper Langemeijer cc: internals@lists.php.net Subject: Re: [PHP-DEV] Windows PECL build machine died In-Reply-To: <5e54ca80-efb2-4a53-8286-1c119ec4179c@app.fastmail.com> Message-ID: <62915afe-066c-19b1-4503-278f9a9df5f5@php.net> References: <90094848-cf18-1b41-da8d-1abd60461940@gmx.de> <5e54ca80-efb2-4a53-8286-1c119ec4179c@app.fastmail.com> Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-1447149468-1710928434=:29878" From: derick@php.net (Derick Rethans) This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1447149468-1710928434=:29878 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Hi, To revive this ancient thread. We have made some progress getting these=20 builds made for Windows again. Shivam has been working on an extension builder for Windows=20 (https://github.com/php/php-windows-builder?tab=3Dreadme-ov-file#build-a-ph= p-extension)=20 =E2=80=94 GHA actions to build your DLLs on release. He's tried that on Xdebug:=20 https://github.com/shivammathur/xdebug/blob/master/.github/workflows/releas= e.yml This is still pre-release, so please don't rely on this yet! We are also looking at buliding some specific PECL extensions for=20 Windows, and uploading them to the downloads server. PECL DLLs are no longer served from the windows.php.net server either,=20 but instead from downloads.php.net/~windows :=20 https://pecl.php.net/package/ssh2/1.3.1/windows Uploading built DLLs to this server can not be done automatically due to=20 2FA requirements, but we'll think on how to improve that. cheers, Derick On Sun, 23 Apr 2023, Casper Langemeijer wrote: > Nothing seems to happen on this front, and our Windows users like to move= to PHP 8.2 too. >=20 > The windows.php.net site states: "This is because the Windows PECL build = machine died, and the team is still working on the long term plan of buildi= ng DLLs for PECL extensions with a new CI process." >=20 > We are 1 year since the machine died. 6 month since the statement on the = website. From the point of view of our users nothing has changed, and are q= uestioning if the windows project is still alive. >=20 > I'd like to ask: Is re-inventing the building process really a smart thin= g to do if it means we'll be out-of-service for more than a year? >=20 > "We're doing our best to finish that as soon as possible, and keep you up= to date." >=20 > I'm not questioning intentions, but I hate to think this is 'our best'. W= e should at least have and share a more concrete plan, possibly share a rou= gh timeframe and share if we hit a blocking problem. If help is needed, we = should ask. >=20 > Greetings, Casper --=20 https://derickrethans.nl | https://xdebug.org | https://dram.io Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/suppo= rt Host of PHP Internals News: https://phpinternals.news mastodon: @derickr@phpc.social @xdebug@phpc.social twitter: @derickr and @xdebug --8323329-1447149468-1710928434=:29878--