Consider a CMakeLists.txt file as if it were one of your project files. You will use the CMakeLists.txt file to generate project files after converting to cmake. You should be able to write one that references your source, just as you reference your source from your existing VS project files.<br>
<br>The source can exist in any directory you want it to, you just have to reference it correctly from within the CMakeLists.txt file. It's only by convention and history that CMakeLists.txt files typically reference source files in the same directory.<br>
<div><br></div><div>Does that make sense?</div><div><br></div><div><br></div><div><div class="gmail_quote">On Thu, Dec 18, 2008 at 11:12 AM, Jon Shuler <span dir="ltr"><<a href="mailto:jonshuler@yahoo.com">jonshuler@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>I am looking at converting our build system to cmake and have found an issue. We keep all the project files (VS 6, VS 2003 and VS 2008) in one common directory that is separate from the source tree. Based on what I read it looks like CMake expects the CMakeLists.txt to exist in the same directory as the source.<br>
<br>What options do we have other than moving the projects files?<br><br>Thanks,<br><font color="#888888">Jon<br></font></div></div></div><br>_______________________________________________<br>
CMake mailing list<br>
<a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br></div>