<div class="gmail_quote">On Wed, Oct 28, 2009 at 11:45 AM, Mathieu Malaterre <span dir="ltr"><<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Oct 28, 2009 at 4:41 PM, Tyler Roscoe <<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>> wrote:<br>
> This is a bad practice because then CMake has no way to know if there<br>
> are new header files and can't regenerate/install correctly. Ok maybe a<br>
> new header coming in will happen to trigger a rerun of CMake because the<br>
> header happens to belong to one of your built libraries or executables,<br>
> but I think this solution is more dangerous than just excluding .svn<br>
> explicitly.<br>
<br>
</div>+1<br>
<br>
Indeed I did not realize that.<br></blockquote></div><br><div>Except: that argument is not valid in this case. Neither file(GLOB nor install(DIRECTORY will "rerun" anything if a new header file is added into the directory...</div>
<div><br></div><div>File(GLOB is discouraged for specifying source files to add_library and add_executable because of the "cmake won't rerun if you add a file" problem. But in this case... it's 6 of one half dozen of the other -- neither case will detect the addition of a header file to the system....</div>
<div><br></div><div><br></div>