From: Brad King <brad.king@ki...> - 2003-10-28 18:46:22
How do others feel about the maturity of the CMake-based configuration
process? Is it time to enable the option by default?
There are two parts to this decision:
Enabling the option by default here will simply replace the
configure script invocation with the cmake-driven process.
Configuration times will improve.
Enabling the option by default here will make the first cmake
"Configure" button-click take a long time. The problem is that the
msdev or devenv processes have to be loaded in the background for each
try-compile. This is very slow. Once the first run is over, though,
the Configure step will take the same time it does now.
Once the explicit try-compiles have been used for a while and we
are confident they are producing the correct results, we can setup the
cmake code to load pre-tested results when one of the Visual Studio
generators is used. This will remove the initial slow configuration