<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div class="im"><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>
<div><br></div><div>Since TestA is a submodule, it should always be present in the sources anyway.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Andreas</div></font></span></div>
</blockquote></div><br><div>I use functionality of TestB in Test. If TestA decides to remove TestB, then Test will break. I was trying to "hide" the implementation of TestA by requiring both TestA and TestB to be submodules of Test, regardless of whether or not TestA has TestB as a submodule of its own.</div>
<div><br></div><div>See what I mean?<br clear="all"><br>David</div>