Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105298 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 64634 invoked from network); 17 Apr 2019 02:10:05 -0000 Received: from unknown (HELO mail.experimentalworks.net) (84.19.169.162) by pb1.pair.com with SMTP; 17 Apr 2019 02:10:05 -0000 Received: from kuechenschabe.fritz.box (ppp-188-174-48-87.dynamic.mnet-online.de [188.174.48.87]) by mail.experimentalworks.net (Postfix) with ESMTPSA id B1E3646B05; Wed, 17 Apr 2019 01:08:49 +0200 (CEST) Message-ID: <1555456129.27325.7.camel@schlueters.de> To: Levi Morrison , Bishop Bettini Cc: Peter Kokot , Internals Date: Wed, 17 Apr 2019 01:08:49 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Required Make version From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Di, 2019-04-16 at 09:46 -0600, Levi Morrison wrote: >  > I'd be happy to work help with the CMake port, as I know it a decent > bit, but I don't have enough time to champion the whole thing. > That has been done ages ago: http://svn.php.net/viewvc/php/cmake/ Back then it didn't have any uptake because it was uncommon and people don't like to change. (and maybe some technical reasons where some hidden sauce in PHP's build system allows some magic) A key factor for PHP's build system (imo) back the was that PHP's incremental build was *a lot* faster (typical development cycle: touch a single file and type "make") than CMake (while CMake+make is more correct since it also checks touched headers) nowadays we have SSDs, which makes this a bit less of an issue, and CMake supports ninja, which eventually might be faster. johannes