Re: Propose a change for build system.

From: Date: Thu, 01 Jan 1970 00:00:00 +0000
Subject: Re: Propose a change for build system.
References: 1 2 3  Groups: php.gtk.dev 
Request: Send a blank email to php-gtk-dev+get-3998@lists.php.net to get a copy of this message
Anant Narayanan escreveu:
That seems incredibly counter intuitive - I know on the windows end it'll just give you a warning that "libraries and headers were not found" but you can still keep building. If nix configure doesn't throw any kind of a warning then yes, it probably should at least inform you that you're nuts, but halting all together might drive people crazy.
    
[theghost php-gtk]$ ./configure --with-extra <snip> checking for gtkextra support... yes checking for gtkextra-2.0 >= 2.1.1... Unable to locate gtkextra version 2.1.1 or higher: not building </snip> Although, I will agree that it's a bit strenuous for the eye to scroll back and check which extensions haven't been built. Perhaps, we could add a small "summary box" at the end of configure that says which extensions will be built - I've come across quite a few projects that follow this practice. -- Anant Yes.
The default for linux is halt the configure, for example, if you do: ./configure --with-mysql On the php source, and do not have the headers for libmysql, the configure stop at that point. But a sumarry box to tell what is build and what is missing is good for me, at last you know what is there and what is missing before you try to use it in a script: Fernando.

« previous php.gtk.dev (#3998) next »