> On Mon, Jun 07, 2010 at 02:14:00PM -0400, Nathan Huesken wrote: >> > 1. Why do you need to nest one project inside the other? I think you >> > will have less trouble if you treat each one as its own independent >> > project. >> >> Because it the outer projects depends on the inner and they are >> strongly connected. It does not make sense to ship the outer without >> the inner. > > But you might ship Inner without Outer, right? Or use Inner in a third > project, OffToTheSide? These relationships are easier to model and less > messy if Inner doesn't live inside Outer. > > Anyway, just something to consider. >
This is not exactly what you want, but may contain the solution you need. I wrote 3 articles on getting separate projects to build together as if they were one. The articles partly focus on the issues of getting Git and Mercurial to cooperate with this, but also use CMake as the glue. (I invent the name 'Unification script'.) I use LuaDoc as the real world example which has dependencies on a bunch of other projects. Article starts here: http://playcontrol.net/ewing/jibberjabber/git_superproject_and_submod.html -Eric _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
