[Cmake] INSTALL_FILES installs unconditionally

[Iker Arizmendi]

Andy,

The argument in favor would be that it avoids
unnecessary builds of other sources that rely
on the installed files.

If I build several packages with dependencies
like so:

     A <- B <- C

then I could have package B point into A's source
directory, but it seems more natural to have B
simply rely on whatever A installs (*). This is
especially true if A's install routine calls for
installing more than what's in A's include directory.
For instance, in my case A's build process creates
a config.h file and a custom cmake include file -
both of which reside in A's build directory.

Regards,
Iker

(*) Package B would use FIND macros over common
install locations to find A's files, just like
it would if installed on an end user's machine.


Andy Cedilnik wrote:
> Hi Iker,
> 
> CMake 2.0 uses redesigned install procedure. That said, it still always
> overwrites files. To my knowledge, this is a common practice.
> 
> Any arguments for and against?
> 
> I am not really sure you should depend on the files that are installed.
> 
> 			Andy
> 
> On Tue, 2004-08-17 at 13:55, Iker Arizmendi wrote:
> 
>>Our network has cmake 1.8.3 and I've noticed that
>>when I use the INSTALL_FILES directive the destination
>>files are updated even if they haven't changed (which forces
>>some of our other packages to rebuild). Does the most
>>recent version of CMake check to see if the install of
>>a file is necessary?
> 
> 
> 
> _______________________________________________
> Cmake mailing list
> Cmake at www.cmake.org
> http://www.cmake.org/mailman/listinfo/cmake
> 

-- 
Iker Arizmendi
AT&T Labs - Research
Speech and Image Processing Lab
e: iker at research.att.com
w: http://research.att.com