On 2007-04-21 21:19+0200 [EMAIL PROTECTED] wrote:
- considering the cache: should XXX_INCLUDE_DIRS and XXX_LIBRARIES *really* be excluded from the (user-configurabe) cache? (I don't think so, because then it's not possible for the user to configure these paths...)
The preferred method is for the user to set CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH appropriately, see http://www.cmake.org/Wiki/CMake_Useful_Variables. The advantage of this approach is it greatly reduces the number of different variables that the user has to worry about. Thus, it is actually a good thing that the user doesn't have to worry about setting individual XXX_INCLUDE_DIRS and XXX_LIBRARIES values for find modules that correspond to the standard. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
