RE: [Vxl-users] Example CMakeLists.txt

[Andrew F. <aw...@ro...>]

I'm slightly worried about path searching for VXL because it 
might find a version which the user doesn't know about, and which 
isn't the one they've just downloaded and installed.  For packages 
like libpng this doesn't matter so much, but for VXL it might 
make a difference.

i.e. imagine I've just installed /home/awf/vxl, and want to
try to use it. Being a good boy, and having read the manual, I go
to a new work area, and make a CMakeLists.txt file.

If I run cmake and it finds /usr/local/vxl, which is a year
old, and doesn't contain the exciting new features which are the
reason I downloaded, I might get confused.  I think new users
are happy with the idea that they must point to their installation
in order to use it, where "point to" means enter it at the cmake
config stage.

A.

> -----Original Message-----
> From: William A. Hoffman [mailto:bil...@ny...] 
> Sent: 17 January 2003 14:36
> To: Andrew Fitzgibbon; 'VXL Users List (E-mail)'
> Subject: RE: [Vxl-users] Example CMakeLists.txt
> 
> 
> I would suggest going one step further.   If you have
> a file you can look for in the VXL_BINARY_PATH, something that
> is configured by cmake, you can use a FIND_PATH command to try and
> find the path for you.   And if you make the default search areas,
> C:, /, ~, and some common names, many folks will just run cmake,
> and build without having to manually change a thing.   On windows, you
> can look in the registry for the last binary directory that 
> CMakeSetup used.
> This is done for VTK, and for most people building 
> application with cmake,
> they do not even have to tell it where VTK is, because cmake finds it.
> If FIND_PATH fails, then it creates the CACHE value just like the one
> you were going to use anyway.
> 
> 
> Here is the VTK one:
>   #
>   FIND_PATH(VTK_DIR UseVTK.cmake
>     # Support legacy cache files.
>     ${VTK_DIR_SEARCH_LEGACY}
> 
>     # Look in places relative to the system executable search path.
>     ${VTK_DIR_SEARCH}
> 
>     # Look in standard UNIX install locations.
>     /usr/local/lib/vtk
>     /usr/lib/vtk
> 
>     # Read from the CMakeSetup registry entries.  It is likely that
>     # VTK will have been recently built.
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build1]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build2]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build3]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build4]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build5]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build6]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build7]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build8]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build9]
>     
> [HKEY_CURRENT_USER\\Software\\Kitware\\CMakeSetup\\Settings\\S
> tartPath;Where
> Build10]
> 
>     # Help the user find it if we cannot.
>     DOC "The ${VTK_DIR_DESCRIPTION}"
>   )
> 
> 
> -Bill
> 
> At 11:11 AM 1/17/2003 +0000, Andrew Fitzgibbon wrote:
> 
> >> I agree with Bill. Having to modify a CVS'ed file to put in local
> >> information is asking for an inadvertent commit to happen. 
> I think the
> >> better solution, which Fred wrote earlier, is
> >> 
> >>    SET( VXL_BINARY_PATH "" CACHE PATH "VXL build (binary) 
> directory" )
> >> 
> >> Then, when you run CMakeSetup, ccmake, or cmake -i, you 
> will get this
> >> as a variable to set. Almost the same effect as editing the
> >> CMakeLists.txt file, but cleaner w.r.t. the CVS repository.
> >
> >Doh.  That version is much better, thanks everybody!
> >
> >
> >
> >
> >-------------------------------------------------------
> >This SF.NET email is sponsored by: Thawte.com
> >Understand how to protect your customers personal 
> information by implementing
> >SSL on your Apache Web Server. Click here to get our FREE 
> Thawte Apache 
> >Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
> >_______________________________________________
> >Vxl-users mailing list
> >Vxl...@li...
> >https://lists.sourceforge.net/lists/listinfo/vxl-users 
> 
>