According to the CMake team if we want CMakeD to make it into the default CMake install we need to do the following:
The test should at least build an executable from more than one file, and a library from more than one file, and link them together. The more it tests, the better.
I had a look at the files in svn. Can you please have a look at the C/C++ support files in current cmake cvs ? They have been reworked a bit, among others to support cross compiling, a "compiler id" and more fine tuning:
Instead of searching for ranlib, there is now a CMakeFindBinUtils.cmake which does that.
The CMakeDetermine<lang>Compiler.cmake files now try to build a simple executable from which a "compiler id" can be extracted, have a look at CMakeDetermineCompilerId.cmake and e.g. CMakeCCompilerId.c
This compiler id is then used for loading the compiler specific file (instead of just the basename of the compiler).
There is now support for a CMAKE_SYSTEM_PROCESSOR specific file, have a look at CMakeCInformation.cmake
The output extension is now set in CMake<lang>Information.cmake and not in the configured file, this makes it easier to support toolchains which have unusual extensions.
