Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103651 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 69910 invoked from network); 30 Dec 2018 22:10:35 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 30 Dec 2018 22:10:35 -0000 To: internals@lists.php.net Date: Sun, 30 Dec 2018 19:42:30 +0100 Message-ID: References: <145164c0-9145-5527-c8d2-8a069a89b9b8@gmx.de> X-Newsreader: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Posted-By: 62.251.31.78 Subject: Re: [PHP-DEV] [RFC] [VOTE] FFI - Foreign Function Interface From: phpdev@ehrhardt.nl (Jan Ehrhardt) "Christoph M. Becker" in php.internals (Sat, 29 Dec 2018 12:27:58 +0100): >As I understand it, the extension would not be compiled by default, but >rather has to be enabled using an explicit --with-ffi configure >option[1] (or --enable-ffi on Windows[2]). A strange difference. Is not the convention that it should be --with-ffi when external libraries are needed? >[1] > >[2] > And as a BTW: in a snapshot build the extension will be enabled by force. Something like snapshot: forcing ffi on -- Jan