Hi,<br><br><div class="gmail_quote">On Thu, May 17, 2012 at 11:20 PM, David Doria <span dir="ltr"><<a href="mailto:daviddoria@gmail.com" target="_blank">daviddoria@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have a main project (called Test) that has two submodules, TestA and TestB. TestA also has a submodule, which is exactly the same TestB.<div><br><div>So there is a directory Test/TestB as well as Test/TestA/TestB</div><div>
<br></div><div>In TestA/CMakeLists.txt, I have add_subdirectory(TestB).<br clear="all">In Test/CMakeLists.txt, I have add_subdirectory(TestA) as well as add_subdirectory(TestB).</div></div></blockquote><div><br></div><div>
Why are you doing that? If TestB is always available as sub-dir under TestA it doesn't make much sense to also add it as a subdirectory of the parent of TestA - IMHO. Test/CMakeLists.txt can still use all targets from TestB, since target names are always valid across the complete project.</div>
<div><br></div><div>Since TestA is a submodule, it should always be present in the sources anyway.</div><div><br></div><div>Andreas</div></div>