Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116706
Message-ID: <30a1da97a3b5689fd4f801f3bf08ae351e2cc4d9.camel@schlueters.de>
To: Nikita Popov <nikita.ppv@gmail.com>, =?ISO-8859-1?Q?Horv=E1th?= "V."
	 <friendlyanon_@hotmail.com>
Cc: PHP internals <internals@lists.php.net>
Date: Tue, 21 Dec 2021 19:26:25 +0100
In-Reply-To: <CAF+90c_5hFVf03BdH47JTM1KXYq2gHX_Ffv73no7xS1aamCRsg@mail.gmail.com>
References: 
	<AM6PR0302MB33980A73D6E4DEAE1A1D2A3E99779@AM6PR0302MB3398.eurprd03.prod.outlook.com>
	 <CAF+90c_5hFVf03BdH47JTM1KXYq2gHX_Ffv73no7xS1aamCRsg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Surveying interest regarding CMake
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Thu, 2021-12-16 at 20:15 +0100, Nikita Popov wrote:
> My main question would be how this will affect 3rd party extensions,
> which are currently using autoconf. Will they need to migrate to
> cmake, or will we have to effectively maintain both build systems?

We would have to keep our autoconf macros for phpize aroudn for a
while. Interoperability for out-of-tree-builds shouldn't be a problem
as long as a php-config script/tool is generated.

For building in PHP's tree (as static extension) the external vendors
would have to provide CMake files.

For building out of tree with CMake we should be able to produce the
FindPHP CMake macros.

Also the "pecl" tool (or a replacement) would need adaption.

But yes, we will need a bit of a grace period for everybody to adapt.
While I assume most will be happy to make the switch.

johannes