Re: Configure summary

From: Date: Mon, 03 Jul 2006 23:57:01 +0000
Subject: Re: Configure summary
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-24259@lists.php.net to get a copy of this message
Gwynne wrote:
On Jul 3, 2006, at 8:34 PM, Rick Widmer wrote:
I was poking around at the TODO and I saw this:
    * make configure print out a summary when it's done (like XEmacs)
I'm working on a patch to bring in this functionality, out of sheer  "I need to learn more about autoconf and I want to contribute to PHP"- ness :). Does anyone have any thoughts on what might go into such a  summary? So far, I have install prefix, SAPI, debug on/off, things of  that simple nature. Also, any thoughts on whether the summary should  be printed from configure itself or config.status?
I would say it should list every option that the user can select, and show its value. For extra credit, on each entry tell if the value is the default - either set to the default value, or not specified.
The general consensus seems to be that I should show as much info as is reasonably possible. For this, extensions need to be able to register the summary information they can provide. I've come up with a couple of different ideas for the syntax on this: 1) Add a new parameter to PHP_NEW_EXTENSION(), i.e.:
    PHP_NEW_EXTENSION(standard, array.c base64.c basic_functions.c browscap.c crc32.c # \ etc,
                       ,,,, \
                       [Standard functions
Regex type:--with-regex=${REGEX_TYPE}]) 2) AC_DEFUN() a new macro, i.e.:
    PHP_SUMMARY_INFO([Standard functions], [Extension: Enabled
Regex type: --with-regex=${REGEX_TYPE}]) These are just random examples based on the standard extension, obviously. Anyone like either of these or have a better idea?
I really don't think it is worth changing/adding to the extension API for this in any way. If we can't do a simple summary with what we already have, let's just skip it. And as far as I am concerned, showing as much as possible isn't the goal here. The goal for me would be to get a summary that fits on a single 80x25 page without scrolling. If it is so long that it scrolls off, then we haven't gained much. It should be a quick-summary that you can glance at and quickly pick out if everything looks ok. -Rasmus

« previous php.internals (#24259) next »