On Sun, Dec 13, 2009 at 8:20 AM, Mark Jones <span dir="ltr"><<a href="mailto:mark.jones1112@gmail.com">mark.jones1112@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi David,<br><br>Thank you for all of your help so far.</blockquote><div><br></div><div>You're welcome...</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Am I attempting to use cmake in a way that is incompatible with cmake, or in a way that it wasn't intended for? It is OK if I am attempting to use it in a way it isn't designed for (in which case I can accept that and move on), </blockquote>
<div><br></div><div>Yes, unfortunately, you are. (So accept it, and move on...) :-)</div><div><br></div><div>You can *either* do add_custom_command stuff and have a bare Visual Studio project without any source files in (but that drives your build through Visual Studio and your existing makefiles without intellisense and all that)...</div>
<div><br></div><div>*Or* you can convert the makefiles you do have into CMakeLists.txt files that list all the sources, do add_library, add_executable and include_directories calls and generate VS project files that *replace* your makefiles...</div>
<div><br></div><div>But not both. (At least not without major CMake re-work...)</div><div><br></div><div>Why not convert your existing makefiles and just use CMake? It wouldn't be that much more effort than getting CMake to generate a hybrid/fake thing like you're trying to do already...</div>
<div><br></div><div><br></div><div>HTH,</div><div>David</div><div><br></div></div>