[Ping jyh] Re: [Omake] Should we provide AC_MSG_* and other autoconf-style functions?

[Jason Hickey]

On Feb 16, 2007, at 8:26 PM, Aleksey Nogin wrote:

> On 15.02.2007 21:24, Nathaniel Gray wrote:
>> I would propose the usual omake convention of camelcase, possibly
>> replacing AC with something like Conf:
>>
>> ConfChecking, ConfMsgError, ConfMsgFound, etc.
>
> Jason, any thoughts?

I think Nathan has the right idea, where we do configuration in the  
natural way, and autoconf compatibility is a separate issue/ 
compatibility module.

> Also, should we replace the functions like CheckHeader with a set like
> CheckCHeader, CheckCXXHeader, etc, or should we use the autoconf style
> of a single "multi-language" test function for every test and a "set
> language" function?

Good question.  I don't think I know the answer.

For a language XXX, I think the easier implementation is  
CheckXXXHeader.  Some other options are like this (I'm using  
"XXXProgram" as an example, but the same applies to CheckXXXHeader  
functions).

Option 0:
    XXXProgram(foo, moo boo)

Option 1:
    section
        LANG = XXX
        Program(foo, moo boo)

Option 2:
    section
        open XXX
        Program(foo, moo boo)

Option 3:
    MyXXX. =
        extends $(XXX)
        Program(foo, moo boo)

It isn't clear to me that one is better than another...

> I have some that are compatible - AC_MSG_CHECKING, AC_MSG_RESULT,
> AC_MSG_WARN and AC_MSG_ERROR.

In any case, it seems like the aim of an autoconf module should be to  
be pretty close to autoconf.

Jason

--
Jason Hickey                  http://www.cs.caltech.edu/~jyh
Caltech Computer Science      Tel: 626-395-6568 FAX: 626-792-4257