[Cmake] Searching for CMAKE_ROOT

[Bill Hoffman]

The following is how we are running the vxl configure scripts in the
Insight package:


# run VXL configure scripts
IF(RUN_CONFIGURE)
  EXEC_PROGRAM(${ITK_SOURCE_DIR}/Code/Numerics/vxl/configure 
               ${ITK_BINARY_DIR}/Code/Numerics/vxl)
  EXEC_PROGRAM(${ITK_SOURCE_DIR}/Code/Numerics/vxl/vcl/configure 
               ${ITK_BINARY_DIR}/Code/Numerics/vxl/vcl)
ENDIF(RUN_CONFIGURE)


This works find with cmake.

RUN_CONFIGURE is set when configure is run from cmake.


-Bill

At 01:42 PM 5/22/2001 -0400, Amitha Perera wrote:
>> CMAKE_ROOT is only for the standard CMake modules. For project
>> specific modules you can put them in the projects source tree and in
>> the projects cmake lists file just use a different include. For
>> example
>
>Actually, the modules and templates don't concern me: what you'd said
>is exactly correct, and that's what happens in vxl. What does concern
>me is running configure, which is run from the system
>directory. (Perhaps I am wrong.)
>
>I know there is some move to drop configure altogether, and have all
>configuration within cmake. Some of the things we want to test during
>configure time are: does the (C++) compiler support partial
>specialization? Does it recognize the export keyword? Does the export
>keyword actually do anything? and so on. Since some of this involves
>compiling little test programs, I'm not sure how it can be done
>cleanly within CMake.
>
>Amitha.
>
>_______________________________________________
>Cmake mailing list
>Cmake at public.kitware.com
>http://public.kitware.com/mailman/listinfo/cmake