We have recently switched from cvs to perforce and encountered the same problem. In our case the fix was to change the CMakeList.txt file to refer directly to the file in the source tree rather than first copying it to the build tree and then referring to it there. As the clean command only affects the build tree the problem goes away - the read only file remains in the source tree and is not required to be cleaned anymore.<br>
<br>--<br>Glenn<br><br><div class="gmail_quote">On 31 January 2012 17:32, James Bigler <span dir="ltr"><<a href="mailto:jamesbigler@gmail.com">jamesbigler@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
We use perforce for our source control, and perforce typically syncs files as read only until you check them out for editing.<br><br>During our build process we copy a few scripts from the source tree to the build tree using 'cmake -E copy' in an 'add_custom_command'. This works famously until we try to run a clean command from within Visual Studio. At this point VS complains that it can't remove a read only file.<br>
<br>Has anyone else run into this problem?<br><br>There doesn't seem to be a way to use 'cmake -E' to change permissions. Would I have to create my own cmake script to run 'configure_file COPYONLY'?<br>
<br>Thanks,<br>James<br>
<br>--<br>
<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br>