Re: [AD] configure script: feature or bug ?

[Hein Zelle <hein@xxxxxxxxxx>]

Eric Botcazou wrote:

> IMHO if the messages were not (strictly) identical, this feature would have 
> little value, since you couldn't compare two runs of ./configure; for example
> 
>    checking for linux/fb.h...yes
> 
> and
> 
>    checking for linux fbcon support....disabled

I'm not sure, maybe I'm misunderstanding the thread, but can't you do
something like what emacs (and many other packages) do and print a
summary at the end of configure with the features that have been
chosen and discarded? That way you can distinguish between if a
feature is 'present' on a system, and if the user selected it or
not. I always find it convenient to get such a summary at the end,
because you can see (without scrolling back through 500 lines) if
configure selected the right options for you.

Something like

Allegro will support the following graphics drivers:

X
fbcon
...

The following drivers are disabled:  (optional)

vga
vbeaf

The same can be done for sound, and other drivers of course. Also for
debug and profiling libraries this would be handy (to indictate if
they will be built).

Hein Zelle

>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-< 
 Unix is user friendly. It's just very particular about who 
 it's friends are.

 Hein Zelle                     hein@xxxxxxxxxx
	                        http://www.icce.rug.nl/~hein
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<