In message <[EMAIL PROTECTED]>, Alexandre Oliva writes:
>On Feb 13, 2000, Ossama Othman <[EMAIL PROTECTED]> wrote:
>
>> I like this idea. The AC_PROG_CXX macro would then be something like
>> the following (based on AC_PROG_CXX in the CVS repo):
>
>> AC_PROG_CXX([LIST-OF-COMPILERS],
>> [ACTION-IF-FOUND],
>> [ACTION-IF-NOT-FOUND])
>
>I like this.
And if ACTION-IF-NOT-FOUND defaults to "report error and exit" it will
allow existing usage to continue to work as expected.
>Maybe we could also have an argument or macro to set the test program
>to be used, so that different packages can set different requirement
>levels of C++, and AC_PROG_CXX will look for a C++ compiler that meets
>their needs, instead of picking the first one it finds just for
>configure to abort later on because the compiler doesn't satisfy the
>checked needs.
What exactly do you have in mind here? Are you thinking of a macro to
specify a level or perhaps better a list of requirements, maybe along
the lines of:
AC_SET_CXX_REQUIREMENTS(templates libstdc++)
AC_PROG_CXX
Or something where the user actually passes in a test program:
AC_SET_CXX_TEST([int main() {return 0;}])
AC_PROG_CXX
The latter is clearly more flexible, but perhaps less desirable as it
requires people to write their own tests (or copy them from elsewhere)
rather than using carefully crafted standard tests.
Cheers,
Olly
