Re: [Vxl-users] Example CMakeLists.txt

[Amitha P. <pe...@cs...>]

> At 07:02 PM 1/16/2003 +0000, Andrew Fitzgibbon wrote:
> 
> >There is an alternative, which I prefer, which is
> >to explicitly set the path to VXL in the private project's
> >CMakeLists.txt file.  Yes, I mean begin your CML.txt
> >with
> > SET(VXL_BINARY_PATH /home/awf/src/vxlbin)
> >This may seem wrong, but in fact is the safest solution.

On Thu 16 Jan 2003, William A. Hoffman wrote:
> This is also problematic because you have files under cvs that
> are locally modified.   CMake variables and the cache are meant to 
> handle this issue.   You find one path, most of the time automatically,
> and then cmake loads a configured file from that path and then knows
> all the path information it needs.

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.

If there are no objections, I'll update the VXL book appropriately.

Amitha.