[CMake] How to handle a submodule existing twice in a project?

[David Doria]

>
> 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.
>
> Since TestA is a submodule, it should always be present in the sources
> anyway.
>
> Andreas
>

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.

See what I mean?

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20120517/eafe8679/attachment.htm>