The idea is that the ./configure script should be modular. Small modules should do separate simple things and they should be able to run alone for testing, without the whole slow and big infrastructure. Still there should be a framework that collects all data and knows what to run. After trying this with project libgpmi, I found that there was a big problem with this: there's no script language which is all:
So scconfig mainly offers a framework to store test results, dependencies between tests and do test compiles/runs. The user may write simple functions in modules that test-compile and run various small test programs and store the result in a tree-like database. On the other layer, this tree can be used to generate makefiles or other text files using an extremely simple built-in template system. Of course the user is not bound to use this templating system, any C program that generates output would do.
There are source releases available for download, but for the latest version supporting the most tests running on most systems, please use svn://repo.hu/scconfig/trunk