<div class="gmail_quote">On Thu, Feb 19, 2009 at 5:25 PM, Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
AFAIK the word 'deprecated' does not appear in the documentation for<br>
EXECUTABLE_OUTPUT_PATH. It will be around for a long time. We just<br>
recommend using the new variables because they are more powerful:<br>
<br>
1.) The new variables actually just initialize target properties<br>
so the values can be set on a per-target basis.<br>
<br>
2.) The new variables distinguish the .dll and .lib parts of a<br>
shared library on windows.<br>
<br>
Also, the new variables should not be put in the cache by convention.<br>
If you want the user to be able to edit the path, provide a different<br>
cache entry that you use to set the variables.</blockquote><div><br>Would a CMake Policy of warning the user if both EXECUTABLE_OUTPUT_PATH and CMAKE_RUNTIME_OUTPUT_DIRECTORY are defined be a good idea? (same for LIBRARY_OUTPUT_PATH)<br>
</div></div><br>-- <br>Philip Lowman<br>