Thanks for the explaination. I added the files to the target list as suggested by Filipe, and it worked. It is nice to know this is the proper way to do it.<br><br><div><span class="gmail_quote">On 8/28/06, <b class="gmail_sendername">
Brad King</b> <<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Doug Henry wrote:<br>> No, since it is a dependency of a source file that is included in the<br>> executable I would expect it to be handled (it was in previous<br>> releases). It seems that cmake does know about it, because it gives an
<br>> error with the correct path to the file that needs to be generated. I<br>> don't know why cmake will not run the custom command anymore. I suspect<br>> that the source files I generate this way are created because they are
<br>> in the list as you suggest.<br><br>Actually CMake never knew about the dependency. It was just an artifact<br>of the way the Makefile generator was implemented that it ever appeared<br>to work. In fact it was possible to not work in a parallel build, so we
<br>considered this "feature" of the Makefile generator a bug and fixed it.<br> It didn't work in the Visual Studio generators at all.<br><br>The only way to get this to work reliably is to add the output of the
<br>custom command as a source file of the target that needs it. Look at<br>the end of this FAQ answer:<br><br><a href="http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_generate_a_source_file_during_the_build.3F">http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_generate_a_source_file_during_the_build.3F
</a><br><br>-Brad<br></blockquote></div><br>