Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116664
Message-ID: <52501841-7691-b69f-ac96-9dc241181057@gmx.de>
Date: Thu, 16 Dec 2021 23:37:23 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.4.0
Content-Language: de-DE
To: =?UTF-8?B?SG9ydsOhdGggVi4=?= <friendlyanon_@hotmail.com>,
 Levi Morrison <levi.morrison@datadoghq.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <AM6PR0302MB33980A73D6E4DEAE1A1D2A3E99779@AM6PR0302MB3398.eurprd03.prod.outlook.com>
 <CAF+90c_5hFVf03BdH47JTM1KXYq2gHX_Ffv73no7xS1aamCRsg@mail.gmail.com>
 <AM6PR0302MB3398EBAAC407E9E7B08DD50699779@AM6PR0302MB3398.eurprd03.prod.outlook.com>
 <CAAKU0un0m0Tv-zr=u=q9mQahoMAkoJdNDJKr-1xT5bpgFWCTow@mail.gmail.com>
 <AM6PR0302MB33986B32A9307B003C322E1499779@AM6PR0302MB3398.eurprd03.prod.outlook.com>
In-Reply-To: <AM6PR0302MB33986B32A9307B003C322E1499779@AM6PR0302MB3398.eurprd03.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Surveying interest regarding CMake
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 16.12.2021 at 22:31, Horv=C3=A1th V. wrote:

>> I think the answer should be that _eventually_ they should have to
>> migrate, but in the interim we must maintain two build systems.
>
> You are right on the first point, but it is not a requirement for
> php-src to be managed by anything other than CMake to maintain phpize
> functionality for existing 3rd party software making use of it. From a
> quick look, I can tell that it just copies some files that can be
> generated/configured by CMake if necessary.

It seems to me the point is the autoconf (emulated on Windows) stuff we
have in php-src which is used by third party extensions in their
config.m4 and config.w32 files.  We cannot break that without giving
sufficient time to the respective maintainers to update these extensions
to use the new CMake build system.  If we can maintain both build chains
for some years, I'm all for switching to CMake, especially because
building on Windows is a major issue for many extension maintainers,
since the build chain is mostly undocumented, and is missing a lot of
features, like requiring a certain minimum version of a library, or
certain features of it.

Wrt. requiring some package manager, such as Conan: I think we should
try to keep the build requirements at a minimum.

Regarding the discussion platform for a potential CMake migration, maybe
a Github project could be helpful.

Regards,
Christoph