[Insight-developers] cmake

[Miller, James V (Research)]

Originally, the issue is one of separation of the code that "finds"
ITK and the code that gets ITK settings.  The FindITK module is 
distributed with CMake and is rather static.  Once ITK is 
found, our CMakeLists.txt files that use ITK then call 
INCLUDE(${USE_ITK_FILE}).  For now, it is important that the UseITK.cmake
file be in the ITK repository so that we can change what gets imported
from ITK without having to wait for an upgrade to CMake.

Perhaps, however, the FindITK.cmake file could have the line
INCLUDE(${USE_ITK_FILE}) (which will load the UseITK.cmake file from 
the "found" version of ITK).

This would make the FindITK.cmake perform like the FindFLTK.cmake or
FindQt.cmake, etc.



> -----Original Message-----
> From: Stephen R. Aylward [mailto:aylward@unc.edu]
> Sent: Wednesday, September 25, 2002 10:14 AM
> To: Insight-Developers (E-mail)
> Subject: [Insight-developers] cmake
> 
> 
> 
> Hi,
> 
> If someone does a FindITK.cmake, shouldn't we assume that 
> they want to 
> include ITK paths and libraries?
> 
> There are arguments against this, but perhaps it would be nice if the 
> following CMakeLists.txt file was sufficient to compile an 
> ITK program 
> out of source...
> 
> PROJECT(MyProject)
> 
> INCLUDE (${CMAKE_ROOT}/Modules/FindITK.cmake)
> 
> SET ( MYPROJECT_SRCS
> main.cxx
> )
> 
> ADD_EXECUTABLE( MyProject MYPROJECT_SRCS )
> 
> 
> 
> -- 
> ===============================================
> Dr. Stephen R. Aylward
> Assistant Professor of Radiology
> Adjunct Assistant Professor of Computer Science
> http://caddlab.rad.unc.edu
> aylward@unc.edu
> (919) 966-9695
> 
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers
>