Re: [A-A-P-develop] configure target

[joerg <j....@we...>]

Bram Moolenaar wrote:
> Joerg Beyer wrote:
> 
> Thus my suggestion is to tell the configure stuff what header file to
> generate, and leave it around, allowing it to be used by the program.
> Thus the header file used during the tests is the same one as used by
> the program to be build.
>

agreed.

> Well, I often prefer names without the "s", because some people think
> they need to use "header" when checking for one file and "headers" when
> checking more than one file.  You could read it as "the header check".
> It's not really important though, you need to lookup the argument in the
> docs anyway.

AC_CHECK_HEADER[S] has optinal arguments: a) the actions what to do
if the header(s) are found and b) if they are not found.

Do we need this or could we simply say: all these headers are needed and
if at  least one is missing, then we have to quit?

If we need a version of the check that has these actions, then I would
implement a check called "check headers" which simply takes a list (with
at least one header file) and a test that takes only one header file,
but has these actions. Usualy the action is to stop the configuration.

     Joerg