[johnisgood]

m4conf is not using anything requiring GNU stuff though, and it has been tested with BSD m4 as well. It is noted in base.m4.

The license of m4conf itself is ISC.

m4sugar could be vetted so it is can become less than 120 KB.

I don't know if it is messy, look at the example configuration file. For me, it is more straightforward and less bloated than autotools, for example.

> I don't think that it's enough to test for header files being present. Almost all my tests target library features: including a header, calling some functions and actually linking a program. The contents of headers vary from system to system and with compiler options.

This is configurable as well in base.m4.

[johnisgood]

Perhaps an addition could be added, however, for third-party header files and functions.

[johnisgood]

I'll contact the author about this perhaps.

Oh and by the way:

> I don't think that it's enough to test for header files being present.

It checks for functions, too, not just header files, along with CPU features.

[johnisgood]

And "m4conf obviously has messy configure scripts" is not true, there are no scripts at all. Check out the examples. You cannot get any simpler.